Discovery & customer understanding · Process model
Double Diamond
Diverge and converge twice so a team frames the right problem before refining a solution.
Start here · 5-minute visual lesson
First choose the right problem. Then choose the right solution. Both choices require opening up before narrowing down.
Think of it like this: A doctor diagnosing before prescribing: explore symptoms, identify the cause, consider treatments, then test one safely.
- 1Explore the situation
- 2Define the real challenge
- 3Create different answers
- 4Test and deliver
“Customers miss appointments, so send more reminders.” The team commits before it understands why.
“When plans change, patients cannot recover.” The team tests rescheduling, caregiver help, and call-back options.
Learn by deciding
The reminder that was not the answer
A clinic asks for more appointment reminders. What should happen first?
Do not design the reminder yet. Discover when appointments are missed, who is affected, and what people tried to do.
Interviews show reminders are seen, but rescheduling is confusing. What changes?
Converge on a new problem: help patients recover when plans change—not “improve reminders.”
Three ideas test well enough to prototype. What is the final move?
Deliver a narrow pilot with a success measure and a guardrail, then loop back if the outcome does not move.
01 · Understand
In plain English
A four-stage map—Discover, Define, Develop, Deliver—that makes problem exploration as explicit as solution creation.
Origin and context
The UK Design Council introduced the Double Diamond in 2004 and later placed it inside its broader Framework for Innovation. The diamonds visualize alternating divergent and convergent thinking; they are not a rigid waterfall.
The problem it solves
Teams often converge on the first plausible solution before they understand the situation. The model protects time for broad evidence gathering, a clear problem definition, multiple solutions, and iterative delivery.
The concepts, explained
Learn the vocabulary first. Each concept changes a decision you will make when using the framework.
Discover
Open up the problem space. Observe people, review evidence, and look beyond the original brief so the team understands what is really happening.
Define
Turn scattered evidence into a focused challenge. Choose which problem matters, who experiences it, and what change would count as progress.
Develop
Open up the solution space. Create genuinely different ways to address the defined problem instead of polishing the first idea.
Deliver
Narrow through evidence. Prototype, test, improve, and release the smallest solution that can prove whether the direction works.
02 · Deep dive
Go beyond the definition
Follow the reasoning inside Double Diamond, then challenge it before you use it.
1 of 4mental model
The mental model
What changes in the way you see the problem
Discover
widen the evidence base
Define
synthesize and choose the challenge
Develop
create and compare alternatives
Deliver
test, improve, and release
Reasoning trace
Watch each step earn the next one
A telehealth team begins with “add appointment reminders.” Discovery shows missed appointments cluster among patients who cannot confidently reschedule. The team defines the challenge as “help patients recover when plans change.” It develops SMS rescheduling, delegated caregiver controls, and a call-back queue. Five task tests favor SMS rescheduling. A pilot targets a reduction in no-shows from 18% to 13% while watching staff workload.
- 01Frame
Write the initial challenge as a question, not a feature request.
Decision question: Where are we converging from opinion rather than evidence? - 02Interrogate
Observe affected people and collect qualitative and quantitative evidence.
Decision question: What evidence would force us to redefine the challenge? - 03Interrogate
Cluster evidence; expose tensions, exclusions, and assumptions.
Decision question: Where are we converging from opinion rather than evidence? - 04Interrogate
Choose a focused problem statement and success evidence.
Decision question: What evidence would force us to redefine the challenge? - 05Interrogate
Generate several materially different solution directions.
Decision question: Where are we converging from opinion rather than evidence? - 06Interrogate
Prototype the riskiest parts and test with realistic tasks.
Decision question: What evidence would force us to redefine the challenge? - 07Decide
Select, ship narrowly, measure, and feed learning into another loop.
Decision question: Where are we converging from opinion rather than evidence?
Failure-mode lab
Which mistake is most likely on your team?
Choose one to turn it into a control for your next workshop.
Context adaptation
The canonical version is only a starting point
Startups can run a two-day micro-diamond around one risky assumption; enterprises can nest diamonds across portfolio and service layers. B2B teams include buyer, admin, and user evidence; marketplaces map both sides.
Signals it fits
- The requested solution may hide a poorly framed problem
- Different disciplines need a shared discovery map
- The cost of solving the wrong problem is high
Signals to switch tools
- The problem and remedy are already understood and reversible
- A safety incident requires immediate containment
- The team treats stages as approval gates
Now use the framework. The workbench below turns your own context into a first decision draft.
Work my problem03 · Apply
How to use Double Diamond
- 01
Write the initial challenge as a question, not a feature request.
- 02
Observe affected people and collect qualitative and quantitative evidence.
- 03
Cluster evidence; expose tensions, exclusions, and assumptions.
- 04
Choose a focused problem statement and success evidence.
- 05
Generate several materially different solution directions.
- 06
Prototype the riskiest parts and test with realistic tasks.
- 07
Select, ship narrowly, measure, and feed learning into another loop.
04 · See it work
A worked example
A telehealth team begins with “add appointment reminders.” Discovery shows missed appointments cluster among patients who cannot confidently reschedule. The team defines the challenge as “help patients recover when plans change.” It develops SMS rescheduling, delegated caregiver controls, and a call-back queue. Five task tests favor SMS rescheduling. A pilot targets a reduction in no-shows from 18% to 13% while watching staff workload.
Business case study
Illustrative fictional scenario
A regional clinic product team uses interviews, cancellation logs, and a service blueprint to reframe a reminder request. The resulting small pilot tests a rescheduling workflow rather than adding more notifications. All figures are invented for practice.
Across company types
Startups can run a two-day micro-diamond around one risky assumption; enterprises can nest diamonds across portfolio and service layers. B2B teams include buyer, admin, and user evidence; marketplaces map both sides.
05 · Work your problem
Turn the framework into a result
Explore the mechanics
Copy the working template
Challenge: Evidence to gather: Discover themes: Defined problem: Solution directions (3+): Prototype evidence: Delivery measure:
06 · Use judgment
Where it helps—and where it breaks
Use when
- The requested solution may hide a poorly framed problem
- Different disciplines need a shared discovery map
- The cost of solving the wrong problem is high
Do not use when
- The problem and remedy are already understood and reversible
- A safety incident requires immediate containment
- The team treats stages as approval gates
Advantages
- Memorable shared language
- Balances problem and solution exploration
- Supports iteration at multiple scales
Limitations & criticisms
- Says little about which research method to choose
- Can look linear when real work loops
- A diamond does not guarantee good evidence
Common failure modes
- Skipping Discover because a stakeholder supplied a brief
- Choosing one solution before Develop
- Calling a launch “Deliver” without learning measures
Often confused with
Design Thinking is a broader family of human-centered mindsets and methods; Double Diamond is a visual process map.
Practical checklist
Reflection questions
- Where are we converging from opinion rather than evidence?
- What evidence would force us to redefine the challenge?
07 · Check
Five-question knowledge check
Key takeaways
- Diverge and converge twice so a team frames the right problem before refining a solution.
- Memorable shared language
- Says little about which research method to choose
08 · Go deeper
Sources and further reading
- Framework for InnovationDesign Council · Design Council · 2019
Double Diamond history, four stages, and divergent/convergent structure.
- The Double DiamondDesign Council · Design Council
Direct visual and plain-language description of the Double Diamond design and innovation process.