A design process model that visualizes four phases: Discover, Define, Develop, and Deliver. The two diamonds represent divergent and convergent thinking — first expanding to understand the problem space, then narrowing to define the problem, then expanding to generate solutions, then narrowing to deliver.
Common contexts
- Running a workshop to align a cross-functional team on which phase of the process they're currently in
- Explaining to a stakeholder why the team is still exploring problem framing rather than presenting design options
- Structuring a project timeline to ensure adequate divergent thinking before solution commitment
Use when
When facilitating a team that tends to jump directly to solutions, or when you need a shared framework to communicate project phase, resource allocation, and expected outputs to non-design stakeholders.
Avoid when
Don't treat the double diamond as a literal sequential checklist — real projects loop, backtrack, and skip phases depending on confidence and risk, and forcing the model onto every project creates bureaucratic overhead.
The most neglected part of the double diamond is the first convergence — defining the right problem with the same rigor as delivering the solution is where most design teams take shortcuts, and where most expensive mistakes are made.
Real-world examples
- The UK Design Council, which created the Double Diamond model, applied it to redesign public services including reducing reoffending rates by reframing the problem before jumping to solutions.
- IDEO uses a process closely aligned with the Double Diamond—diverging to explore problems broadly before converging on insights, then diverging again on solutions—across all client engagements.
- The BBC's UX design teams use the Double Diamond framework to structure large-scale projects, ensuring teams spend sufficient time in the 'Discover' and 'Define' phases before designing solutions.