Product discovery

⏱ 5 min  ·  📅 2026

Product discovery is the continuous process of researching, validating, and learning about user problems and business opportunities before committing resources to building a solution. Its goal is not to define what to build: it is to reduce uncertainty about whether what is going to be built is worth building.

The term was popularized by Marty Cagan (Inspired, 2017) and Teresa Torres (Continuous Discovery Habits, 2021), who argue that discovery is not a phase prior to development but rather a continuous activity running in parallel with delivery.

Discovery vs. delivery

• Discovery: Which problem is worth solving? Will this solution work? Is it valuable to the user and viable for the business?
• Delivery: Building the agreed solution with quality and reliability.

The dual-track agile model proposes running both in parallel: while one track delivers the committed work, the other explores the opportunities for the next cycle.

The Discovery Cycle

Discovery follows an iterative flow:

1. Framing the problem: Separate the symptom from the root cause. Formulate the challenge from the user's perspective, rather than from the perspective of the solution. Tool: Jobs to Be Done.
2. Mapping assumptions: Explicitly list the assumptions upon which the solution depends. Classic categories include desirability, viability, and feasibility; Teresa Torres adds usability and ethics, while David Bland includes adaptability. These are prioritized using the importance vs. evidence matrix from Bland’s Assumptions Mapping: test the important assumptions that lack supporting evidence first. While it is common to start with desirability, the specific quadrant dictates the priority.
3. Designing the experiment: Choose the most efficient method to validate the most critical assumption—such as an interview, a prototype, a learning MVP, or an A/B test.
4. Evaluating the evidence: Analyze results with skepticism, distinguishing patterns from noise and correlation from causation. Evidence is stronger the more closely an observation resembles a real-world decision that carries a cost for the person making it: an opinion carries less weight than a sign-up, and a sign-up carries less weight than an actual payment.
5. Deciding: Persevere, iterate, pivot, or stop—capturing the learnings regardless of the outcome.

Common tools

• Interview snapshots to accumulate learning from user interviews.
• Opportunity solution tree to organize opportunities, solutions, and experiments.
• Story map to connect discovery with the backlog.
• Minimum viable product to validate hypotheses with minimum effort.

Common mistake

Treating discovery as a phase that is done at the start of the project and then closed. Torres's continuous discovery proposes a weekly cadence of user interviews as a steady practice, not as a one-off activity. Markets change and product hypotheses become invalid. A team that did discovery six months ago and has spent months in pure delivery is building up the risk of misalignment with the user's real needs.

Resources

🏦 Customer discovery and validationState of the art and guide · Skill Arena

📄 Product Owner v.2.0 [in Spanish]Free download · Scrum Manager

References

• Cagan, Marty. (2017). Inspired: How to Create Tech Products Customers Love. Wiley.
• Torres, Teresa. (2021). Continuous Discovery Habits. Product Talk LLC.

See also

Jobs to Be Done Opportunity solution tree Minimum viable product Interview snapshot User story Product Owner OKR Feature factory

Want to advance in agility? You can search for course and exam calls or go at your own pace by becoming a member of the Agile Club. This membership includes exclusive resources, e-learning classrooms, and access to Skill Arena: a space to practice and measure your agile skills at your own pace.

Search calls

Agile Club