Continuous Discovery
Synonyms: continuous product discovery, ongoing user research, continuous research, dual-track discovery, always-on research
Definition
Use cases
- Fixing “the wall”: Developers start asking, “Why are we building this?” Weekly user clips reconnect the team to real user problems without requiring a massive research report.
- Roadmap prioritization: Instead of debating priorities in meetings, teams use recent user feedback to decide what matters most right now.
How it's used in practice
- Recruit ahead of time: Set up an automated pipeline so users appear on your calendar every Thursday without you lifting a finger.
- Focus on problems: Ask users about recent frustrations and workarounds instead of asking what features they want.
- Share the raw data: Invite one engineer and one stakeholder to every call so the whole "trio" hears the pain points firsthand.
Challenges & limitations
- Recruiting fatigue: Weekly research requires a steady flow of participants, which takes operational work most teams underestimate.
- Stakeholder skepticism: Some teams mistake continuous discovery for slowing down delivery if research findings are not clearly tied to roadmap decisions.
- Research without action: Collecting interviews means very little if the team does not change priorities or product decisions afterward.
Commonly used tools
- Dovetail: Best for tagging and searching interview insights across a team repository.
- User Interviews: Best for automated weekly participant recruiting at scale.
- Maze: Best for fast prototype and assumption testing between interview cycles.
Free resources
- The Opportunity Solution Tree primer — Teresa Torres' original explainer on the OST, the backbone framework of continuous discovery.
- Product Talk — Product Discovery Hub — Teresa Torres' curated landing page on continuous discovery, with her best articles on interviewing, assumption testing, and OST in one place.

