Image 1 of 1
Playbook 02 · Lead Designer Series
Discovery as risk reduction — not research theatre.
Overview
Discovery gets cut. Not because organisations don't value it, but because it rarely produces anything that changes what gets built. Insight decks are presented, themes are named, and then the roadmap proceeds largely as planned. That pattern has a name: insight theatre.
This playbook reframes discovery entirely — from a research process that produces knowledge to a risk-reduction engine that produces decisions. The difference changes what you do in every session, how you communicate findings to product and engineering, and how you know when to stop discovering and start building.
Written for designers who run discovery inside organisations where time is constrained, stakeholders are sceptical, and the bar for stopping a roadmap is high.
The goal of discovery is not to understand users better. The goal is to reduce the cost of being wrong.
What's Inside
| Section | What it covers |
|---|---|
| Chapter 01 | What Discovery Actually Is The shift from validated learning to risk reduction — and the four things discovery can never tell you |
| Chapter 02 | The Scoping Stack A five-step sequence for scoping problems without a proper brief — including how to handle the three ambiguous mandate types organisations actually give you |
| Chapter 03 | The Discovery Risk Radar The Signature Framework — categorising risk across Value, Usability, Feasibility, and Viability; two-stage usage methodology; the viability blind spot most teams miss |
| Chapter 04 | The Assumption-Mapping Session A four-phase cross-functional facilitation guide; the Assumption Ledger with worked examples; handling political assumptions without losing the room |
| Chapter 05 | Interviews That Generate Insight, Not Noise The Insight-to-Action interview structure; the analysis discipline rule; the commercial stakeholder presentation format for findings |
| Chapter 06 | Framing Findings for Product and Engineering The PM translation framework; the spike proposal format; the five-point discovery output document that replaces the research deck |
| Chapter 07 | Exit Criteria — When to Stop Discovering How to design exit criteria before discovery starts; worked examples across all four risk quadrants; the three-option response when criteria can't be met |
| Chapter 08 | Discovery at Three Speeds Sprint configurations for 2-day, 2-week, and 6-month discovery — day-by-day breakdowns and a Radar adaptation table for each mode |
| Appendix | Working Templates The Discovery Risk Radar as a standalone tool; the Assumption Ledger; the Discovery Sign-Off document; the five-point output structure |
Signature Framework
The Discovery Risk Radar
A four-quadrant risk categorisation model covering Value, Usability, Feasibility, and Viability. Used at the start of every discovery engagement to determine where the real risk sits — and which quadrant to reduce first. Included as a standalone working template with a two-stage usage guide.
This playbook is for you if
- You're a senior designer or design lead responsible for running discovery inside product teams
- Your research produces insight decks that don't change what gets built
- You're working in a time-constrained environment where discovery needs to earn its place on the roadmap
- Stakeholders are sceptical about research and you need a commercial frame to justify the process
- You want a structured methodology, not a set of research methods