Double Diamond Design Process: The Complete Guide for Product Teams (2026)
The Double Diamond design process is one of the most widely adopted frameworks for solving complex design problems. Developed by the British Design Council, it gives product teams a clear structure for moving from a vague challenge to a tested, shippable solution.
This guide covers everything you need to know about the Double Diamond: what it is, where it comes from, how each phase works, and how modern product teams apply it alongside tools like UXPin Merge to move from insight to interactive prototype faster.
What Is the Double Diamond Design Process?
The Double Diamond is a visual framework that maps the design process into two connected diamond shapes. Each diamond represents a cycle of divergent thinking (exploring broadly) followed by convergent thinking (narrowing to a decision).
- Diamond 1 — Problem space: Discover the landscape, then Define the core problem.
- Diamond 2 — Solution space: Develop possible solutions, then Deliver the best one.
The model encourages teams to resist jumping to solutions before they truly understand the problem — a discipline that consistently produces better outcomes.
Origin and History of the Double Diamond
The British Design Council formalised the Double Diamond in 2005 after studying the design processes at eleven leading companies, including LEGO, Sony, and Starbucks. The council found that regardless of industry, successful design projects followed the same diverge-converge pattern twice: once for the problem, once for the solution.
The concept has deeper roots in the divergence-convergence model described by Hungarian-American linguist Béla H. Bánáthy, who proposed that problem-solving naturally alternates between exploring broadly and focusing narrowly. The Design Council applied this principle to design practice and gave it a memorable visual shape — the two diamonds.
Since 2005, the framework has been adopted by government agencies (the UK’s NHS and Government Digital Service), global enterprises, and startups alike. It remains one of the most-referenced design process models in UX education and practice.
The Four Phases of the Double Diamond
1. Discover — Explore the Problem Space
The Discover phase is about divergent research. Teams cast a wide net to understand users, business context, and the landscape surrounding the challenge. Key activities include:
- User interviews and contextual inquiry — Observe and talk to real users in their environment.
- Stakeholder workshops — Align on business goals, constraints, and success metrics.
- Analytics review — Mine quantitative data for behavioural patterns.
- Competitive analysis — Understand how others address similar problems.
- Service safaris — Experience the current product or service first-hand.
The goal is empathy and breadth — resist narrowing down too early.
2. Define — Frame the Right Problem
In the Define phase, teams converge. They synthesise discovery research into a clear, actionable problem statement (sometimes called a design brief or How Might We statement). Activities include:
- Affinity mapping — Cluster research insights into themes.
- Persona development — Create representative user archetypes.
- Journey mapping — Visualise the end-to-end user experience and identify pain points.
- Problem framing — Write a concise problem statement the team will solve.
A strong Define output ensures the entire team is solving the same problem — and prevents the common trap of building a solution nobody asked for.
3. Develop — Generate and Prototype Solutions
The Develop phase is where creativity peaks. Teams diverge again, this time generating a wide range of potential solutions before converging on the most promising ones. Key activities:
- Ideation workshops — Brainstorm, sketch, and use techniques like Crazy 8s or SCAMPER.
- Low-fidelity prototyping — Paper sketches, wireframes, and quick clickable mockups.
- High-fidelity prototyping — Interactive prototypes that mimic real product behaviour.
- Concept testing — Put early ideas in front of users to gather directional feedback.
This is where UXPin Forge can dramatically accelerate the process. Teams describe what they need in a text prompt, and Forge generates interactive prototypes using real React components from the team’s own design system. Instead of spending days wiring up screens, designers get a functional starting point in seconds — then refine with UXPin’s professional design tools.
4. Deliver — Test, Refine, and Launch
The Deliver phase converges on a final solution through rigorous testing and iteration. Teams work to validate that the solution actually solves the problem identified in the Define phase. Activities include:
- Usability testing — Observe users completing key tasks with the prototype.
- A/B testing — Compare solution variants with real traffic.
- Accessibility audits — Ensure the solution works for all users.
- Design-to-development handoff — Deliver final specs and assets to engineers.
With UXPin Merge, the handoff gap shrinks dramatically. Because designers prototype with the same coded components engineers use in production, the final design is the specification. Engineers receive production-ready JSX instead of static mockups, which enterprise customers report reduces engineering time by up to 50%.
Double Diamond vs. Design Thinking: How Do They Compare?
| Aspect | Double Diamond | Design Thinking (IDEO/d.school) |
|---|---|---|
| Phases | Discover → Define → Develop → Deliver | Empathise → Define → Ideate → Prototype → Test |
| Structure | Two explicit diverge-converge cycles | Five stages (less explicit about diverge/converge) |
| Emphasis | Equal weight on problem and solution | Heavy emphasis on empathy and rapid prototyping |
| Origin | British Design Council (2005) | IDEO / Stanford d.school (2000s) |
In practice, many teams blend both. You might use the Double Diamond’s two-diamond framing for strategic planning while applying Design Thinking’s five stages as tactical steps within each diamond.
How to Apply the Double Diamond in Your Team
Start With Real Research, Not Assumptions
The most common mistake teams make is skipping the first diamond entirely. Invest time in Discover and Define before jumping to solutions. Even a few user interviews can prevent months of building the wrong thing.
Timebox Each Phase
Without boundaries, the Discover phase can stretch indefinitely. Set clear timeboxes and commit to moving forward with the best understanding you have.
Use the Right Fidelity at the Right Time
Low-fidelity artifacts (sticky notes, sketches, wireframes) are ideal during Discover and Define. High-fidelity interactive prototypes belong in Develop and Deliver.
Integrate With Agile Workflows
The Double Diamond works well as a strategic overlay on agile sprints. The first diamond feeds the backlog with well-defined problems. The second diamond’s Develop and Deliver phases map naturally to sprint cycles.
Prototype With Production Components
In the Develop phase, teams that prototype with real UI components get more realistic user feedback and smoother developer handoff. UXPin Merge makes this possible by letting designers drag and drop coded components from libraries like MUI, shadcn/ui, or your own custom React library directly onto the canvas.
Who Uses the Double Diamond Framework?
- Government: The UK’s Government Digital Service (GDS) and NHS use the Double Diamond as the basis for their service design approach.
- Enterprise product teams: Companies like PayPal, where a 5-person UX team supports over 60 products and 1,000+ developers, rely on structured frameworks to ensure research-backed design decisions at scale.
- Startups: Early-stage teams use the first diamond to validate that a real problem exists before investing in development.
- Design agencies: The framework’s clarity makes it an effective tool for communicating process to clients.
Common Mistakes When Using the Double Diamond
- Skipping the first diamond. Jumping straight to solutions without understanding the problem leads to wasted effort.
- Treating phases as strictly linear. In reality, teams often loop back — a usability test in Deliver may reveal a problem that requires returning to Define.
- Confusing divergent with unfocused. Divergent thinking still needs direction.
- Over-polishing in the Develop phase. The goal is to learn, not to ship.
- Neglecting the handoff. Even the best-designed solution fails if it gets lost in translation to code.
Accelerate the Double Diamond With UXPin
UXPin supports the Develop and Deliver phases with capabilities purpose-built for product teams:
- Forge AI generates interactive prototypes from text prompts, image uploads, or URLs — using real components from your design system. It gets teams to 80% of a prototype instantly, then professional design tools handle the final 20%.
- Merge connects your production component library directly to the design canvas. Designers and developers work from the same source of truth.
- Interactive prototyping with states, variables, and conditional logic lets teams build prototypes that behave like the real product.
- Production JSX output means engineers get clean, production-ready code instead of redline documents.
Try UXPin for free and see how code-backed prototyping transforms the Develop and Deliver phases of your Double Diamond process.
Frequently Asked Questions
What is the Double Diamond design process?
The Double Diamond design process is a framework created by the British Design Council in 2005. It visualises design work as two connected diamonds: the first focuses on understanding the problem (Discover and Define), while the second focuses on creating the solution (Develop and Deliver). Teams alternate between divergent thinking (exploring broadly) and convergent thinking (narrowing down).
What are the four phases of the Double Diamond?
The four phases are Discover (research and explore the problem space), Define (synthesise findings into a clear problem statement), Develop (ideate and prototype potential solutions), and Deliver (test, refine, and launch the final solution).
Who created the Double Diamond model?
The British Design Council formalised the Double Diamond in 2005 after studying the design processes of eleven global companies. The underlying divergent-convergent thinking pattern draws on Béla H. Bánáthy’s earlier linguistic model.
How does the Double Diamond differ from Design Thinking?
Design Thinking (popularised by IDEO and Stanford d.school) uses five stages: Empathise, Define, Ideate, Prototype, and Test. The Double Diamond covers similar ground but frames the work as two distinct problem-solution phases with explicit diverge-converge cycles. In practice, many teams blend elements from both frameworks.
Can I use the Double Diamond for agile product development?
Yes. Many product teams use the Double Diamond as an overarching strategy framework while running agile sprints within the Develop and Deliver phases. The first diamond’s research and definition work feeds the product backlog, and agile iterations handle execution.
What tools help teams apply the Double Diamond process?
Teams typically need research tools (interviews, analytics), collaboration tools (whiteboards, workshops), and prototyping tools. UXPin supports the Develop and Deliver phases by enabling teams to build interactive prototypes with production-ready components, test with real users, and hand off clean code to developers.
