In 30 seconds
- Discovery decides what to build; delivery builds it.
- Tests four risks: value, usability, feasibility, business viability.
- Runs continuously alongside delivery.
The four risks
| Risk | Question |
|---|---|
| Value | Will customers want it? |
| Usability | Can they figure out how to use it? |
| Feasibility | Can we build it? |
| Viability | Does it work for the business? |
This framing comes from Marty Cagan's book Inspired.
Common techniques
- Customer interviews and observation
- Prototypes tested with users
- Experiments such as fake-door tests
- Design thinking workshops
Discovery alongside delivery
Many teams run discovery and delivery in parallel, sometimes called dual-track agile. Discovery feeds validated ideas into the Product Backlog; delivery ships them.
Myth vs reality
Myth · Discovery is a phase before development.
Reality · It's continuous, alongside delivery.
Myth · Only product managers do discovery.
Reality · Product, design and engineering work together.
Myth · Discovery is slow.
Reality · Good discovery tests ideas in days, not months.
FAQ
How much time should go into discovery?
It varies; many teams keep a steady slice each week.
What's a product trio?
Product manager, designer and tech lead running discovery together.
When is an idea ready for delivery?
When its biggest risks have reasonable evidence.