Continuous Discovery
✓ Weekly customer touchpoints, built into how you ship
On this page
Customer needs don't stand still, so product decisions shouldn't rely on research conducted months ago. Continuous discovery helps product teams make decisions based on an ongoing stream of customer insight instead of occasional research projects.
Rather than talking to customers only before a major launch, continuous discovery encourages regular customer conversations to validate ideas, identify opportunities, and keep product decisions grounded in real user needs. Whether you're a product manager, designer, researcher, or engineer, this guide explains what continuous discovery is, how it differs from project-based research, and how to build a sustainable program.
TL;DR
Continuous discovery is the practice of conducting at least weekly customer touchpoints with the team building the product through small research activities focused on a specific outcome. The approach, popularized by Teresa Torres in Continuous Discovery Habits, helps teams make better product decisions by staying connected to customer needs.
A successful continuous discovery program includes:
- A clearly defined product outcome
- A consistent process for recruiting participants
- A habit of testing assumptions before building
- A repeatable system for synthesizing research findings
Common challenges include information overload, limited stakeholder buy-in, and relying too heavily on feedback from a narrow group of users.
What is continuous discovery?
Continuous discovery is the practice of conducting at least weekly customer touchpoints with the team building the product through small research activities focused on a desired outcome. That definition comes from Teresa Torres, author of Continuous Discovery Habits.
“At a minimum, weekly touchpoints with customers by the team building the product where they conduct small research activities in pursuit of a desired outcome.”
The idea is straightforward: products evolve continuously, so customer research should too. Four parts of Torres's definition are especially important.
- Weekly customer touchpoints. Regular conversations help teams stay current with changing customer needs instead of relying on research conducted months earlier.
- The team building the product. Product managers, designers, and engineers participate directly in customer conversations. Hearing feedback firsthand builds shared understanding and reduces the risk of insights becoming diluted as they're passed between teams.
- Small research activities. Continuous discovery favors lightweight methods such as user interviews, usability tests, and short surveys over large, infrequent research projects. Keeping studies manageable makes a weekly cadence achievable.
- A desired outcome. Every activity should support a specific product goal, whether that's validating a feature, understanding user behavior, or identifying new opportunities.
Continuous discovery vs project-based discovery
Many organizations still approach discovery as a series of standalone research projects conducted before major product launches. While this approach can answer strategic questions, customer insights often become outdated as products and user needs change.
Continuous discovery takes a different approach. Instead of treating research as a one-time project, it becomes an ongoing part of product development. Discovery and delivery happen in parallel, allowing customer insights to inform decisions throughout the product lifecycle.
Factor | Project-based discovery | Continuous discovery |
|---|---|---|
| Cadence | Occasional, tied to launches | At least weekly |
| Who runs it | Dedicated research phase, often led by a specialist | The product team |
| What it produces | One large research report | Ongoing product decisions |
| Main risk | Findings may become outdated before they're applied | Requires an effective system for organizing and synthesizing data |
| Best for | Strategic, one-time research questions | Continuous product improvement |
Project-based research still plays an important role for large strategic initiatives. Continuous discovery complements that work by providing a steady flow of customer insight to guide day-to-day product decisions.
Who runs continuous discovery? The product trio
According to Teresa Torres, continuous discovery should be led by the team building the product. In practice, that often means the product trio: a product manager, designer, and engineer participating in customer conversations together.
When the people responsible for product decisions hear customer feedback firsthand, they develop a shared understanding of user needs and spend less time debating how to interpret research findings.
Researchers continue to play an important role. Rather than owning every customer conversation, they help teams improve research quality by advising on study design, interview techniques, and more complex research methods while supporting the product trio's ongoing discovery work.
Why run a continuous discovery program?
Continuous discovery helps product teams make better decisions by keeping customer insights current. Key benefits include:
- Stay aligned with changing customer needs. Regular conversations help teams identify changing priorities before they're reflected in usage data or support requests.
- Reduce the curse of knowledge. The longer teams work on a product, the easier it is to assume customers think the same way they do. Frequent customer conversations provide a more accurate view of the user experience.
- Reduce wasted development effort. Testing ideas early helps teams identify potential issues before investing significant engineering time.
- Improve backlog prioritization. Ongoing customer feedback provides better context for deciding what to build next and which opportunities deserve the highest priority.
- Build stronger customer relationships. Customers who see their feedback reflected in the product are more likely to remain engaged and invested.
- Balance customer and business goals. Continuous discovery helps teams evaluate customer feedback alongside business priorities to make more informed product decisions.
How to set up a continuous discovery program
Define your desired outcome
Start with a clear product outcome. It provides a shared focus for the team and helps distinguish meaningful customer feedback from information that isn't relevant to the decision you're trying to make.
Recruit participants continuously
Recruitment is often the biggest obstacle to maintaining a consistent discovery practice. If every study requires finding participants, coordinating schedules, and sending reminders from scratch, it's difficult to sustain weekly customer conversations.
Instead, build participant recruitment into your existing workflows. Invite customers while they're actively using your product, work with sales and customer success teams to identify potential participants, and automate scheduling wherever possible.
Great Question supports this process by helping teams recruit participants, send study invitations, manage incentives, and maintain a consistent participant pipeline. AI Moderation can also help teams conduct more customer conversations without requiring a researcher to moderate every session.
Organizations using this approach have significantly expanded their research capacity. One enterprise customer increased its annual customer interviews from 10,000 to 100,000. ServiceNow reduced participant recruitment time from 118 days to six, while Asana shortened recruitment timelines from approximately two weeks to just two or three days.
Test your assumptions before you build
Every product idea is based on assumptions. Before committing engineering resources, identify the assumptions that must be true for the idea to succeed and validate the most important ones first.
A useful framework is to evaluate each assumption against three questions:
- Desirability: Do customers actually want this?
- Feasibility: Can we build it?
- Viability: Does it support the business?
Continuous discovery helps answer these questions early through customer conversations, prototype testing, and lightweight research before development begins.
Ask better interview questions
A weekly cadence is only as good as the questions you ask in it. Two habits do most of the work.
The quality of your insights depends on the quality of your questions. Prioritize questions about past behavior over hypothetical scenarios. For example, asking, “Walk me through the last time you tried to do X” generally produces more reliable insights than “Would you use a feature that does X?”
Avoid leading questions that encourage participants to agree with your assumptions. Instead of asking, “How useful was this?” ask, “What did you do next?” Neutral, open-ended questions are more likely to uncover authentic customer behavior.
Visualise what you learn
As research accumulates, organizing and synthesizing findings becomes increasingly important.
Frameworks such as the Opportunity Solution Tree and experience maps help teams connect research findings to product opportunities and better understand the customer journey. Tools like Miro and FigJam make these frameworks easy to create and maintain.
As the volume of research grows, synthesis can become time-consuming. Great Question automatically groups recurring themes across interviews and links each finding back to the supporting transcript, making it easier to review evidence and identify patterns across studies.
Prioritise, act, and track
Research creates value only when it influences product decisions.
Prioritize findings based on their impact, feasibility, and alignment with your desired outcome. Then track both product metrics, such as Net Promoter Score and retention, and research health metrics, including customer participation and stakeholder engagement.
Regularly sharing findings and decisions helps maintain visibility and reinforces the value of continuous discovery across the organization.
Risks to watch
Like any research practice, continuous discovery comes with challenges.
- Information overload. Frequent customer conversations generate a large volume of qualitative data. Without an effective system for organizing and synthesizing findings, important insights can be overlooked.
- Limited stakeholder buy-in. Teams may hesitate to adopt continuous discovery without seeing its value. Sharing early successes and demonstrating business impact can help build support.
- Customer fatigue. Repeated research requests can reduce participation over time. Rotate recruitment strategies, space requests appropriately, and use incentives thoughtfully.
- Sampling bias. Relying on the same participants repeatedly can skew research findings. Recruit participants from different customer segments to ensure broader representation.
- Over-reliance on stated feedback. Customer interviews reveal what people say, which doesn't always match what they do. Combine qualitative research with behavioral data whenever possible.
How Great Question supports continuous discovery
Maintaining a continuous discovery program requires more than a research repository. Teams also need reliable ways to recruit participants, schedule sessions, conduct research, and organize findings.
Great Question brings these together in one platform, allowing teams to recruit participants, run studies, and analyze research without relying on multiple disconnected tools.
Unlike a standalone research repository, Great Question supports the entire research workflow, from participant recruitment through analysis. Several customers have moved away from Dovetail after adopting it.
For teams running research every week, consolidating these activities into a single platform can make continuous discovery easier to sustain.
Ready to build a continuous discovery program?
Frequently asked questions
What is continuous discovery in product management?
Continuous discovery is the practice of conducting at least weekly customer touchpoints with the team building the product through small research activities focused on a specific outcome. The goal is to keep product decisions grounded in current customer needs rather than relying on outdated research.
How is continuous discovery different from regular user research?
Traditional user research is often conducted as a standalone project tied to a product launch or major initiative. Continuous discovery is an ongoing practice that runs alongside product development, allowing customer insights to inform decisions throughout the process.
How often should you talk to customers in continuous discovery?
Teresa Torres defines continuous discovery as at least weekly customer touchpoints. The exact number of interviews is less important than maintaining a consistent cadence. Even one or two customer conversations each week can support an effective continuous discovery practice.
Who should run continuous discovery?
Continuous discovery is typically led by the product trio: a product manager, designer, and engineer. Researchers continue to play an important role by advising on research methods, interview design, and more complex studies while supporting the team's ongoing discovery work.
What tools do you need for continuous discovery?
At a minimum, teams need a reliable way to recruit participants, schedule and conduct research sessions, and organize research findings. Using a single platform for these activities can make it easier to maintain a consistent continuous discovery practice.
