Continuous Discovery

Continuous discovery is the practice of conducting weekly customer touchpoints by the product trio (PM, designer, engineer) to inform ongoing product decisions. It was popularized by Teresa Torres in Continuous Discovery Habits (2021) and is structured around mapping desired outcomes to opportunities to solutions to assumption tests, rather than running discovery in concentrated batches separate from delivery. It is the operational evolution of Marty Cagan's product-discovery framing, focused on making customer evidence a weekly rhythm rather than a project.

The core practices Torres specifies: weekly customer touchpoints (at minimum, a 30-minute conversation with a real customer each week, by the whole trio, not just the PM), opportunity solution tree (a visual map starting from the desired outcome at the top, branching into opportunities (customer needs, pain points, desires), then into solutions (ideas to address those opportunities), and finally into assumption tests at the bottom), assumption mapping (for each candidate solution, listing the desirability, usability, feasibility, and viability assumptions, then designing the cheapest test for the riskiest assumption), and interview snapshots (structured one-page summaries of each customer conversation that the whole team can reference). The most distinctive feature of continuous discovery versus traditional product research: the trio does the research together, not the PM alone, so the learning lands in the people making the build decisions rather than getting filtered through a hand-off. The 2024 to 2026 evolution: AI tools (Dovetail, Notably, Marvin, Sturdy) have automated the synthesis side of continuous discovery (transcription, theme extraction, snapshot generation) without replacing the actual conversation, which has shifted the bottleneck from "we can't synthesize fast enough" to "we don't talk to enough customers."

flowchart TD
    O[Desired Outcome] --> P1[Opportunity 1]
    O --> P2[Opportunity 2]
    O --> P3[Opportunity 3]
    P1 --> S1[Solution A]
    P1 --> S2[Solution B]
    P2 --> S3[Solution C]
    P3 --> S4[Solution D]
    S1 --> T[Assumption tests]
    S2 --> T
    S3 --> T
    S4 --> T

Ryan's Take

Continuous discovery is what good product teams do, full stop. The rest is just packaging. The hard part of the practice is not the tooling or the framework. It's the discipline to actually keep a weekly customer conversation on the calendar when the sprint is on fire and a release is slipping. The teams that protect that hour every week, in good months and bad, are the teams that build products people actually want. The teams that defer it to "next sprint when things calm down" never have a sprint where things calm down. The hour is the practice.

What founders get wrong: Treating continuous discovery as something only the product manager does. The whole point of the practice is that the trio (PM, designer, engineer) hears the customer directly, so the design and engineering decisions are informed by the same evidence the PM is operating on. If only the PM is in the interviews, you've recreated the hand-off problem the framework was designed to solve.

Related: [Product Discovery] · [User Research] · [Product Management] · [Product Team] · [Jobs To Be Done]

FAQ

What is continuous discovery? The practice, popularized by Teresa Torres in Continuous Discovery Habits (2021), of conducting at least one customer touchpoint per week by the product trio (PM, designer, engineer together) to inform ongoing product decisions. Structured around opportunity solution trees, assumption mapping, and interview snapshots.

What is an opportunity solution tree? A visual map developed by Teresa Torres, starting from the desired outcome at the top, branching into opportunities (customer needs, pain points, desires), then into solutions (ideas to address those opportunities), and finally into assumption tests. The tree is updated weekly as new evidence arrives.

Who should be in the customer interviews? The full product trio (PM, designer, engineer), not just the product manager. The distinctive value of continuous discovery is that the people making build decisions hear the customer directly, rather than getting evidence filtered through a hand-off. PM-only interviews recreate the problem the framework was designed to solve.