Continuous Discovery Habits
by Teresa Torres
Discover products that create customer value and business value using a structured continuous discovery framework.
The short route — our review and key takeaways, 5 min read. The long route — buy the book on Amazon if you want to go deeper. Both routes work.
About the author
Teresa Torres
The short route
northstar's take on this book
Continuous Discovery Habits is the book that took user research out of the hands of dedicated researchers and put it back on PM desks. Teresa Torres argues — and now most modern teams agree — that talking to users is too important to outsource to a sprint or a quarterly study. It needs to be a habit.
The Opportunity Solution Tree is the artifact most teams remember from this book, and it has become standard practice at companies that run continuous discovery seriously. The framework is genuinely useful, but its real value is forcing PMs to articulate the chain between desired outcome, customer opportunity, and proposed solution — a discipline most roadmaps skip entirely.
Timing helped the book land. It came out in late 2021, when remote and distributed product teams had been forced to figure out asynchronous discovery without their usual office user-research infrastructure. It synthesized practices that had been emerging across product orgs for years — the weekly user touchpoint, the discovery trio, the structured opportunity-mapping exercise — into a single coherent operating system. The post-COVID moment made it land harder than it would have in 2018.
Newsletter
Like this review? Get the next book breakdown in your inbox.
One book or case study every few days — the short route, with the takeaways and our honest read. Free.
Free forever. Unsubscribe anytime. No spam.
The most common misreading is that the book is about 'doing customer interviews every week.' That's the practice, but it's not the point. The deeper argument is about how product decisions get made: whether they emerge from accumulated, ongoing contact with users, or whether they emerge from quarterly planning offsites driven by stakeholder politics. The interviews are downstream of the philosophy. PMs who try to copy the weekly interview habit without buying into the underlying argument tend to burn out within a few months.
Read this if you're a PM who has the title but feels disconnected from your users. It's most useful when you have authority over the discovery process and want to convince stakeholders that ongoing customer contact beats a quarterly research sprint. It's less useful at companies where research is already a separate function — though many such companies probably should question that structure.
For Indian PMs, the book's harder challenge is structural. Many Indian product teams sit inside founder-driven organizations where the founder's intuition about users carries more weight than any structured discovery process. The book assumes you have permission to talk to users on your own cadence; many Indian PMs don't, by default, and that permission is part of what they have to win before the book's practices become possible. It's worth reading not just to learn the methodology but to understand what good looks like.
Pair it with The Mom Test for the actual mechanics of customer conversations. Continuous Discovery Habits is strong on process and weak on the moment-to-moment craft of asking better questions; The Mom Test is the reverse.
Key concepts
- Opportunity Solution Tree — A visual map that branches from a desired outcome → customer opportunities (problems / unmet needs) → candidate solutions → experiments to validate them.
- Continuous discovery (weekly customer touchpoints) — Talking to at least one user every week as a habit, not as a quarterly research sprint — so user understanding stays fresh and built into decisions.
- Outcome over outputs — Measuring success by the change in customer behavior or business metric, not by the number of features shipped.
- Assumption tests vs. customer interviews — Interviews uncover what customers actually do today; assumption tests check whether specific beliefs about a future solution are true. They're different tools for different questions.
- The discovery trio (PM, designer, engineer in research) — All three roles attend customer conversations, not just PMs — because engineers and designers spot different signals than PMs do.
Who should read it
PMs who feel disconnected from their users and want a structured habit (not just a project) to fix it. Especially useful for teams transitioning from feature-factory to outcome-driven work.
Frequently asked
4 questionsSee it in practice
Case studies that demonstrate the ideas
More in Product Management