Skip to content
Module
Product and data

Product discovery: definition and method

Product discovery covers the activities a team uses to decide what to build before committing engineering time: understanding user problems, exploring solutions and testing the riskiest assumptions. Marty Cagan describes it as reducing four risks: value, usability, feasibility and viability for the business. Teresa Torres popularized continuous discovery, carried out every week rather than as a separate phase.

Definition written by Alex Dionisio, Senior Product Manager. Updated November 13, 2026.

Why it matters for a PM

Most product ideas do not deliver the hoped-for result, and engineering is the most expensive way to find that out. Discovery lets a PM rule out weak ideas cheaply, reach development with evidence in hand and defend choices more convincingly when stakeholders push their own requests.

Example

A team keeps hearing requests for a customizable dashboard. Six interviews reveal that users mostly want to know every Monday which clients are late on payments. A clickable prototype of a simple weekly summary is tested with five customers, who strongly prefer it to the dashboard first imagined.

Key points

  • Start from a stated problem and a target outcome, not from a solution already chosen.
  • Talk to users regularly, asking about past behavior rather than future intentions.
  • Identify the riskiest assumption and test it first, as cheaply as possible.
  • Involve design and engineering in discovery, not just the PM.

Common mistakes

  • Running interviews to confirm an idea rather than to learn.
  • Treating discovery as a one-off phase before a long delivery tunnel.
  • Confusing what users ask for with the problem they are trying to solve.

Go further with Module

The courses and lessons that cover this concept:

Guide on this topic