The Double-Diamond Model

From the British Design Council (2005). Two diamonds, each a diverge → converge cycle:

   FIND THE RIGHT PROBLEM        FIND THE RIGHT SOLUTION
   diverge → converge            diverge → converge
   (discover) (define)           (develop) (deliver)

1. First diamond — find the right problem. Don't accept the stated problem; diverge to explore all underlying issues, then converge on the real problem statement. ("Never solve the problem I am asked to solve — it's usually a symptom.")
2. Second diamond — find the right solution. Diverge across many possible solutions, then converge on one proposal.

Each diamond uses the The HCD Iterative Process — Observe / Ideate / Prototype / Test (observe/ideate/prototype/test) internally.

Why it unsettles managers

Designers appear to "go backward" — questioning the assignment, traveling to study users, generating many half-formed ideas, sometimes re-formulating the problem mid-way (requiring a repeat). This looks chaotic but follows established procedure.

How to manage it

"Encourage free exploration, but hold them to schedule and budget constraints. There is nothing like a firm deadline to get creative minds to converge."

Relationship

Embodies HCD's two commitments: solve the right problem + meet human needs. Pairs with Root Cause Analysis and the Five Whys for the first diamond.

Confidence

1.0 — explicit, attributed model.

Sources: ["DOET ch.6 'The Double-Diamond Model' p.220-221 (Fig 6.1; British Design Council 2005)"]