Skip to main content
Most product teams spend their time in one of two modes: exploring (lots of ideas, lots of research, lots of “what if?”) or converging (picking a direction, scoping, shipping). The Double Diamond is a framework that makes those two modes explicit - and insists you do both, twice.

​
The shape of good design

Developed by the British Design Council in 2005, the Double Diamond maps a design process as two consecutive diamonds. Each diamond has a diverge phase (opening up) and a converge phase (narrowing down). Diamond 1 - the right problem
  • Discover - explore the problem space broadly. Talk to users, do research, observe behaviour. Don’t narrow too early.
  • Define - synthesise what you found into a clear problem statement. What is the real problem worth solving?
Diamond 2 - the right solution
  • Develop - ideate widely. Generate many potential solutions before committing to any.
  • Deliver - test, iterate, and ship the solution that best addresses the defined problem.
The insight the framework encodes: you need to diverge and converge on the problem before you diverge and converge on the solution. Most teams skip the first diamond entirely 😬

​
Why the first diamond matters most

Here’s the thing - the second diamond (ideation, prototyping, delivery) is where most teams naturally live. They’re good at it. The tools exist, the process is familiar, sprints are running. The first diamond is where the expensive mistakes get made. Teams that jump straight to solutions are almost always solving the wrong problem - or a symptom of the right problem rather than its root cause. The “Define” stage at the end of the first diamond is the most valuable output. A well-written problem statement - specific, human, free of assumed solutions - is worth more than a hundred feature ideas. It aligns the team, focuses the research, and acts as a filter for every decision downstream.

​
How it relates to other frameworks

The Double Diamond maps cleanly onto other tools you might already use: It’s less a standalone methodology and more a mental model that helps you see where you are in the process - and whether you’ve skipped anything important.

​
The honest limitation

The Double Diamond is a useful map, not a guarantee of good outcomes. You can run a textbook double diamond process and still end up with the wrong answer if your research is shallow, your problem statement is too vague, or your team rushes through the diverge phases to get to the comfortable business of building. Lesson learned: the value of the framework is in the questions it forces you to ask. Are we exploring broadly enough before we converge? Have we really defined the problem or just dressed up a solution as one? If you use it as a checklist to rush through, it won’t help you 🤷