What is Product Discovery?
Product discovery is the set of activities a team uses to decide what to build, as opposed to delivery, which is building it well. The goal is to reduce risk by validating ideas before committing significant engineering effort — answering whether customers want it (value), can use it (usability), the team can build it (feasibility), and it works for the business (viability).
Discovery is continuous, not a one-time phase. Modern practice (championed by Teresa Torres and Marty Cagan) favors lightweight, frequent experiments — customer interviews, prototypes, and tests — running in parallel with delivery, rather than a big upfront research project.
PMs lead discovery alongside design and engineering (the "product trio"). Strong discovery is what separates teams that ship the right things from "feature factories" that ship lots of things nobody uses. It's where prioritization decisions earn their evidence.
Examples
- A trio runs weekly customer interviews and tests a prototype before adding a feature to the roadmap.
- A PM kills a planned feature after discovery reveals users don't actually have the assumed problem.
Where PMs use this
Related terms
Minimum Viable Product (MVP)
The simplest version of a product that delivers enough value to learn from real users.
Usability Testing
Observing real users attempting tasks with a product to uncover where they struggle.
User Persona
A fictional, research-based archetype representing a key segment of a product's users.
Product-Market Fit
The point at which a product satisfies strong market demand — the prerequisite for scalable growth.
Prioritization
The discipline of deciding what to work on next by weighing value, effort, and strategic fit.