Continuous discovery is the practice of talking to customers at a regular cadence — typically weekly — as a standing team activity rather than a project-based initiative. Teresa Torres has made the framework widely known, and many teams have tried to implement it. Fewer have made it stick past the first quarter.
Why Continuous Discovery Fails to Become Habitual
The most common failure pattern is treating continuous discovery as a research team responsibility rather than a product team behavior. When interviews are scheduled and run exclusively by researchers, the practice scales poorly and the insights arrive secondhand to the people making decisions. Product managers and engineers who have not heard the customer's actual words will always discount the findings, however well they are written up.
The second failure pattern is setting expectations too high at the start. Committing to eight customer conversations per week for a team that has never run one is unsustainable. The habit breaks under deadline pressure and does not restart.
The Minimum Viable Discovery Cadence
A sustainable continuous discovery practice starts small: one interview per week, with the product manager in the room or on the call, talking to an existing customer about a problem the team is currently working on. That is the entire initial commitment. One conversation, one decision-maker present, one topic of active relevance.
The value of this minimum viable cadence is not the volume of insights it produces. It is the habit of contact — the weekly reminder that customers are real people with real workflows, not personas in a deck. Teams that sustain this minimum cadence for three months almost always expand it, because they have experienced what it changes.
Recruiting Infrastructure Is the Real Bottleneck
Once a team is committed to weekly interviews, the scheduling friction becomes the primary obstacle. Finding a new participant every week requires either a standing panel of customers who have agreed to periodic conversations, a well-maintained opt-in segment in your CRM, or an incentivized research program that surfaces willing participants from the user base continuously.
Building this infrastructure is a one-time investment that pays for itself in the third week. The teams that skip it burn out on recruiting within a month.
Connecting Discovery to Decisions
Continuous discovery only sustains when the team can trace specific product decisions back to specific customer conversations. Building a shared log — even a simple Notion page or Slack thread — where weekly interview notes are referenced when a roadmap decision is made creates the feedback loop that motivates the team to keep talking to customers. When the connection between conversation and decision is invisible, the practice feels like overhead. When it is visible, it feels like leverage.