What Is Double Diamond Thinking: Mapping Divergent and Convergent Modes
This skill teaches you how to deliberately switch between expansive exploration and focused decision-making at each stage of the Double Diamond, ensuring your team knows when to broaden possibilities and when to narrow toward action.
To map divergent and convergent thinking in the Double Diamond, label each of the four phases—Discover, Define, Develop, Deliver—as either expansive (divergent) or narrowing (convergent). Discover and Develop are divergent phases where you generate options without judgment. Define and Deliver are convergent phases where you analyze, filter, and commit to focused decisions. Deliberately signal each mode shift to your team.
Outcome: You will be able to consciously orchestrate when your team explores broadly and when it converges on decisions, preventing the most common source of wasted effort in design projects—mixing modes at the wrong time.
Prerequisites
- Basic understanding of the Double Diamond framework and its four phases
- Familiarity with facilitation or workshop techniques
- Experience participating in at least one design or product discovery process
Overview
Understanding what is Double Diamond at a deeper level means recognizing that the framework's power isn't in its four phases alone—it's in the deliberate alternation between divergent and convergent thinking modes. Divergent thinking opens up the solution space: you generate ideas, gather data, and explore without premature judgment. Convergent thinking narrows it: you synthesize, prioritize, and commit. The Double Diamond visualizes this rhythm as two successive expansions and contractions, forming its iconic diamond shape.
Many teams fail not because they skip phases, but because they mix thinking modes within a single phase. A brainstorming session derailed by immediate feasibility critiques, or a prioritization meeting that keeps spawning new ideas—these are symptoms of mode confusion. Mapping divergent and convergent thinking explicitly onto your process gives every participant a shared mental model for what kind of contribution is needed right now.
This skill is foundational to the Double Diamond method and directly supports sibling skills like conducting discovery research (a divergent activity) and converging on final solutions (a convergent activity). Master the mode map first, and every other Double Diamond skill becomes dramatically more effective.
How It Works
The Double Diamond process model divides design work into four phases arranged in two diamonds. Each diamond contains one divergent phase followed by one convergent phase:
Diamond 1 — Problem Space
- Discover (Divergent): Cast a wide net. Research users, explore the problem landscape, collect data without filtering. The goal is breadth of understanding.
- Define (Convergent): Synthesize research into a clear problem statement. Filter out noise, cluster themes, and commit to the specific challenge you'll solve.
Diamond 2 — Solution Space
- Develop (Divergent): Generate as many potential solutions as possible. Brainstorm, prototype, sketch, and explore without committing to any single direction.
- Deliver (Convergent): Evaluate solutions against criteria, select the strongest, refine through testing, and ship.
The mechanism that makes this work is cognitive mode separation. Research in psychology (particularly Guilford's work on creative thinking) shows that people produce better ideas when generation and evaluation are separated in time. When you ask someone to simultaneously invent and judge, both activities suffer. The Double Diamond institutionalizes this separation at the process level.
Mapping these modes means making the current mode visible and explicit. This can be as simple as writing "DIVERGE" or "CONVERGE" on a whiteboard, or as structured as defining specific rules of engagement for each mode (e.g., "No critiques during diverge; all ideas are captured" vs. "Every option must be evaluated against our criteria during converge"). The map becomes a facilitation tool that prevents the most destructive dynamic in design work: premature convergence.
Step-by-Step
Step 1: Audit Your Current Process for Mode Awareness
Before you can map thinking modes, you need to understand your team's current default behavior. Review your last 2-3 projects and identify moments where the team switched between exploring options and making decisions. Look for signs of mode confusion: brainstorming sessions where ideas were immediately shot down, or decision meetings that generated more questions than answers.
Create a simple timeline of your typical project and annotate each activity as primarily divergent or convergent. You'll likely find that many activities are ambiguously mixed, or that your team defaults heavily to one mode (usually convergent, since organizations reward decisiveness).
Tip: Interview 2-3 team members separately about where they felt frustrated in recent projects. Frustration often signals a mode mismatch—someone wanting to explore while the group is converging, or vice versa.
Step 2: Create a Visual Mode Map for Your Double Diamond
Draw or print a Double Diamond diagram and explicitly label each phase with its thinking mode. Go beyond the simple label by defining what each mode looks like in practice for your team:
- Discover (Diverge): What research methods will you use? What counts as valid input? How will you avoid filtering too early?
- Define (Converge): What synthesis techniques will you apply? What criteria determine your problem statement? Who has decision authority?
- Develop (Diverge): What ideation formats will you use? How many ideas is the minimum before converging? What constraints are temporarily suspended?
- Deliver (Converge): What evaluation criteria will you use? What testing must happen before a decision? What does 'done' look like?
This map becomes a living artifact your team references throughout the project. Post it in your workspace or pin it in your project channel.
Tip: Use color coding—green for divergent phases and red for convergent phases—to create an immediate visual signal that even newcomers understand at a glance.
Step 3: Define Explicit Rules of Engagement for Each Mode
Generic labels aren't enough. Teams need behavioral rules that make each mode concrete. Write down 3-5 rules for divergent mode and 3-5 rules for convergent mode that your team agrees to follow.
Example divergent rules: All ideas are captured without critique. Quantity matters more than quality. Build on others' contributions ('Yes, and…'). Wild ideas are encouraged. No discussion of feasibility yet.
Example convergent rules: Every option is evaluated against stated criteria. Decisions require evidence or rationale. Silence means consent. We commit to the outcome and move forward. New ideas are parked for the next divergent phase.
Having these rules written down gives facilitators and participants a shared vocabulary. When someone starts critiquing during a divergent phase, anyone on the team can point to the rules without it feeling personal.
Tip: Laminate the rules or create a digital card that facilitators can literally hold up when mode violations occur. Physical signals are more effective than verbal corrections.
Step 4: Design Transition Rituals Between Modes
The most vulnerable moment in the Double Diamond is the transition from divergent to convergent (and back). Without a clear signal, teams drift between modes chaotically. Design a brief transition ritual for each shift:
- Discover → Define: Hold a 'research closeout' where the team reviews all gathered data and explicitly agrees: 'We have enough to synthesize.' This prevents infinite research loops.
- Define → Develop: Share the finalized problem statement and get verbal commitment from the team: 'This is the problem we're solving.' Then explicitly open the solution space.
- Develop → Deliver: Conduct a 'concept review' where all generated ideas are displayed and the team agrees: 'These are our candidates.' Then introduce evaluation criteria.
These transitions don't need to be elaborate—even a 5-minute standup can serve as a mode shift signal. The key is that the shift is conscious and communal, not accidental.
Tip: Some teams find it helpful to physically change the room setup at transitions—rearranging chairs from circles (diverge) to rows facing a screen (converge)—to trigger a cognitive shift.
Step 5: Assign a Mode Guardian for Each Session
In any workshop or meeting, assign one person the explicit role of 'mode guardian.' This person's job is to watch for mode violations and gently redirect the team. They don't need to be the facilitator—in fact, separating these roles can be more effective because the facilitator can focus on content while the guardian watches the process.
The mode guardian monitors for common violations: premature critique during divergent phases, introduction of new possibilities during convergent phases, or the team slipping into analysis paralysis (a sign of trying to converge without enough divergent material).
Rotate this role across team members to build collective mode awareness over time.
Tip: Give the mode guardian a physical prop—a colored flag, a bell, or even an emoji reaction in virtual meetings—so interventions feel playful rather than punitive.
Step 6: Calibrate Timebox Ratios for Each Mode
Not all phases need equal time. A common mistake is spending too long in divergent phases (research paralysis, ideation without closure) or too little (jumping to solutions after superficial exploration). Establish rough timebox ratios based on project complexity.
For a typical product design sprint, a useful starting ratio is:
- Discover: 25-30% of total time
- Define: 10-15%
- Develop: 30-35%
- Deliver: 20-30%
These ratios shift based on how well-understood the problem is. If the problem space is well-known, you can compress Diamond 1 and spend more time in Diamond 2. If you're entering a completely new domain, Diamond 1 may need 60% of total time.
Review and adjust these ratios after each project as part of your retrospective.
Tip: Track actual time spent in each mode across multiple projects. Most teams discover they under-invest in divergent phases by 30-40%, which explains why their solutions feel incremental rather than innovative.
Step 7: Retrospect on Mode Discipline After Each Project
After completing a Double Diamond cycle, hold a brief retrospective specifically about thinking mode discipline. Ask: Where did we mix modes? Did any phase feel rushed or bloated? Were transition points clear? Did the mode map help us make better decisions?
Capture lessons learned and update your mode map, rules of engagement, and timebox ratios accordingly. Over 3-4 projects, your team will develop intuitive mode awareness and need less explicit scaffolding.
This retrospective should be separate from your general project retro to give it focused attention. Even 20 minutes is enough.
Examples
Example: Mapping Modes for a Mobile Banking App Redesign
A fintech product team is redesigning their mobile banking app's bill payment flow. They have 6 weeks and a cross-functional team of 8 (designers, engineers, a product manager, and a researcher). The team has previously struggled with rushed designs that didn't address actual user pain points.
The team starts by creating a mode map on a shared Miro board. They allocate Week 1-2 to Discover (divergent): conducting 12 user interviews, analyzing support tickets, benchmarking 6 competitor apps, and running a diary study with 5 users. The board header reads 'MODE: DIVERGE — All findings welcome, no filtering yet.'
At the end of Week 2, they hold a transition ritual: a 2-hour synthesis workshop where they cluster all findings into themes. They switch the board header to 'MODE: CONVERGE — Defining the problem.' By end of day, they've committed to a problem statement: 'Users abandon bill payments because they can't verify payee details before committing, leading to anxiety and manual workarounds.'
Week 3-4 opens Diamond 2. The header switches to 'MODE: DIVERGE — All solutions welcome.' The team runs three ideation sessions using different techniques (Crazy 8s, reverse brainstorming, analogous inspiration from gaming UIs). They generate 47 distinct concepts. A mode guardian prevents the engineering lead from dismissing ideas based on technical complexity—those concerns are parked for the convergent phase.
Week 5-6 shifts to Deliver (converge). The team evaluates all 47 concepts against four criteria: user anxiety reduction, implementation complexity, alignment with brand, and measurability. They narrow to 3 concepts, prototype each, test with 5 users, and converge on a solution that combines payee verification with a confidence indicator. The final retrospective reveals that explicitly marking modes prevented at least three instances where the team would have prematurely killed promising ideas.
Example: Applying Mode Mapping to a Non-Design Context (Policy Development)
A government digital services team needs to develop a new accessibility policy for public-facing websites. The team lead has heard about the Double Diamond but isn't sure how thinking modes apply outside traditional product design.
The team maps the Double Diamond to their policy process. Discover (diverge): they review accessibility complaints, interview disabled users, audit 20 existing government websites, and study international accessibility standards—casting a wide net without pre-deciding what the policy should cover.
Define (converge): they synthesize findings into three core problem areas—screen reader compatibility, cognitive load for neurodiverse users, and mobile accessibility for users with motor impairments—and select the most impactful problem to address first.
Develop (diverge): they generate multiple policy approaches—prescriptive technical standards, outcome-based requirements, incentive-based compliance, mandatory testing regimes—without initially debating which is 'realistic.' They invite external accessibility experts to add more approaches the team hadn't considered.
Deliver (converge): they evaluate approaches against criteria including enforceability, cost, measurable impact, and political feasibility. They select a hybrid approach, draft the policy, test it with three pilot agencies, and refine based on feedback.
The explicit mode mapping helped the team resist their organizational tendency to jump immediately to writing policy text (a convergent activity) before fully understanding the problem space.
Best Practices
Make the current thinking mode physically visible at all times—on a whiteboard, a Miro board header, or a Slack channel topic—so no one has to guess whether to explore or decide.
Always diverge before you converge, even when you think you already know the answer. A brief 15-minute divergent warm-up before a decision meeting consistently produces better outcomes than jumping straight to evaluation.
Use divergent phases to build psychological safety: when all ideas are welcomed without judgment, quieter team members contribute more, and the team's collective intelligence rises.
Set explicit quantity targets for divergent phases (e.g., 'We need 30 ideas before we start filtering') to prevent the team from converging too early out of comfort.
Document the transition criteria between phases in advance. 'We will move from Discover to Define when we have interviewed at least 8 users and identified recurring themes' is far more useful than 'when we feel ready.'
When stakeholders join mid-project, brief them on the current thinking mode before the meeting starts. Stakeholders are the most common source of mode violations because they lack process context.
Common Mistakes
Allowing critique during divergent phases ('That won't work because…')
Correction
Enforce a strict 'capture everything' rule during divergent phases. Park feasibility concerns on a separate list to address during the convergent phase. Even one premature critique can shut down creative exploration for the entire group.
Treating convergence as simply voting or picking favorites
Correction
Convergence requires evaluation criteria defined before you start filtering. Use structured techniques like weighted scoring matrices, impact/effort mapping, or How-Might-We clustering. 'I like this one' is not convergence—it's preference without rigor.
Skipping the Define phase and jumping from Discover directly to Develop
Correction
This is the single most common Double Diamond failure. Without explicit convergence on a problem statement, teams develop solutions for vaguely understood problems. Force the team to articulate the problem in one sentence before opening the solution space.
Running the entire Double Diamond as one long convergent process with brief 'brainstorming breaks'
Correction
Divergent phases should be substantial, not token gestures. If your Discover phase is a single stakeholder interview and your Develop phase is one 30-minute brainstorm, you're not actually diverging—you're just decorating a linear process with Double Diamond labels.
Assuming the Double Diamond is strictly linear with no iteration
Correction
While the mode sequence (diverge→converge→diverge→converge) should be respected within each cycle, you may need to loop back. If convergence in Define reveals you lack sufficient understanding, return to Discover. The key is making these loops conscious and time-bounded rather than chaotic.
Other Skills in This Method
Converging on Solutions in the Deliver Phase
How to evaluate, test, and iterate on concepts to select and refine the final solution for implementation in the Deliver phase.
Synthesizing Insights to Define the Problem
How to apply convergent thinking in the Define phase to analyze discovery findings, create problem statements, and narrow focus to the right challenge.
Facilitating Divergent Ideation in the Develop Phase
How to run structured brainstorming, co-design workshops, and prototyping sessions to generate a wide range of potential solutions in the second diamond.
Conducting Discovery Research in the Discover Phase
How to use divergent thinking techniques like user interviews, desk research, and observation to broadly explore the problem space in the first diamond.
Creating Double Diamond Process Diagrams
How to visually map your design process onto the Double Diamond diagram to communicate project phases, activities, and progress to stakeholders.
Choosing Between Double Diamond and Design Thinking
How to compare the Double Diamond with other design frameworks like Stanford d.school Design Thinking and Lean UX to select the right approach for your project.
Adapting the Double Diamond for UX Design Projects
How to apply the Double Diamond framework specifically to UX workflows, integrating user research, wireframing, usability testing, and iterative design.
Frequently Asked Questions
What is Double Diamond divergent and convergent thinking?
The Double Diamond framework uses two types of thinking in alternating phases. Divergent thinking (used in Discover and Develop) means expanding your options—gathering data, generating ideas, and exploring without judgment. Convergent thinking (used in Define and Deliver) means narrowing down—synthesizing, evaluating, and committing to decisions. The two diamonds represent two complete diverge-then-converge cycles.
How do I know when to switch from divergent to convergent thinking?
Switch when you've reached sufficient breadth. In practice, this means defining transition criteria in advance: a minimum number of user interviews completed, a target quantity of ideas generated, or a time boundary reached. If your team starts repeating the same insights or ideas, that's a strong signal you've saturated the divergent phase and should converge.
Can I diverge and converge within a single meeting or workshop?
Yes, and experienced facilitators do this frequently. A 90-minute workshop might include 30 minutes of divergent brainstorming followed by 60 minutes of convergent evaluation. The key is making each mode shift explicit—announce it, change the rules, and give participants a moment to mentally switch gears.
What is Double Diamond used for beyond design?
The Double Diamond's divergent-convergent pattern applies to any complex problem-solving context: strategy development, policy creation, scientific research planning, and organizational change. Any situation where you need to first understand a problem broadly before narrowing to a solution benefits from this structured mode alternation.
How do I handle team members who resist divergent thinking?
Some team members—often engineers or senior leaders—default to convergent thinking because they're rewarded for decisiveness. Help them by framing divergence as a risk-reduction strategy: 'We're spending 2 hours exploring options now to avoid spending 2 months building the wrong thing.' Also, give structured divergent activities (like Crazy 8s) rather than open-ended brainstorming, which can feel aimless.
Is the Double Diamond always two diamonds, or can there be more diverge-converge cycles?
The classic model uses two diamonds, but real projects often require additional cycles. You might diverge and converge three times in the problem space before feeling confident in your problem definition. The important principle is maintaining the diverge-before-converge rhythm—each expansion should be followed by a deliberate contraction before the next expansion begins.