Improving the Double Diamond Design Process

Why the Double Diamond Needs Improvement

The Double Diamond design process, developed by the British Design Council in 2003, has become one of the most widely recognized frameworks for describing the design and innovation process. Its elegant visualization of diverging and converging thinking across four phases has made it a staple in design education and practice worldwide.

However, the traditional Double Diamond represents an idealized view that rarely matches the messy reality of project delivery. This guide examines common criticisms and provides actionable strategies to improve your design process.

What You'll Learn

• The core principles of the traditional Double Diamond framework
• Why the idealized model often falls short in practice
• Evidence-based improvements to make the framework more effective
• Practical tools and techniques for each phase

Understanding the Traditional Double Diamond

The Double Diamond is a visual representation of the design process featuring two diamonds that represent the two main stages of design work. Each diamond contains both divergent and convergent thinking, creating a rhythm of exploration and focus.

The Four Phases Explained

Phase 1: Discover

The first phase is all about understanding the problem space. Teams immerse themselves in research, gathering insights about users, the market, and the broader context. Key activities include user interviews, market analysis, competitive research, and observational studies.

Phase 2: Define

After gathering research, the Define phase focuses on synthesizing findings and framing the problem clearly. Teams identify patterns, develop personas and user journeys, and create a concise problem statement.

Phase 3: Develop

The Develop phase is characterized by creative exploration and ideation. Teams generate a wide range of ideas through brainstorming, sketching, prototyping, and iterative testing.

Phase 4: Deliver

The final phase focuses on implementation and refinement. Teams test solutions at small scale, reject approaches that won't work, and iteratively improve the ones that show promise.

Why the Traditional Double Diamond Falls Short

Despite its widespread adoption, the traditional Double Diamond has several limitations that can hinder practical application:

1. Linear Illusion

The Double Diamond suggests a clean, linear progression through distinct phases. In reality, design work rarely follows such a tidy path--teams frequently need to revisit earlier phases and iterate based on new insights.

2. Stakeholder Reality Gap

The traditional framework positions designers as primary drivers with significant latitude to explore. In most contexts, stakeholders have already defined the problem space before designers are engaged. Effective UX design services help navigate these constraints while ensuring alignment with web development best practices.

3. Delivery Oversimplification

The Deliver phase appears straightforward--test, refine, implement. However, bringing designs to market involves complex coordination, technical constraints, and changing requirements that the framework doesn't fully address.

4. Iteration Ambiguity

The framework doesn't explicitly address when to cycle through diamonds multiple times or when additional iteration is needed for complex projects.

5. Team and Context Blindness

The one-size-fits-all model doesn't account for team dynamics, organizational culture, or project constraints that vary significantly across teams.

Proposed Improvements to the Double Diamond

Andy Budd's Triple Diamond Approach

Andy Budd proposed the "Triple Diamond" approach, recognizing that the space between the two diamonds is where design has the most leverage. His approach adds an explicit "bridge" phase that addresses translating insights into action and emphasizes stakeholder management throughout the process.

The Framework for Innovation

The Design Council evolved the Double Diamond into the "Framework for Innovation," which acknowledges that learning can send teams back to earlier phases and that making and testing early-stage ideas can be part of discovery. This evolution reflects how modern design thinking approaches iterative work and complements our bespoke web design methodology.

Flexible Phase Implementation

Rather than following a rigid sequence, effective teams adapt the framework to their context:

• Running concurrent phases when timelines are tight
• Embedding discovery activities throughout the project
• Using lightweight Define activities to maintain momentum
• Treating delivery as ongoing iteration rather than completion

The key is using the framework as a mental model, not a rigid prescription.

Implementing an Improved Design Process

Enhancing the Discover Phase

• Expand research methods beyond interviews and surveys to include observational research and analytics review
• Involve cross-functional stakeholders early to build shared understanding and reduce misalignment
• Document insights systematically in accessible repositories for reference throughout the project
• Continue discovery throughout the project, not just at the beginning, to catch new insights

Strengthening the Define Phase

• Develop clear problem statements specific enough to guide decisions but broad enough for creative solutions
• Create shared artifacts like personas and journey maps that evolve as understanding deepens
• Establish explicit decision criteria before ideation begins to keep focus on outcomes
• Validate problem definitions with stakeholders before proceeding to ensure alignment

Elevating the Develop Phase

• Embrace structured ideation techniques like SCAMPER and bodystorming for novel ideas
• Prototype at the right fidelity for what you're testing--low-fidelity for concept validation
• Test with real users early and often to maximize learning opportunities
• Document alternatives considered for future reference and team learning

Transforming the Deliver Phase

• Treat delivery as iteration, not completion--plan for post-launch improvement from the start
• Build continuous feedback mechanisms through analytics, support tickets, and ongoing testing
• Coordinate closely with implementation teams to prevent good ideas from being lost in handoffs
• Measure outcomes, not just outputs--define success metrics early and track them rigorously

Common Pitfalls and How to Avoid Them

Skimping on Discovery

When timelines are tight, discovery is often shortened--false economy that leads to flawed problem definitions and solutions that miss the mark.

Prevention: Build discovery time into project plans from the start and protect it from compression.

Premature Convergence

Pressure to converge quickly locks teams into directions before fully exploring the problem space.

Prevention: Use explicit convergence criteria and resist stakeholder pressure to converge early.

Over-Prototyping

Excessive investment in high-fidelity prototypes creates sunk cost bias that makes abandoning ineffective approaches harder.

Prevention: Match prototype fidelity to what you're testing--use low-fidelity for concept validation.

Neglecting Delivery

Some teams treat delivery as someone else's problem, but implementation quality dramatically affects outcomes.

Prevention: Stay engaged through delivery and plan for post-launch iteration from the start.

Conclusion

The Double Diamond framework has endured for over two decades because it captures something essential about the design process--the rhythm of exploration and focus. But the traditional model doesn't fully reflect how design work actually unfolds in organizations.

By understanding the framework's limitations and implementing evidence-based improvements, teams can create design processes that are more realistic and effective. The key is to use the framework as a mental model for thinking about design work, not as a rigid prescription.

The improved Double Diamond acknowledges that design is iterative, that stakeholder management is integral, and that delivery is just the beginning of ongoing learning. By embracing these insights, teams can achieve better outcomes for users and businesses alike.

Looking to improve your organization's design process? Our web development services include UX design and process optimization to help teams work more effectively. We also offer AI-powered automation solutions that can streamline your design-to-development workflow.

Sources

1. Design Council: The Double Diamond - The official source for the canonical four-phase model from the British Design Council
2. Smashing Magazine: Improving The Double Diamond Design Process - Andy Budd's comprehensive critique and Triple Diamond proposal
3. LaunchNotes: The Double Diamond Framework - Practical implementation guidance and phase breakdowns