# Double Diamond

A four-phase framework for exploring a problem broadly, choosing a clear focus, exploring solutions, and delivering a tested response.

- Type: framework
- Domain: Strategy & discovery
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/double-diamond/>)

## What it means

The Double Diamond is a visual model of design work created by the UK Design Council. Its two diamonds alternate divergent thinking, where a team expands its view, with convergent thinking, where it makes choices. The phases are commonly named Discover, Define, Develop, and Deliver.

## Why it matters

Teams often converge on a solution before they understand the problem. The Double Diamond makes that risk visible and gives cross-functional groups a shared map for moving between research, framing, ideation, testing, and implementation without pretending the path is perfectly linear.

## When to use it

Use it to plan an ambiguous product initiative, explain a discovery-to-delivery process, or diagnose whether a team has skipped exploration. It is especially useful at project kickoff and at decision gates between problem and solution work.

## How it works

1. Discover broadly through research, data review, observation, and stakeholder input.
2. Define the most consequential user problem, constraints, and desired outcome.
3. Develop multiple solution directions rather than polishing the first plausible idea.
4. Deliver by prototyping, testing, refining, launching, and measuring the selected approach.

## A practical example

A banking team asked to improve account opening first studies abandonment data and interviews applicants. It reframes the issue from “redesign the form” to “help applicants recover when identity checks fail,” explores assisted and self-service options, then pilots a guided recovery flow before wider release.

## Where it breaks

The diagram can imply neat, sequential phases even though real discovery loops backward and overlaps delivery. It does not specify research methods, decision criteria, governance, or how much evidence is enough, so teams must adapt it rather than treat it as a project plan.

## Common mistakes

- Using the diamonds as rigid stage gates with no iteration.
- Starting with a preferred feature and performing discovery only to justify it.
- Generating many ideas without explicit evidence or selection criteria.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/double-diamond/#visualization-double-diamond>)

## Sources

1. [The Double Diamond](<https://www.designcouncil.org.uk/resources/the-double-diamond/>) — Design Council · Primary framework overview
2. [History of the Double Diamond](<https://www.designcouncil.org.uk/resources/the-double-diamond/history-of-the-double-diamond/>) — Design Council · Institutional history

## Related topics

- [Design Thinking](<https://wiki.soroush.uk/topic/design-thinking/>)
- [Problem Framing](<https://wiki.soroush.uk/topic/problem-framing/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
