Continuous Discovery: How to Talk to Customers Every Week (Without It Eating Your Roadmap)
Most teams do discovery in bursts, then build on stale assumptions for months. Continuous discovery — small, weekly customer touchpoints — keeps you close to reality. Here's how to make the habit stick without it eating your roadmap.
Most teams "do discovery" in bursts — a research sprint before a big bet, then months of heads-down building on assumptions that quietly go stale. By the time the feature ships, the market has moved and nobody noticed. The fix isn't more research. It's continuous discovery: small, weekly touchpoints with customers, run by the team building the product.
Why Weekly Beats Quarterly
The cadence is the whole point. Teresa Torres, who coined the term, argues for at least weekly contact — because if you only talk to customers monthly, you spend a whole month making decisions with no feedback. Weekly, you can still remember what you shipped and why, and course-correct before a bad assumption compounds into a quarter of wasted work. Discovery stops being a phase and becomes a habit — like writing tests, not a special event.
The Three Conditions
Continuous discovery only works if three things are true:
- The team talks to customers directly — not through a research report, a persona deck, or a sales team's paraphrase. Second-hand insight loses the detail that changes a decision.
- Activities are small. Not a two-week study — a 20-minute interview, one prototype test, a quick survey. It has to fit alongside shipping, or it won't happen.
- It's anchored to an outcome. You're not collecting interviews for a library; you're chasing a specific result (lift activation, reduce churn) and using contact with customers to find the path.
Where It Breaks Down
The habit is simple; sustaining it is hard. Two failure modes kill it:
- Recruiting friction — if booking a customer call takes a week of back-and-forth, weekly becomes monthly becomes never. Automate the pipeline with a standing interview slot.
- Insight decay — you do the interviews, then the notes scatter across Notion, Slack, and someone's head. Three months later nobody can find the quote that should have killed a feature.
Keep reading
The PM Role Is Splitting: Which Product Manager Are You Becoming?
The generalist PM is becoming the hardest role to hire for — because the job is splitting. The specialize-vs-AI-generalist fork, the four flavors of "AI PM," and the one career question that now matters most.
Jobs to Be Done: Why Your Customers "Hire" Your Product (and What That Changes)
Customers don't want your product — they hire it to get a job done, and fire it when something does the job better. Here's how Jobs to Be Done reframes discovery, prioritization, and messaging.
Your North Star Metric Is Probably Wrong: How to Pick the One That Isn't
Most teams pick a North Star Metric that's easy to move — and easy metrics don't predict survival. Here's how to choose one that measures value, break it into inputs you control, and connect it to evidence you can trust.