Definition
Continuous Discovery
Continuous discovery is the practice of engaging with customers regularly — ideally weekly — to inform product decisions, rather than running discovery as a one-off phase before delivery. Small cross-functional teams interview users, spot unmet needs, test solution ideas, and feed that learning directly into what they build, keeping discovery and delivery running in parallel.
Key takeaways
- Continuous discovery means engaging customers on a regular (ideally weekly) cadence to inform decisions — not a one-off phase before building.
- Popularized by Teresa Torres, it runs with a product trio (PM, designer, engineer) so insights arrive while there's still time to act.
- Learning is tied to decisions via the opportunity solution tree and small assumption tests before committing to a build.
- It pairs with dual-track agile: discovery and delivery run in parallel rather than in sequence.
Popularized by Teresa Torres in Continuous Discovery Habits, the approach counters the old model where research happens once at the start and the team then builds in the dark for months. Instead, a product trio — typically a product manager, designer, and engineer — talks to customers on a steady weekly cadence so insights arrive while there is still time to act on them.
The point is not interviews for their own sake but a tight link between learning and decisions. Teams map what they learn onto an opportunity solution tree, connecting a target outcome to the customer opportunities they could address and the solutions they might try, then run small assumption tests before committing to a build.
Continuous discovery pairs with dual-track agile: a discovery track surfaces and de-risks what to build while a delivery track ships validated work, the two running in parallel rather than in sequence. The discipline is consistency — a habit of small, frequent touches beats occasional large research projects.
In Planoda, discovery insights, opportunities, and the experiments testing them live alongside the delivery backlog, so learning and shipping stay connected on one surface.
Related terms
- Opportunity Solution TreeAn opportunity solution tree is a visual map, created by Teresa Torres, that connects a desired outcome at the top to the customer opportunities (unmet needs and pain points) beneath it, then to candidate solutions and the assumption tests that validate them. It keeps a team focused on outcomes and makes the reasoning behind product decisions explicit.
- Customer Journey MapA customer journey map is a visual representation of every step a customer takes to accomplish a goal with a product or company — across stages, touchpoints, channels, and over time. It captures what the customer does, thinks, and feels at each step, exposing friction, gaps, and moments of delight so teams can improve the end-to-end experience.
- Jobs to Be Done (JTBD)Jobs to Be Done is a framework for understanding why customers adopt a product: people "hire" products to make progress on a specific job in a given circumstance. It shifts focus from customer demographics and product features to the underlying goal — the job — revealing the real competition and the true criteria by which customers judge success.
- Product-Market FitProduct-market fit is the point at which a product satisfies a strong market demand — the right product serving the right market so well that growth begins to pull rather than push. It is the milestone before which a startup should focus on finding fit, and after which it should focus on scaling, often felt as demand outrunning the team's ability to keep up.
- Minimum Viable Product (MVP)A minimum viable product is the smallest version of a product that can be released to learn the most about customers with the least effort. Rather than building everything, a team ships just enough to test whether the core idea solves a real problem, then uses real-world feedback to decide what to build, change, or abandon next.