18 Double Diamond Download: Everything You Need to Know About This Framework
The design world has no shortage of methodologies, frameworks, and buzzwords — but few have proven as enduring, versatile, or genuinely useful as the Double Diamond. And when practitioners talk about an “18 Double Diamond Download,” they’re referring to something specific: a deep, structured walkthrough of how the Double Diamond model operates across eighteen distinct touchpoints, stages, or dimensions of a design and innovation process. Whether you’re a UX designer, a product manager, a service designer, or a business strategist, understanding the Double Diamond at this level of granularity can transform the way you think about solving problems.
This guide is a comprehensive breakdown of the 18 Double Diamond Download concept — what it means, how to apply it, why it matters, and how you can use it to run better projects, facilitate stronger workshops, and build products that actually work for real people.
What Is the Double Diamond?
Before diving into the eighteen-point breakdown, it helps to understand the original framework. The Double Diamond was developed and published by the British Design Council in 2005. It was their attempt to visualize the design process in a way that was simple enough to communicate broadly but rich enough to actually guide real work.
The model takes the shape of two diamonds placed side by side. Each diamond represents a phase of thinking: the first diamond covers the process of discovering and defining a problem, while the second covers the process of developing and delivering a solution. The left side of each diamond expands outward — representing divergent thinking, where you open up possibilities, gather information, and explore widely. The right side of each diamond narrows inward — representing convergent thinking, where you synthesize, prioritize, and make decisions.
That’s the classic four-phase version: Discover, Define, Develop, Deliver.
But design practice has grown significantly since 2005. The Double Diamond has been iterated on, expanded, and deepened by practitioners and organizations worldwide. The 18 Double Diamond Download reflects that evolution — breaking the process into a richer set of stages, mindsets, tools, and principles that go far beyond the original four phases.
Why Eighteen?
The number eighteen isn’t arbitrary. In practice, experienced designers and design leads have found that the Double Diamond, when applied rigorously to complex organizational problems, naturally surfaces around eighteen meaningful checkpoints — moments where the team must make a conscious decision about direction, method, or output. These aren’t rigid steps in a linear sequence. Think of them more like landmarks on a terrain map. You’ll visit most of them. Some you’ll revisit. A few you might move through so quickly they blur together, while others become the center of gravity for weeks of work.
The 18 Double Diamond Download is a way of naming those landmarks so that teams can orient themselves, communicate clearly, and avoid the most common pitfalls that derail design projects.
The 18 Points: A Full Breakdown
1. Problem Framing
Every Double Diamond begins before the first diamond even opens. Problem framing is the work you do to understand what question you’re actually trying to answer. Too many teams skip this and dive straight into research or ideation with a poorly formed brief. A well-framed problem is specific enough to guide action but open enough to allow discovery. It distinguishes between the presenting problem (what the client or stakeholder says is wrong) and the underlying problem (what’s actually going on).
2. Stakeholder Mapping
Before any research begins, you need to understand who is involved — not just who will use the thing you’re designing, but who has influence over it, who will be affected by it, and whose buy-in will be essential for implementation. Stakeholder mapping in the Double Diamond isn’t a bureaucratic exercise. It’s an act of empathy expansion. It forces you to see the full ecosystem around a problem before you’ve assumed who the main characters are.
3. Research Planning
Good discovery research doesn’t happen by accident. Research planning involves deciding what you want to learn, which methods will help you learn it, who you need to speak to, and how you’ll capture and analyze what you find. This is the point where many teams underinvest, leading to discovery phases that feel busy but produce thin insights. A research plan should be a genuine strategic document — modest in length but rigorous in its logic.
4. Contextual Discovery
This is the heart of the first diamond’s divergent phase. Contextual discovery means going out into the world — interviewing people in their own environments, observing behavior, reviewing existing data, auditing the competitive landscape, and immersing yourself in the context of the problem. The goal is not to confirm what you already believe. It is specifically to be surprised. The best contextual discovery work generates tension between what you thought was true and what you’re finding.
5. Secondary Research and Desk Review
Alongside primary research, a thorough download of existing literature, reports, analogous cases, and domain expertise is essential. This doesn’t mean reading for the sake of reading. Secondary research should directly inform your primary research questions and help you identify gaps that fieldwork can fill. It also prevents teams from reinventing the wheel — often someone, somewhere, has already solved a related problem and documented it.
6. Synthesis Preparation
Raw research is not insight. Between data collection and sense-making, there is a critical preparation phase: organizing your material, transcribing interviews, clustering observations, and creating the conditions for collaborative synthesis. Teams that rush this step often end up doing synthesis badly — their themes are shallow, their insights are descriptions rather than revelations, and their design principles don’t hold up under scrutiny.
7. Insight Generation
This is where divergent thinking begins to tip toward convergent thinking within the first diamond. Insight generation is the practice of moving from “here’s what we heard and observed” to “here’s what it means.” Good insights are non-obvious, specific, actionable, and grounded in evidence. They usually take the form of a tension or a paradox — something that surprises the team and reframes how they understand the people they’re designing for.
8. How Might We Questions
The How Might We (HMW) format is a classic bridge between the first and second diamond. Each insight is translated into a generative question that opens up the solution space. “How might we help people feel less overwhelmed by complex financial decisions?” is an example. The format matters: “how” implies there’s a way forward, “might” implies there are multiple options, and “we” establishes shared ownership. HMW questions are the seeds of ideation.
9. Defining the Design Challenge
This is the convergent point of the first diamond — the narrowing moment where all of your discovery work, synthesis, insights, and HMW questions are distilled into a clear, compelling design challenge. This challenge statement is not a solution. It is a precise articulation of the problem worth solving, informed by everything you’ve learned. Getting this right is arguably the most valuable work in the entire Double Diamond. A well-defined challenge acts as a filter for everything that follows.
10. Ideation
The second diamond opens wide with ideation — a phase of deliberate, disciplined creative expansion. Good ideation is not a single brainstorming session. It involves multiple methods, multiple sessions, and multiple perspectives. It includes techniques like worst possible idea (to break anchoring bias), analogous inspiration (to import solutions from adjacent fields), and co-design with actual users (to generate ideas rooted in real need). The goal is quantity and diversity of ideas before quality.
11. Concept Development
From the ideation pool, a smaller number of directions are developed into rough concepts. These aren’t polished designs — they’re developed enough to be evaluated and tested. Concept development involves thinking through how an idea would actually work, who it would serve, what it would require, and what its risks might be. It is the first moment in the process where you’re genuinely building something, even if that something is made of Post-it notes and whiteboard diagrams.
12. Prototyping
Prototyping in the Double Diamond is not about making things look good. It’s about making things testable. A prototype is a tool for learning. It could be a paper sketch, a clickable wireframe, a physical model, a role-play scenario, or a written service blueprint. The fidelity of your prototype should match the questions you’re trying to answer. If you’re testing a fundamental interaction logic, a rough paper prototype is often better than a polished digital mockup because it invites honest feedback rather than premature judgment on aesthetics.
13. User Testing and Feedback
Getting your concepts in front of real users or stakeholders is a non-negotiable part of the second diamond. User testing at this stage isn’t about validation — it’s about learning what to change. The goal is to find out where your assumptions were wrong, where the experience breaks down, and what users understand differently than you expected. A test that confirms everything is usually a sign that you weren’t testing rigorously enough.
14. Iteration
Based on testing feedback, concepts are refined, pivoted, or sometimes abandoned. Iteration is the process of applying what you learned from testing back into the design. This might happen once or many times before a concept is ready to move forward. Iteration is where the real value of the Double Diamond accumulates — each cycle tightens the fit between the solution and the actual need.
15. Solution Definition
At some point, the team must converge on a defined solution to move into delivery. Solution definition involves specifying what will be built or implemented, to what level of fidelity, for which users, through which channels, and to what success criteria. It’s the point where design hands the baton to engineering, service operations, or implementation teams — and the quality of the handoff depends entirely on how clearly the solution has been defined.
16. Pilot and Soft Launch
Many experienced design teams insist on a pilot phase before full-scale delivery. A pilot is a real-world test of the solution at limited scope — a single location, a small user cohort, a constrained version of the service. It allows teams to catch operational issues, edge cases, and unanticipated user behaviors before they become large-scale problems. A well-run pilot generates evidence for organizational decision-makers and builds confidence in the solution.
17. Measurement and Evaluation
Design doesn’t end at launch. Measurement involves tracking whether the solution is achieving its intended outcomes. This requires having defined success metrics earlier in the process — ideally as part of the problem framing and design challenge stages. Evaluation goes deeper: it asks whether the solution is having the right impact, on the right people, in the right ways. This feeds directly back into the next iteration of the Double Diamond.
18. Organizational Learning and Documentation
The final landmark is one of the most overlooked. What did the team learn — not just about the problem and solution, but about the process itself? How should those learnings be captured and shared so that the organization builds capability over time? This is the meta-layer of the Double Diamond Download: treating the design process itself as a subject of reflection and improvement. Teams that do this well develop proprietary methodological intelligence that compounds over years.
How to Use the 18 Double Diamond Download in Practice
You don’t need to treat this framework as a checklist to be completed in order. The most effective teams use it as a navigation tool — a shared vocabulary that helps everyone on a project understand where they are, where they’re going, and what kind of thinking is appropriate right now.
If you’re running a workshop, you might use the eighteen points to design your agenda: spending a full day on insight generation, a morning on HMW questions, and an afternoon on ideation. If you’re managing a project, you might use them as milestone markers that help you report progress to stakeholders in plain language. If you’re mentoring junior designers, you might use them to explain why a team that jumped straight from discovery to delivery is likely to struggle.
The 18 Double Diamond Download is also deeply useful for organizational transformation work — helping companies that are new to human-centered design understand that it is not a single event but a discipline with real structure and real phases, each of which requires time, skill, and attention.
Common Mistakes to Avoid
One of the most persistent mistakes teams make is treating the Double Diamond as a linear process with a clear start and end. In reality, it is highly iterative and often recursive. You might complete a full cycle and then realize that the problem you defined in the first diamond needs to be reframed — sending you back to the beginning with much richer information than you had the first time.
Another common mistake is conflating discovery with research. Discovery is a mindset as much as a method. It requires genuine openness to being wrong, genuine curiosity about people’s lives, and a willingness to let findings lead you somewhere uncomfortable. Teams that use discovery to confirm what they already know produce briefs that don’t generate genuinely new solutions.
Perhaps the most damaging mistake is under-resourcing the first diamond and over-resourcing the second. Organizations often feel pressure to start building quickly, which means rushing through discovery and definition. But a poorly defined problem leads to well-executed solutions to the wrong challenge — and that is one of the most expensive mistakes a team can make.
Why the Double Diamond Still Matters
In a world of agile sprints, lean canvases, and AI-assisted design tools, it might seem like the Double Diamond is showing its age. But the framework’s durability comes from something more fundamental than any specific methodology: it encodes a deep truth about how humans solve complex problems well.
We need to open up before we close down. We need to understand before we act. We need to question the problem before we answer it. And we need to test our answers against reality before we commit to them at scale.
Those principles are not going out of fashion. They are, if anything, more important in an era when it has become cheaper and faster than ever to build the wrong thing with tremendous confidence and speed.
The 18 Double Diamond Download is not a rigid prescription. It is a map drawn by practitioners who have walked this terrain many times and want to share what they found. Use it as a guide. Adapt it to your context. And use it most of all to bring the people around you into a shared understanding of what good design process actually looks like — not as an abstract idea, but as a concrete, navigable journey from problem to solution.
Whether you’re facilitating your first design sprint, leading a product team, or transforming a large organization’s approach to innovation, the Double Diamond framework — explored at this depth — gives you something rare: a common language for doing hard creative work together, with rigor, empathy, and clarity.
