What is the double diamond design process?
The double diamond is a design process model developed by the UK Design Council in 2005 that visualizes design work as two consecutive diamonds, each representing a cycle of divergent and convergent thinking. The first diamond covers the problem space: the Discover phase opens out to gather broad research and insights, and the Define phase narrows that research to a specific, well-evidenced problem statement. The second diamond covers the solution space: the Develop phase opens out to generate and explore multiple potential solutions, and the Deliver phase narrows to the refined, tested solution that is built and shipped.
Why is the double diamond useful for UX teams?
The double diamond makes the structure of design work legible to stakeholders who may not be familiar with why research, ideation, and testing take time. By naming the phases and explaining the divergent-convergent rhythm, teams can communicate why they are exploring broadly at some stages and narrowing at others, and why jumping straight from problem to solution bypasses essential work. It also helps teams recognize when they are in the wrong phase: a team that is defining solutions before completing discovery, or shipping before delivering tested designs, is compressing phases in ways that increase risk.
How does the double diamond relate to other design frameworks?
The double diamond is a process model, not a methodology. It can be implemented using many different research and design methods. Design sprints are a compressed version of the double diamond that runs through both diamonds in five days. Lean UX adapts the double diamond for continuous delivery environments where work happens in shorter cycles. The key insight that the double diamond captures, that good design requires explicitly exploring the problem before solving it, is consistent across all these frameworks even when the specific methods and timelines differ.