Loading content
Double Diamond is a structured four-phase design method (Discover, Define, Develop, Deliver) that guides teams from problem exploration to validated solutions. It separates divergent and convergent thinking to reduce risk and increase clarity. Widely used in product design, it supports stakeholder alignment and iterative learning.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Double Diamond is a four-phase design framework that guides teams from open problem exploration to a tested, deliverable solution.
The Design Council described Double Diamond as a design process model with the four phases Discover, Define, Develop, and Deliver. It emerged in the British design context as a response to the recurring problem of mistaking an unclear task for a ready-made solution too early. The framework therefore separates exploring and sharpening the problem from generating and testing options.
Think of two back-to-back diamonds as a search-and-decision cycle. On the left, the team first widens the view so observations, needs, and relationships become visible, then narrows to a clear problem statement. On the right, the same pattern is applied to solutions: many ideas are generated, tried, and progressively narrowed until one workable, deliverable option remains.
Observations, needs, causes, and constraints are gathered before a direction is fixed.
Different approaches are created and then weighed against one another.
The view is deliberately opened so alternatives and perspectives are not narrowed too early.
Options are reduced step by step until a workable decision remains.
Prototypes, tests, or feedback check whether an assumption holds in practice.
Double Diamond is especially useful for new products, service redesigns, unclear requirements, or complex stakeholder situations. It creates a shared language and lowers the risk of building the wrong solution too early. For small, already well-defined tasks, the full process can be too heavy; it also does not replace research, prioritization, or technical feasibility.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.