Double Diamond Design Process: The Research-Driven Framework for Product and UX Teams

The Quick Answer

The Double Diamond is a design and research framework developed by the UK Design Council in 2004 that structures creative problem-solving into four phases: Discover, Define, Develop, and Deliver. Two "diamonds" represent cycles of divergent thinking (exploring widely) and convergent thinking (focusing on what matters). Teams that follow the full framework — particularly committing to the Define phase before jumping to solutions — build products with measurably better outcomes. Design-led companies that use structured research processes outperform their peers by 32% in revenue growth and 56% in total shareholder returns, according to McKinsey's analysis of 300+ companies over 10 years.

What Is the Double Diamond?

The Double Diamond framework was created by Richard Eisermann and his team at the UK Design Council in 2004, drawing on a divergence-convergence model originally described by Hungarian-American systems theorist Béla Bánáthy in 1996. (Versions of the diamond shape were already in use at IDEO in the late 1990s, where designer Dave Duncanson described the product development process as "diamond-shaped.") What the Design Council contributed was to standardize, visualize, and name the model in a way that became universally adopted.

The core insight is deceptively simple: good design requires two rounds of expanding and narrowing. Most teams do only one — they identify a problem, brainstorm solutions, pick one, and build. The Double Diamond insists that before you define the problem, you must first explore broadly enough to understand whether you are solving the right one.

The 2019 update to the framework — the Framework for Innovation — added four operating principles that surround the diamonds: put people first, communicate visually and inclusively, collaborate and co-create, and iterate constantly.

The Four Phases

Phase 1: Discover (First Diamond — Divergent Thinking)

The Discover phase is about expanding your understanding. You are not looking for solutions yet — you are looking for context, patterns, and surprises. Research methods in this phase include:

• User interviews — structured, semi-structured, and exploratory conversations with people who experience the problem space
• Field studies and contextual inquiry — observing people in their natural environment to capture behavior, not just self-report
• Desk research and secondary sources — reviewing existing data, market reports, and academic literature to understand the domain
• Competitive landscape analysis — understanding how others have approached related problems
• Analytics review — quantitative data that reveals what is happening (though not why)

The Discover phase requires genuine curiosity and suspension of judgment. The most expensive mistake teams make here is conducting discovery research with hypotheses already formed — which turns discovery into confirmation. The goal is to be surprised.

Phase 2: Define (First Diamond — Convergent Thinking)

The Define phase is where raw insight gets transformed into a clear problem statement. This is the most commonly skipped phase — and the most consequential to skip.

Teams in Define are synthesizing everything learned in Discover:

• Affinity mapping — clustering observations into themes that reveal patterns
• Insight writing — translating observations into "why" statements that explain behavior
• Problem statement formulation — defining the specific challenge to solve, in user terms
• Persona refinement — building research-backed descriptions of users based on observed behavior
• Journey mapping — visualizing where friction occurs across user flows

The output of Define is a problem statement sharp enough to guide ideation. Not "improve the user experience" (too vague) but "working parents who use our app struggle to track multiple family schedules simultaneously, causing them to miss important events and creating stress they associate with our product." That is specific enough to design against.

Phase 3: Develop (Second Diamond — Divergent Thinking)

The Develop phase opens the aperture again — but now you are diverging on solutions, not problems. You know what you are solving for; the question is how.

Methods include:

• Brainstorming and ideation sessions — generating as many solution candidates as possible before evaluating any
• Sketching and wireframing — quick low-fidelity visualization of concepts for team alignment
• Prototyping — building testable versions of the most promising ideas
• Co-design workshops — involving users directly in the solution-generation process
• Scenario development — imagining how different user types would experience each solution

The discipline here is quantity before quality. Teams that evaluate ideas too early eliminate promising concepts before they are fully formed.

Phase 4: Deliver (Second Diamond — Convergent Thinking)

The Deliver phase narrows from multiple solution candidates to the one (or few) that will be built and launched.

Methods include:

• Usability testing — validating that solutions work for real users in realistic conditions
• Pilot programs — testing at small scale before full rollout to catch systemic issues
• Preference testing — comparing solution variants with representative users
• Quality assurance — ensuring the solution performs as intended across scenarios
• Post-launch evaluation — measuring whether the solution actually solved the defined problem

The Deliver phase feeds new observations back into Discover. In practice, the Double Diamond is not a once-and-done process but a continuous cycle of understanding, defining, developing, and delivering.

Why Teams Skip the Define Phase (And What It Costs Them)

Clayton Christensen's research at Harvard found that 95% of innovation initiatives fail — and 70% of projects fail to deliver on their promises to customers. The pattern is almost always the same: teams invest heavily in building and delivering solutions to problems they have not clearly defined.

Frog Design documented the failure mode directly: "Clients wanted to gobble up all the promise of design thinking without the time and money spent on larger-scale, upfront research." The result was design processes that looked like Double Diamond on paper but collapsed the entire first diamond into a one-day workshop.

The Define phase is uncomfortable because it does not produce visible artifacts. It produces understanding. And in cultures where productivity is measured in output rather than insight, "we spent two weeks understanding the problem" is a hard sell to stakeholders.

But the cost of skipping it is substantial. Forrester's total economic impact study of IBM's design thinking practice found a 301% ROI — a return driven largely by reduced rework and faster time-to-market. Catching the wrong problem definition in the Discover and Define phases costs a whiteboard session. Catching it after launch costs everything.

The Nike FlyEase Case Study

Few examples illustrate the Double Diamond better than Nike FlyEase — a product line that emerged from following the framework seriously.

It began in 2012 when Matthew Walzer, a teenager with cerebral palsy, wrote to Nike explaining that he could not tie his own shoes independently. Nike designers entered a genuine Discover phase — researching, interviewing, and observing adaptive athletes. The insight that emerged in Define was precise: the problem was not "adaptive athletes need different shoes." It was "getting your foot into the shoe is the friction point."

That specific problem definition — not "accessible footwear" broadly, but "foot entry" specifically — led to the FlyEase design with its wrap-around zipper and hands-free entry mechanism.

What happened in Deliver was a surprise: the product turned out to be popular far beyond its target users — parents with infants in their arms, travelers rushing through airports, older adults with arthritis. A well-defined problem led to a solution that outperformed its design brief. This is what rigorous Define makes possible.

The 2019 Framework for Innovation Update

The original 2004 Double Diamond described what to do. The 2019 Framework for Innovation addressed how to do it — specifically, the cultural and organizational conditions that make the process work.

The Design Council added four guiding principles that now surround the core diamonds:

1. Put people first — Start with understanding the people using a service, their needs, strengths, and aspirations. Not assumptions about them.

2. Communicate visually and inclusively — Design thinking is collaborative; visual communication makes ideas accessible to people who are not designers and builds shared understanding.

3. Collaborate and co-create — The more diverse the team, the better the design. Include the people affected by the problem in the solution process itself.

4. Iterate, iterate, iterate — No solution is perfect on the first attempt. Iteration is not failure; it is the process.

These principles address a failure mode the Design Council observed repeatedly: organizations adopting the Double Diamond as a process while maintaining cultures where assumptions were not challenged, research was rushed, and iteration was resisted by leadership.

Applying the Double Diamond With AI-Powered Research

The most time-intensive phases of the Double Diamond are Discover and Define — both heavily dependent on user research. Traditional moderated research at the scale needed for meaningful Discover work is slow: scheduling participants, conducting interviews, transcribing, analyzing.

Koji dramatically accelerates the first diamond. Here is how Koji maps to each phase:

Discover Phase: Run broad exploratory interviews at scale. Use Koji's AI interviewer to conduct 30–50 open-ended conversations about users' experiences, needs, and pain points across your problem space. The AI follows interesting threads automatically, with configurable probing depth for each question. Koji's 6 structured question types — open_ended, scale, single_choice, multiple_choice, ranking, and yes_no — let you mix exploratory conversation with quantitative capture in the same session, something static surveys cannot do.

Define Phase: Koji's automatic thematic analysis synthesizes what emerged across all interviews — surfacing patterns, themes, and notable quotes that become the raw material for insight writing and problem statement formulation. What used to take days of manual affinity mapping happens automatically in your Koji report.

Develop Phase: Run concept validation interviews. Share early prototypes or concept descriptions through the Koji brief, ask participants to react, and configure the AI to probe their responses. Get structured feedback at scale before committing to a direction.

Deliver Phase: Run post-launch research. Import users from your CRM, invite them to voice or text interviews, and systematically track satisfaction, adoption, and experience using scale questions and open probes.

Where traditional tools like SurveyMonkey or Qualtrics force you to choose between depth (one-on-one moderated research) and scale (surveys, no follow-up), Koji provides both in every phase of the Double Diamond.

Common Mistakes to Avoid

Treating the framework as linear. The Double Diamond is iterative. New findings in Define should send teams back into Discover. Prototype tests in Develop should be allowed to question the problem definition. Treat it as a loop, not a waterfall.

Compressing the first diamond for speed. Teams under time pressure often cut Discover to a single day. The minimum meaningful time in Discover for a significant product decision is 3–4 weeks of real research. Less than that and you are confirming hypotheses, not discovering needs.

Writing vague problem statements in Define. "Improve the experience" is not a problem statement. "Users who use our product for the first time without a tutorial cannot complete their first meaningful action within 10 minutes" is a problem statement. The specificity of your problem statement directly determines the quality of your solutions.

Skipping user involvement in Develop. Co-design and prototype testing with real users in the Develop phase is how you avoid building elegant solutions to wrong interpretations of the right problem.

Ignoring the 2019 principles as decorative. The four operating principles — put people first, communicate visually, collaborate, iterate — are not flourishes. Teams that treat them as optional consistently report worse outcomes than teams that treat them as operational requirements.

When Each Phase Typically Takes

Timeline varies by project scale, but as a baseline:

• Discover: Minimum 3–4 weeks for meaningful research on a significant product decision
• Define: 1–2 weeks for synthesis, insight writing, and problem statement validation
• Develop: 2–4 weeks for ideation and prototyping
• Deliver: Ongoing, feeding back into Discover

Teams that compress Discover to a single workshop consistently report worse product outcomes and more expensive rework downstream.

Summary: The Framework That Starts With "Why?"

The Double Diamond's enduring value is its insistence that before you answer "how do we build this?", you must thoroughly answer "are we building the right thing?" The first diamond is about understanding the problem space. The second diamond is about finding the right solution.

Design-led companies that invest in the full process — including rigorous Discover and Define phases — grow at twice the rate of their peers. The framework is not magic; it is discipline. The discipline to stay in the problem space long enough to understand it deeply before designing a solution.

---

Related Resources

• Structured Questions in AI Interviews
• Generative Research: How to Uncover User Needs You Didn't Know Existed
• How to Write Research Insight Statements That Drive Action
• Affinity Mapping: Organize Qualitative Data Into Themes
• Product Discovery Research: How to Validate Ideas Before Building
• How to Write a UX Problem Statement: Templates and Examples