30 Second Overview
Discovery is often squeezed between sprints or sidelined by deadlines. But without structured discovery, teams risk building the wrong thing.
Great discovery is intentional, continuous, and focused on learning — not perfection. It informs smarter decisions and ensures delivery drives real value.
1: Discovery: What Success Looks Like
- Your discovery process is planned and timeboxed, not reactive.
- Hypotheses are defined and tested early with users.
- Learning is captured and shared across teams.
- Discovery runs alongside delivery, not in isolation.
- Teams use frameworks borrowed from design thinking (‘How might we?’, ‘Crazy 8s’ etc..) or user interviews.
2: Discovery Case Study
Monzo uses regular discovery sprints to explore user pain points before shaping their roadmap. One discovery sprint led to the creation of ‘Shared Tabs’ — a feature that increased retention in group users.
3: Discovery Step-by-Step
- Identify assumptions and gaps in knowledge.
- Design low cost experiments or tests (e.g. interviews, prototypes).
- Engage users early and get feedback before building.
- Synthesize insights into clear direction for delivery.
- Repeat discovery regularly to stay grounded in reality.
4: Discovery Checklist
- Discovery time is allocated in roadmap
- Clear hypotheses or questions defined
- Real users engaged for feedback
- Insights captured and reviewed
- Informs backlog and strategy
5: Discovery Pitfalls (and How to Avoid Them)
| Pitfall | Avoidance Strategy |
| No time for discovery | Make discovery a recurring activity, not a one-off effort |
| Too much research, too little action | Keep discovery focused and timeboxed |
| Insights not shared | Document and communicate what you’ve learned |
| Confusion between discovery and validation | Discovery is about learning; validation is about confirming assumptions |
6: Discovery FAQ
What’s the difference between discovery and delivery? Discovery is about learning what to build. Delivery is building it right.
How much time should we spend on discovery? Depends on the risk. Higher uncertainty means more discovery.
Who owns discovery? Led by product, but should involve design, engineering, and customers.
Can we do discovery in agile? Yes — through focussed discovery that feeds into sprints or integrated discovery sprints.
