Double Diamond Workflow¶

A macro design process — instantiates Divergence-Convergence Cycle Orchestration

Runs two diverge-then-converge diamonds in series — the first to reframe and define the right problem, the second to develop and deliver a solution — so a team can't skip straight to answering the wrong question.

Where most of its siblings are single beats of divergence and convergence, Double Diamond Workflow is the macro shape that chains two of them and insists on their order. The first diamond opens up the problem (explore widely what's really going on) and then closes on a sharp problem definition; only then does the second diamond open up solutions and close on one to deliver. Its defining commitment is the boundary in the middle: you must reframe and define the right problem before generating solutions to it. That single constraint is what separates it from a one-diamond workshop — it refuses the near-universal reflex of treating the first plausible problem statement as settled and racing to solutions.

Example¶

A government agency's online benefits application has a soaring drop-off rate, and the obvious project is "redesign the form." The Double Diamond stops that reflex. Diamond one — discover (diverge): the team studies where applicants actually stall — call logs, session recordings, interviews — and finds most abandonment happens before the form, at an eligibility step nobody can understand. Diamond one — define (converge): the challenge is reframed from "redesign the form" to "help people find out if they qualify before they invest an hour." That reframed problem is the commitment the first diamond exists to produce. Diamond two — develop (diverge): the team generates ways to deliver early eligibility clarity — a pre-check, a plain-language wizard, a phone-first path. Diamond two — deliver (converge): one is built, piloted in a single region, and rolled out only after it holds.

Had they run a single diamond, they'd have built a beautiful version of the wrong form. The middle boundary is what saved the project.

How it works¶

What distinguishes it from a single diverge-converge cycle:

Two diamonds, fixed order. Problem space is explored and defined first; solution space is opened only after the problem is committed. Solutioning before the first diamond closes is treated as an error.
Each diamond is a full diverge-then-converge. Both halves get genuine expansion and genuine narrowing — the workflow doesn't shortcut breadth in either.
The middle is a real commitment. The defined problem is an explicit, reversible commitment that the second diamond is accountable to.
Delivery is staged. The final convergence lands through pilot-then-roll-out, so the solution commitment deepens with evidence rather than launching all at once.

Tuning parameters¶

Problem-diamond depth — how much time goes into discovering and reframing before solutioning is allowed. Deeper reframing catches wrong-problem errors but delays visible progress and tests stakeholder patience.
Boundary firmness — how strictly solutioning is forbidden until the problem is defined. A hard boundary prevents premature answers; a soft one lets a team backtrack if discovery reveals the frame was wrong.
Iteration between diamonds — whether the process is a strict one-pass sequence or loops back when the second diamond exposes a bad problem definition. Looping is more honest but less tidy to plan and budget.
Delivery staging depth — how many pilot rungs precede full commitment. More rungs de-risk the launch but slow it.

When it helps, and when it misleads¶

Its strength is structural: by giving the problem its own full diverge-converge cycle, it defends against the most expensive design error — solving the wrong problem well. Popularized as the Double Diamond by the UK Design Council, it has become the default macro-frame for service and product design precisely because the middle boundary makes "are we sure this is the problem?" a required step rather than a nag.^[1]

Its failure mode is being run as a rigid waterfall: teams treat the four phases as strictly linear gates and lose the iteration the model actually intends, so a bad problem definition can't be revisited once the second diamond starts. It can also become ceremony — dutifully drawing two diamonds while skimping the real divergence in each, especially the uncomfortable problem-space exploration. And it says nothing about how to generate or score within a diamond; it is a container, not a technique. The discipline that keeps it honest is treating the middle definition as reversible, allowing loop-backs when the solution diamond reveals a mis-framed problem, and filling each diamond with real generation and selection mechanisms rather than performing the shape.

How it implements the components¶

The Double Diamond owns the macro-framing and staged-commitment machinery — it structures the whole lifecycle and hands the in-phase work to other mechanisms:

challenge_scope_frame — the first diamond's discover phase is precisely the act of establishing, then widening, what is actually in scope before anything is fixed.
cycle_objective_and_decision_horizon — the define phase produces the sharp problem statement that sets what the rest of the work must decide and by when.
reversible_commitment_ladder — the mid-point problem definition and the staged pilot-to-rollout delivery are commitments made at a depth proportional to evidence, and kept reversible.

It does not itself generate candidates or score them — the candidate_option_inventory and option_comparison_frame inside each diamond are filled by tools like Morphological Matrix, then Scoring and Multi-Criteria Decision Matrix; and a single facilitated sitting is a Divergence-Convergence Workshop, not this whole workflow.

Instantiates: Divergence-Convergence Cycle Orchestration — it is the two-cycle macro workflow that puts a problem cycle before a solution cycle.
Sibling mechanisms: Divergence-Convergence Workshop runs a single beat inside one of its diamonds · Concept Screening Funnel can drive a diamond's convergence · Morphological Matrix, then Scoring · Multi-Criteria Decision Matrix · Assumption Reversal and Recombination · Design Studio Critique Cycle · Dot Voting with Evidence Gate

References¶

[1] The Double Diamond is the four-phase design framework (discover, define, develop, deliver) popularized by the UK Design Council. It is explicitly meant to be iterative rather than a strict waterfall — the failure mode above is running it as if the phases were one-way gates. ↩