Product discovery
Last reviewed
Product discovery is the work of deciding what to build and why, as distinct from delivery, which is building it well. It covers understanding customer problems, generating solution options and testing the assumptions behind them. An Opportunity Solution Tree is a way of making the state of that work visible.
Discovery and delivery run together
Discovery is not a phase that finishes before delivery starts. In teams that work this way, both run continuously and feed each other: delivery produces usage data and new questions, discovery decides what is worth building next. Treating discovery as a gate at the start of a project reintroduces the waterfall the practice was meant to replace.
The product trio
Discovery is usually described as the work of a trio: a product manager, a designer and an engineer, deciding together. The composition matters because the three roles surface different risks. A trio catches feasibility problems while the idea is still cheap to change, and a designer in the room from the start prevents usability from being discovered after launch.
Frequently asked questions
What is the difference between product discovery and delivery?
Discovery answers what to build and why; delivery answers how to build it well. Discovery reduces the risk of building the wrong thing, delivery reduces the risk of building the thing badly. Both run continuously rather than in sequence.
Who takes part in product discovery?
Typically a product trio: a product manager, a designer and an engineer working together. Each role surfaces a different category of risk, and having all three present means feasibility and usability problems appear while the idea is still cheap to change.
Related terms
- Continuous discoveryContinuous discovery is the habit of maintaining at least weekly customer touchpoints, run by the team building the product, in pursuit of a desired outcome.
- OutcomeAn outcome is a measurable change in customer or business behaviour that a product team commits to creating.
- Assumption testingAssumption testing is the practice of identifying the beliefs a solution depends on and checking the riskiest ones with small tests before building.
See how product discovery fits the whole tree
The full guide covers all four layers and how they connect.