Product Discovery Basics
Level 3 Β· Finding the right problem
What product discovery is, and the four risks it tests before any code is written. Why good teams keep doing it every week.
Course contentsLesson 5 of 13
Level 1 Β· The job
Level 2 Β· Where the product is going
Level 3 Β· Finding the right problem
Level 4 Β· Choosing what goes first
Level 5 Β· Shipping and measuring
After this lesson you can
- Name the four risks discovery tests
- Pick a cheap test for an idea
- Explain why discovery never stops
12 mincovers 4 glossary entries
Worth reading first: Product Requirements Document
How a team finds out what to build
Product discovery is the work of finding out what to build before building it. The team talks to users to learn their problems. Then it tests ideas cheaply, with sketches, mockups or a fake button. A test that takes two days can save two months of building the wrong thing.
Discovery checks four risks. Will people want it? Can they work out how to use it? Can the team build it with the time and skills it has? Does it work for the business, in cost, law and sales? An idea has to pass all four. Most ideas fail one of them early, which is the point.
The cheapest test is a talk with a user. Ask about the last time the problem came up, what they did and what it cost them. Ask about real past events, not what they might do one day. People are kind about ideas and honest about their own week.
The next step up is a prototype. It is a mockup you can click that looks real but has no code behind it. Five users trying one will find most of the confusing parts. Each test should answer one question. Write down before it starts what result would change your mind.
Discovery is not a phase done once at the start. Good teams keep doing it every week, next to the building. A small piece of time, a few user talks and a test or two, keeps the next round of building pointed at a real problem. Teams that stop find out at launch.
This sounds like customer discovery, and the two are close. Customer discovery asks if a whole business has a market, before there is a product. Product discovery asks which feature to build next, once there are users. A startup does the first one once. A product team does the second one all the time.
Worked example
Lucy's team drops a planner
Lucy's banking team plans a budget planner that would take 3 months to build. First they run five user talks and show a clickable mockup to 8 people.
Six of the 8 skip the planner and ask for an alert when spending jumps. The team builds alerts in 3 weeks, and the planner is dropped.
The words for this lesson4
Check yourself
What are the four risks product discovery tests?
Finished this lesson?
Marking it complete also marks its 4 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.