Product discovery is the work of reducing uncertainty about which customer problems to address and which solutions are worth pursuing. Teams use research, prototypes, and assumption tests to make decisions before committing substantial delivery effort. Discovery can continue as the product is built and used.
What do teams learn in discovery?
Start with the outcome you want to improve and the decisions you need to make. Marty Cagan describes four risks: whether customers will value the solution, whether they can use it, whether the team can build it, and whether it works for the business.
Choose evidence that fits the risk. A prototype can show whether users understand an interaction. A technical investigation can establish whether the proposed behavior is feasible. Interview findings can explain why a problem matters and help the team decide which solutions to explore.
Example: helping accounts send their first invoice
An invoicing team sees that many new accounts create drafts but few send a first real invoice. The team wants more eligible new accounts to send a first real invoice within seven days of signup.
| Discovery question | What the team does |
|---|---|
| Why do people hesitate? | Observe people preparing a real invoice and ask about the last time they stopped before sending. |
| Would a preview help? | Show a prototype that lets users see the client’s view. Ask them to explain what the client would receive and when. |
| Can the preview reflect the actual invoice? | Check with engineering that the preview and the final invoice use the same data and render consistently. |
| Is it worth supporting? | Estimate what it will cost to maintain accurate previews across invoice templates. Compare that effort with the value of helping more accounts send correctly. |
If the evidence supports the preview, the team can build it and evaluate whether it changes the share of new accounts sending a real invoice. Use usability sessions to check comprehension, then consider a randomized test to estimate the effect on activation if traffic supports one.
How does discovery fit with delivery?
Keep the next important assumption visible while delivery proceeds. Teresa Torres’s continuous discovery approach advocates at least weekly customer contact by the team building the product and small research activities tied to a desired outcome. A team can start by recording the decision, the evidence that informed it, and what would change its mind.