The Double Diamond: A Proven Framework for Design and Innovation
The double diamond is a design process model created by the British Design Council in 2005. It visualizes the design process as two connected diamonds representing four phases: Discover, Define, Develop, and Deliver. Each diamond pairs divergent thinking (exploring broadly) with convergent thinking (narrowing focus), guiding teams from problem exploration through to tested solutions. The first diamond ensures you solve the right problem; the second ensures you build the right solution.
Overview
The double diamond is one of the most widely recognized visual frameworks for structuring the design and innovation process. First formalized by the British Design Council in 2005 after studying the design practices of eleven global companies, the model maps the end-to-end journey from an initial challenge to a delivered solution. Its distinctive shape — two adjacent diamonds — communicates a powerful idea: great design requires alternating between opening up possibilities and narrowing down to decisions, and you must do this twice — once for the problem space and once for the solution space.
The first diamond covers Discover and Define. During Discover, teams cast a wide net through user research, stakeholder interviews, market analysis, and ethnographic observation. During Define, they synthesize those findings to articulate a clear problem statement or design brief. The second diamond covers Develop and Deliver. In Develop, teams generate a broad range of potential solutions through ideation, prototyping, and co-creation. In Deliver, they converge on refined solutions through testing, iteration, and implementation.
What makes the double diamond design process enduringly valuable is its simplicity and universality. It applies equally well to service design, product development, UX design, and organizational innovation. It doesn't prescribe specific tools or techniques — instead, it provides a thinking structure that helps teams avoid two of the most common design failures: solving the wrong problem, or jumping to solutions before understanding the problem deeply enough.
The British Design Council updated the framework in 2019 to include an outer layer of "design principles" — be people-centred, communicate visually, collaborate and co-create, and iterate relentlessly. This evolved version, sometimes called the Framework for Innovation, acknowledges that real design work is rarely as linear as two clean diamonds, but the core mental model remains an indispensable guide for teams navigating complexity.
How It Works
Step 1: Discover — Explore the Problem Space
Begin by casting a wide net to understand the world around the design challenge. Conduct user interviews, ethnographic observations, stakeholder workshops, desk research, and data analysis. The goal is **not** to find the answer — it's to build a rich, empathetic understanding of the people, contexts, and systems involved. Resist the urge to filter or judge what you find; embrace divergence and let unexpected insights emerge.
Step 2: Define — Frame the Right Problem
Synthesize everything gathered during Discover into a clear, actionable problem statement or design brief. Use techniques like affinity mapping, journey mapping, insight clustering, and "How Might We" framing to move from raw data to a focused definition of the challenge. This convergent phase ends the first diamond. The output should be a problem statement that the entire team agrees is worth solving.
Step 3: Develop — Generate and Explore Solutions
With a well-defined problem in hand, open up again into divergent thinking — this time in the solution space. Run brainstorming sessions, design sprints, co-creation workshops, and rapid prototyping exercises. Encourage wild ideas alongside pragmatic ones. Explore multiple solution directions rather than committing to the first idea. Build low-fidelity prototypes to make concepts tangible and testable.
Step 4: Deliver — Converge, Test, and Implement
Narrow down the solution options through user testing, feasibility analysis, and iterative refinement. Select the strongest concept(s), increase prototype fidelity, and validate with real users. Address technical and business constraints. This convergent phase closes the second diamond and results in a tested, refined solution ready for implementation, launch, or handoff to engineering.
When to Use
- When tackling a complex, ambiguous problem where the root cause is unclear and the team needs a structured way to explore the problem space before jumping to solutions.
- When launching a new product, service, or feature and you need to move from initial opportunity through research, ideation, and validated delivery in a systematic way.
- When aligning a cross-functional team (designers, engineers, product managers, stakeholders) around a shared process and vocabulary for design work.
- When you suspect your team is stuck in a pattern of solutioning without sufficient problem understanding, and you need a framework to enforce proper discovery and definition.
- When conducting a UX redesign or service improvement initiative and you want to ensure both the problem diagnosis and the solution are grounded in user research.
When Not to Use
- When the problem is already well-defined and validated — such as fixing a known bug or implementing a feature with clear specifications — and going through a full Discover/Define cycle would add unnecessary overhead.
- When you need to ship an emergency fix or respond to a time-critical production issue where speed of execution matters more than thorough exploration of the problem and solution spaces.
- When working on highly technical, engineering-driven tasks (like infrastructure migration or performance optimization) where the challenge is execution complexity rather than design ambiguity.
- When the team lacks the time, budget, or organizational support to conduct meaningful research in the Discover phase — a half-hearted double diamond process can create a false sense of rigor while producing shallow results.
Skills in This Method
Converging on Solutions in the Deliver Phase
How to evaluate, test, and iterate on concepts to select and refine the final solution for implementation in the Deliver phase.
Synthesizing Insights to Define the Problem
How to apply convergent thinking in the Define phase to analyze discovery findings, create problem statements, and narrow focus to the right challenge.
Facilitating Divergent Ideation in the Develop Phase
How to run structured brainstorming, co-design workshops, and prototyping sessions to generate a wide range of potential solutions in the second diamond.
Mapping Divergent and Convergent Thinking Modes
How to deliberately switch between expansive exploration and focused decision-making at each stage of the Double Diamond process.
Conducting Discovery Research in the Discover Phase
How to use divergent thinking techniques like user interviews, desk research, and observation to broadly explore the problem space in the first diamond.
Creating Double Diamond Process Diagrams
How to visually map your design process onto the Double Diamond diagram to communicate project phases, activities, and progress to stakeholders.
Choosing Between Double Diamond and Design Thinking
How to compare the Double Diamond with other design frameworks like Stanford d.school Design Thinking and Lean UX to select the right approach for your project.
Adapting the Double Diamond for UX Design Projects
How to apply the Double Diamond framework specifically to UX workflows, integrating user research, wireframing, usability testing, and iterative design.