Framework⚡ Medium

Double Diamond

Diverge to explore, converge to define — twice. The Double Diamond separates finding the right problem from finding the right solution, with a deliberate expansion-and-contraction rhythm in each phase.

Product DiscoveryProblem FramingSolution DevelopmentStakeholder AlignmentSprint PlanningDesign Critique

01 — TL;DR

Two sentences.

The Double Diamond is a design process framework that structures work into two diamond shapes, each representing a diverge-then-converge cycle: the first diamond finds the right problem, the second finds the right solution. The model makes the expansion and contraction of thinking explicit — diverging means deliberately exploring widely before narrowing, and converging means making a deliberate commitment rather than drifting into a default.

Published by the British Design Council in 2005 as a visualisation of the design process they observed across eleven global companies, the Double Diamond is not a new methodology but a description of how good design work actually happens. Its value for product teams is in giving a shared vocabulary for the two most common process failures: converging too early on a solution before the problem is understood, and diverging again during solution development when the team should be committing to a direction.

02 — When to Use

Apply this when…

→Your team is debating whether to build a feature without having validated the underlying problem

→A project has stalled because stakeholders disagree about the problem definition

→You are reviewing a design and want to check whether both types of convergence have happened

→You are onboarding a new team to a project and need a shared mental model for the process phases

→A sprint retrospective reveals the team shipped something that did not solve the user problem

When NOT to apply it

Skip it when the problem is fully validated and the team is in pure execution mode. Also skip when your team is so small that formal process phases add friction without clarity, when the work is incremental improvement to a known interface, or when stakeholders expect the framework to prescribe specific methods rather than describe a rhythm.

03 — How It Works

The mechanism

The Double Diamond works by making two cognitive modes — expansive exploration and focused commitment — structurally visible and sequentially ordered. Most process failures happen because teams collapse these modes: they explore and commit simultaneously, which means they never explore broadly enough and never commit clearly enough.

Diverge-converge is how breakthrough thinking works

The Design Council's original research identified that all effective design work showed the same double-expansion pattern regardless of domain, team size, or methodology. The finding was not that teams should follow a process, but that they inevitably do — and the problems come when one of the four phases is collapsed or skipped.

Diamond one and diamond two are not interchangeable

Diamond one — Discover and Define — is about the problem space. It starts broad and ends narrow: a problem statement, a brief, a "How Might We." Diamond two — Develop and Deliver — is about the solution space. Skipping the second divergence — going directly from problem definition to a single solution — is the most common failure mode in product design.

The model is descriptive, not prescriptive

The Double Diamond does not tell you what methods to use, how long each phase should take, or how many people should be involved. Teams that fill it with mandatory activities have turned a mental model into a bureaucratic process. A two-day sprint can follow the pattern as effectively as a six-month research programme.

Evaluate each convergence point, not each phase

The critical moments are the two convergence points: the end of Define (committing to a problem) and the end of Deliver (committing to a solution). Both should produce a clear, explicit decision. "We are building X because we have validated that users need Y" is a clean double convergence. "We decided to add a filter because users complained" is a convergence that skipped the first diamond entirely.

Not a linear sequence

The Double Diamond is often misread as Discover → Define → Develop → Deliver in a straight line. It is not. It is two cycles, each with a mandatory expansion before a mandatory contraction. Teams can and should loop back from Develop to Discover if prototype testing reveals that the problem definition was wrong. The model permits — in fact, expects — iteration between the diamonds.

04 — Real Example

GOV.UK's transition from departmental structure to citizen-centred services

When the UK Government Digital Service was formed in 2011, it inherited government websites built around departmental structures rather than citizen needs. The first diamond was substantial: a discovery phase that mapped what citizens actually needed, producing a problem definition so different from the existing structure that the entire information architecture had to be reconceived.

The insight was that the first diamond's convergence — "citizens need to find services by task, not by department" — was so fundamental that it invalidated most of what had been built before. Every design decision in GOV.UK's celebrated design system traces back to that first convergence. Without a robust first diamond, the second diamond would have produced a better-looking version of the same departmental mess.

GOV.UK · Government Digital Service · 2011

First diamond convergence changes everything

First convergence → complete IA restructure

05 — In the Wild

Test yourself & see real examples

No examples yet — be the first.

Spotted a team that ran both diamonds properly — or one that built a polished solution to the wrong problem entirely? Submit what you observed.

✓ Reviewed before publishing✓ Your name on every example you submit✓ Violation or fix — both welcome

Seen the Double Diamond violated in a real product? Help grow the evidence base.

06 — Common Mistakes

Where teams go wrong

✗Treating the framework as four sequential phases rather than two cycles. Each diamond is a cycle with its own expansion and contraction — and the end of Deliver can feed back into the start of Discover. A Double Diamond that cannot loop is a waterfall with better graphics.

✗Skipping the second divergence. The most common failure is moving from Define directly into a single solution without a genuine ideation phase. The Develop phase exists because the right solution is rarely the first solution — and the only way to find it is to generate multiple competing approaches before committing to one.

✗Using the framework to justify work already decided. Teams sometimes run the Double Diamond after a solution has been selected — conducting research that confirms the chosen direction. This is process performance, not process discipline. The first diamond only produces value when its convergence is genuinely open.

✗Prescribing methods instead of protecting rhythm. Filling each phase with mandatory deliverables replaces a thinking rhythm with a compliance checklist. What matters is that expansion happens before contraction, and that both convergences produce clear, explicit commitments. The methods are context-dependent.

07 — Variations & Related Principles

Connected ideas

The Double Diamond sits alongside Design Thinking as a process framework — both describe the rhythm of good design work rather than prescribing specific tools.

The most important pairing is the Double Diamond with Design Thinking. They describe the same underlying process from different angles — the Double Diamond makes the rhythm visible, Design Thinking names the cognitive moves within it. Using both together gives teams both the structural frame and the specific mode-descriptions needed to guide practice.

08 — 10-Min Exercise

Run it right now

⏱ 10 minutes · Team · No prep

The Diamond Audit

1. Pick one feature or product decision from the last six months. Write down the problem statement that drove the work. If you cannot write one from memory, that is your first finding.

2. Assess the first diamond: did the team expand the problem space before committing — conducting research, exploring alternatives, challenging assumptions? Rate it: full, partial, or skipped.

3. Assess the second diamond: before committing to the solution, did the team generate and evaluate multiple competing approaches? Rate it: full, partial, or skipped.

4. Share the ratings. If either diamond was skipped or partial, identify at what point the team would need to re-enter to address the gap. That is the starting point for the next similar problem.

10 minutes