Product Discovery
Product discovery is the work a product team does to decide what to build before committing to full delivery. The team studies customer needs, compares possible solutions, and tests risky assumptions so product decisions rest on evidence.
itEngineering leadership and delivery management | OpenSkills.info
Course pathWalk it in order
Look it upDip in anytime
Go furtherLeaves this page
Intro
Product Discovery
Product discovery is the work of deciding what to build. Product delivery is the separate work of building, shipping, and maintaining a production product. Discovery reduces uncertainty before a team makes an expensive delivery commitment. It does not eliminate uncertainty, predict demand with certainty, or replace judgment.
The discovery system
A useful discovery system connects five elements:
- A desired outcome defines the change the team is trying to influence.
- Customer evidence reveals needs, pain points, desires, and current behavior.
- An opportunity space organizes those customer needs without treating requested features as the problem definition.
- Several solution options propose different ways to address a selected opportunity.
- Assumption tests produce evidence about the risks inside those options.
The flow is iterative, not a stage gate. Evidence can change the opportunity map, invalidate a solution, or show that the outcome needs clarification. Delivery can also generate new evidence after release. Discovery and delivery therefore overlap, while retaining different purposes.
The people doing the work
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://www.producttalk.org/product-discovery/
Supports
- Product discovery decides what to build while product delivery builds, ships, and maintains it
- Product trios typically include product management, design, and engineering perspectives
- Continuous discovery uses recurring customer interviews and assumption testing
- Opportunities are customer needs, pain points, and desires
- Assumptions can be examined through prototypes, surveys, data analysis, and research spikes
- https://www.producttalk.org/getting-started-with-discovery/
Supports
- Continuous discovery uses at least weekly customer touchpoints by the product-building team
- Small research activities pursue a desired product outcome
- Discovery decides what to build and delivery builds it
- https://www.producttalk.org/opportunity-solution-trees/
Supports
- An opportunity solution tree connects a desired outcome to opportunities, solutions, and assumption tests
- Opportunities should be grounded in customer interviews rather than invented
- One tree is scoped to one product team's desired outcome
- Teams compare several solutions and test their underlying assumptions
- https://www.producttalk.org/glossary-discovery-assumption-testing/
Supports
- Assumption testing evaluates risk in underlying assumptions instead of whole ideas
- Prototype tests, one-question surveys, data mining, and research spikes answer different bounded questions
- Product assumptions include desirability, usability, feasibility, viability, and ethics
- https://www.svpg.com/four-big-risks/
Supports
- Product discovery addresses value, usability, feasibility, and viability risks
- Each risk represents a separate question rather than one general validation state
- https://www.designcouncil.org.uk/resources/the-double-diamond/history-of-the-double-diamond/
Supports
- The Double Diamond uses Discover, Define, Develop, and Deliver phases
- Divergent and convergent thinking recur across problem and solution work
- The Design Council began sharing the model in 2004
- https://learn.producttalk.org/home
Supports
- Product Talk Academy offers structured courses on continuous product discovery and opportunity solution trees
- https://github.com/sindresorhus/awesome
Supports
- The main Awesome index links to Awesome Product Management under Learn
- https://github.com/dend/awesome-product-management
Supports
- Discovery of Balsamiq and Figma as design and prototyping tools
- Discovery of Productboard and Screeb as feedback and research tools
- The list links Product Discovery Basics and story-based interview guidance
- https://balsamiq.com/product/
Supports
- Balsamiq provides low-fidelity wireframing for early product conversations
- https://www.figma.com/prototyping/
Supports
- Figma creates interactive prototypes and collaborative design flows
- https://www.productboard.com/product-discovery-tool/
Supports
- Productboard consolidates user inputs and feature ideas
- Productboard connects needs and strategic objectives to prioritization and roadmaps
- https://screeb.app/
Supports
- Screeb provides in-product research and customer feedback capabilities
- https://www.atlassian.com/software/jira/product-discovery
Supports
- Jira Product Discovery captures opportunities, feedback, and requests
- Fields and scoring compare ideas before connecting them to Jira delivery work
- https://dovetail.com/
Supports
- Dovetail centralizes customer signals and supports evidence-linked synthesis
- Product teams can organize interviews, support feedback, and research insights
- https://www.usertesting.com/platform
Supports
- UserTesting recruits audiences and gathers feedback on ideas, prototypes, and live experiences
- Its platform supports research analysis and sharing
- https://www.userinterviews.com/
Supports
- User Interviews recruits and manages participants for research studies
- https://maze.co/
Supports
- Maze supports moderated and unmoderated research on prototypes and live experiences
- https://sprig.com/
Supports
- Sprig supports surveys, interviews, and in-product research
- https://miro.com/product-overview/
Supports
- Miro provides a collaborative visual workspace for mapping and ideation