Double Diamond Model: The Complete Guide to Smarter Problem-Solving
Most teams don’t fail because they build the wrong solution. They fail because they solve the wrong problem.
The Double Diamond Model is the antidote. Developed by the British Design Council, it’s one of the most widely adopted design thinking frameworks in the world — used by teams at Apple, Microsoft, LEGO, Starbucks, and Sony to move from fuzzy challenge to confident, user-centered solution.
This guide breaks down every phase of the Double Diamond, explains the thinking behind it, and shows you how to put it to work on your next project.
What Is the Double Diamond Model?
The Double Diamond is a visual framework that maps the design process into two connected diamond shapes. Each diamond represents a cycle of divergent thinking (exploring broadly) followed by convergent thinking (narrowing to a decision).
- Diamond 1 — Problem space: Discover the landscape, then Define the core problem.
- Diamond 2 — Solution space: Develop possible solutions, then Deliver the best one.
The model was formalized by the British Design Council in 2004–2005 after studying the design processes of eleven leading global companies. The underlying divergent-convergent pattern draws on decades of creative problem-solving research, including work by Sidney Parnes, Alex Osborn, and Béla H. Bánáthy.
Its enduring appeal comes from a simple but powerful insight: the problem is just as important as the solution. Skipping straight to “how do we fix this?” almost always produces solutions that miss the mark.
The 4 Phases of the Double Diamond
Phase 1: Discover (Diverge)
The first phase is about opening up — resisting the urge to jump to answers and instead immersing yourself in the problem space.
Teams conduct user interviews, ethnographic observation, surveys, stakeholder workshops, and desk research. The goal is to gather raw insight into what people actually experience, feel, and need — not what your team assumes they need.
Key activities:
- User interviews and contextual inquiry
- Competitor and market analysis
- Surveys and analytics review
- Collaborative workshops with cross-functional teams
Outcome: A rich body of evidence about the real-world problem landscape.
Phase 2: Define (Converge)
Now you synthesize. All the research gathered in Discover gets analyzed, themed, and distilled into a sharp problem statement.
This is the most underestimated phase of the Double Diamond. Teams often rush it. But a well-crafted problem definition — grounded in evidence, not opinion — is the foundation everything else is built on. A useful prompt here is the “How Might We?” question format, which reframes challenges as opportunities without prescribing solutions.
Key activities:
- Affinity mapping and thematic analysis
- User persona and journey mapping
- Point-of-view (POV) or problem statement writing
- “How Might We?” framing exercises
Outcome: A clear, agreed-upon problem statement that the whole team can align around.
Phase 3: Develop (Diverge)
With the right problem defined, the second diamond opens up again — this time around solutions.
Teams brainstorm broadly, sketch concepts, and build low-fidelity prototypes. The goal is creative volume: generating many possible answers before committing to any of them. Co-design sessions with users and stakeholders are especially valuable here, as external perspectives break internal assumptions.
Key activities:
- Brainstorming and ideation workshops
- Sketching, wireframing, and concept development
- User co-design sessions
- Low-fidelity prototyping
Outcome: A range of candidate solutions, stress-tested against user needs.
Phase 4: Deliver (Converge)
The final phase narrows the solution space to the best option and brings it to life. Teams refine prototypes, conduct usability testing, iterate based on feedback, and prepare for launch.
Get Aditya Raj’s stories in your inbox
Join Medium for free to get updates from this writer.
Delivery doesn’t mean “done.” Most mature teams treat launch as the start of a learning loop — monitoring real-world behavior and feeding insights back into future discovery cycles.
Key activities:
- High-fidelity prototyping and usability testing
- Developer handoff and QA
- Launch and post-launch monitoring
- Feedback collection for future iteration
Outcome: A tested, refined solution ready for real users.
The Core Principles Behind the Model
The British Design Council updated the Double Diamond in 2019 to make its underlying principles explicit. Four principles guide how teams should work within the framework:
- Put people first. Deeply understand the needs, aspirations, and challenges of the people you’re designing for.
- Communicate visually and inclusively. Use visual tools to build shared understanding across your team.
- Collaborate and co-create. Bring in diverse perspectives — including end users — throughout the process.
- Iterate, don’t perfect. Test frequently to reduce risk and build confidence in your decisions.
These aren’t just values — they’re what separates teams who use the Double Diamond as a checklist from those who use it as a genuine compass.
Double Diamond vs. Design Thinking
The Double Diamond is often compared to the five-stage Design Thinking model popularized by IDEO and Stanford’s d.school (Empathize, Define, Ideate, Prototype, Test). Both frameworks cover similar ground — human-centered research, problem framing, ideation, and testing.
The key difference is structural. Design Thinking is presented as five sequential stages. The Double Diamond makes the diverge-converge rhythm explicit with its visual shape, and it cleanly separates problem exploration from solution exploration into two distinct phases. In practice, many teams blend both frameworks, using the Double Diamond as an overarching structure while drawing on specific Design Thinking tools within each phase.
Double Diamond + Agile: A Powerful Combination
The Double Diamond and agile methodologies are complementary, not competing. Many product teams use the Double Diamond for strategic direction while running agile sprints for execution.
The first diamond’s research and problem definition work feeds directly into a product backlog. The second diamond’s Develop and Deliver phases map naturally to sprint cycles — where teams prototype, test, and iterate in short loops. The Double Diamond gives you the “what and why”; agile gives you the “how and when.”
Real-World Example: A Mobile Banking App Redesign
Here’s how the Double Diamond plays out in a real UX context:
Discover: The UX team interviews current app users, reviews support tickets, and analyzes drop-off data. They find users frequently abandon the transfer flow mid-task.
Define: Synthesizing the research, they identify the core problem: users don’t trust the confirmation step because the language is ambiguous and the visual feedback is unclear. They write a problem statement: “How might we make users feel confident that their transfer was completed correctly?”
Develop: The team brainstorms and sketches eight different approaches to the confirmation screen — ranging from animated checkmarks to detailed transaction summaries. Three concepts go into low-fi prototypes.
Deliver: Usability testing with 12 participants reveals one design is significantly clearer. The team refines it, hands off to engineering, and ships. Post-launch, transfer completion rates increase by 18%.
Common Mistakes Teams Make with the Double Diamond
- Rushing Define. The pressure to “get to solutions” causes teams to skip rigorous synthesis. The result: a well-executed answer to the wrong question.
- Treating it as linear. The model looks sequential on paper, but real design work is iterative. Findings in Develop often send teams back to Define — and that’s healthy.
- Skipping co-design. The framework explicitly calls for collaboration with users and diverse stakeholders, not just internal brainstorming.
- Conflating Discover and Define. Research and synthesis are different cognitive modes. Keeping them separate prevents premature conclusions from contaminating raw data.
Who Should Use the Double Diamond?
The Double Diamond isn’t just for designers. Any role involved in solving complex, ambiguous problems benefits from the framework:
- UX and product designers building digital products
- Product managers aligning teams around the right problems to solve
- Service designers reimagining customer journeys
- Innovation and strategy teams exploring new markets or business models
- Non-profits and public sector organizations designing interventions and policies
If your work involves uncertainty about what problem to solve, and who you’re solving it for, the Double Diamond is relevant.
Whether you’re redesigning a checkout flow or rethinking a public service, the Double Diamond gives you the structure to do it right.
PhaseRecommended ToolsDiscoverUser interview guides, observation frameworks, competitor matricesDefineAffinity maps, journey maps, problem statement templates, HMW boardsDevelopBrainstorming canvases, wireframe kits, rapid prototyping tools (Figma, Miro)DeliverUsability test scripts, QA checklists, launch monitoring dashboards
