What is Product Discovery?
Product discovery is the set of activities PMs, designers, and engineers do to decide what to build next. It answers four questions: Is this a real problem? Is our solution desirable to users? Is it technically feasible? Is it viable for the business?
Discovery is not a phase that happens once. In modern product teams, discovery happens continuously alongside delivery. While part of the team ships the current sprint's work, the product trio is validating what should go into future sprints.
Why Product Discovery Matters
The most expensive product mistake is building the wrong thing. Discovery prevents this by testing assumptions before you write code. A two-week discovery sprint that kills a bad idea saves three months of wasted engineering.
Discovery also produces better solutions. When you deeply understand the user's problem through research and testing, the solution you build fits more precisely. Users adopt it faster because it addresses their actual workflow, not your guess about their workflow.
How to Do Product Discovery
Start with the opportunity solution tree. Map your target outcome at the top, identify the opportunities (user needs) that could drive that outcome, and then generate multiple solution ideas for each opportunity.
Run weekly user interviews. Talk to at least one user or customer every week. Ask about their problems and workflows, not about feature requests. Continuous discovery habits keep you close to user reality.
Test before building. Use prototypes, fake door tests, Wizard of Oz tests, or landing pages to validate demand and usability. The goal is to learn as much as possible with as little engineering as possible.
Make evidence-based decisions. After running tests, compare results against your success criteria. Kill ideas that fail, iterate on ideas that show promise, and green-light ideas that pass all four risk tests.
Product Discovery in Practice
Teresa Torres popularized the continuous discovery framework used at companies like Hope Health, Snagajob, and Gartner. Teams conduct weekly interviews, run assumption tests, and make evidence-based decisions as a product trio.
At Spotify, discovery happens within squads. Each squad owns a user journey and runs continuous experiments to identify and validate improvements. Discovery is not a separate team or a separate phase.
Common Pitfalls
- Skipping discovery for "obvious" features. Even features that seem obvious benefit from validation. The devil is in the details.
- Discovery as a phase gate. If discovery is a month-long phase before development starts, it is too slow. Make it continuous.
- Only talking to existing users. Discovery should include non-users and churned users to understand why people leave or never adopt.
- Falling in love with solutions. Discovery should kill your bad ideas. If every idea passes, your tests are not rigorous enough.
Related Concepts
Product discovery is structured through the opportunity solution tree and continuous discovery habits. It involves user research, hypothesis testing, and prototyping. The product trio of PM, designer, and engineer collaborates on discovery.