Product Discovery

Product discovery is the practice of validating problems, opportunities, and solutions with customers and data before committing engineering effort to build them. It is distinguished from product delivery (the act of designing, building, and shipping) and aimed at killing bad ideas cheaply so the team only builds things likely to drive the intended outcome. It is the front half of modern product work, and the part most under-invested in by startups that mistake speed of shipping for speed of learning.

The discipline was popularized in its modern form by Marty Cagan, especially in Inspired (2008/2017) and Empowered (2020), with the core argument that great product teams discover what to build before they decide to build it, using a mix of qualitative methods (customer interviews, usability testing on prototypes, story-mapping) and quantitative methods (analytics, A/B tests, prop modeling). Teresa Torres's Continuous Discovery Habits (2021) operationalized the practice for modern PM teams: at least one customer touchpoint per week, opportunity solution trees mapping opportunities to assumption tests, and discovery as an ongoing rhythm rather than a project. The standard discovery toolkit includes customer interviews (the foundational method, typically 30 minutes, story-based questions about past behavior rather than hypothetical future intent), opportunity sizing (estimating how often the problem occurs, how painful it is, how many customers feel it), assumption mapping (listing the desirability / usability / feasibility / viability assumptions each idea depends on, then designing the cheapest test for the riskiest assumption), prototyping (clickable wireframes or smoke tests to validate solution direction before committing engineering), and A/B and usability testing on live or near-live product. The single best diagnostic of a discovery-led team versus a delivery-only team: how often does the team kill an in-flight idea based on discovery learning? If the answer is "rarely," discovery is theater.

What founders get wrong: Skipping discovery because the team "already knows what to build." Founders pattern-match from their own experience and assume the team can do the same. The team usually can't, because the team doesn't have the founder's customer intuition, and the founder's intuition usually has more gaps than they admit. Discovery exists to make the team's evidence as strong as the founder's instinct, and to catch the cases where the founder's instinct is wrong.

Related: Product Management · Continuous Discovery · User Research · Prototype · Product Market Fit

FAQ

What is product discovery?
The practice of validating problems, opportunities, and solutions with customers and data before committing engineering effort. Distinguished from product delivery (the actual build), and aimed at killing bad ideas cheaply so the team only builds things likely to drive the intended outcome.

Who popularized product discovery?
Marty Cagan, in Inspired (2008/2017) and Empowered (2020). Teresa Torres operationalized continuous discovery for modern PM teams in Continuous Discovery Habits (2021), introducing weekly customer touchpoints and opportunity solution trees as standard practice.

How is product discovery different from product delivery?
Discovery is the front half of product work: validating that an idea is worth building. Delivery is the back half: actually designing, building, and shipping the thing. Discovery-led teams kill ideas before they become features; delivery-only teams build everything and find out later which features were worth it.