Catalog
method#Product#Delivery#Governance#Software Engineering

Double Diamond

A four-phase design framework (Discover, Define, Develop, Deliver) for structured problem discovery and solution development.

Double Diamond is a structured four-phase design method (Discover, Define, Develop, Deliver) that guides teams from problem exploration to validated solutions.
Established
Medium

Classification

  • Medium
  • Organizational
  • Organizational
  • Intermediate

Technical context

Product management tools (roadmaps, backlogs)Analytics and user research platformsPrototyping and usability testing tools

Principles & goals

Separation of divergent and convergent phasesUser-centeredness and evidence-based approachEarly validation before large-scale implementation
Discovery
Enterprise, Domain, Team

Use cases & scenarios

Compromises

  • Incomplete user research leads to false assumptions
  • Stakeholder overload from too many divergent options
  • Skipping validation steps increases implementation risk
  • Early involvement of stakeholders and decision makers
  • Define clear kill criteria for experiments
  • Regularly document insights and decisions

I/O & resources

  • Access to user data and analytics
  • Interdisciplinary team members
  • Stakeholder support and time
  • Validated problem statements
  • Prototypes and test results
  • Decision basis for implementation

Description

Double Diamond is a structured four-phase design method (Discover, Define, Develop, Deliver) that guides teams from problem exploration to validated solutions. It separates divergent and convergent thinking to reduce risk and increase clarity. Widely used in product design, it supports stakeholder alignment and iterative learning.

✔

  • Reduces risk through staged validation
  • Improves stakeholder alignment
  • Enables focused prototyping and learning

✖

  • Can be misunderstood as linear, though intended iterative
  • Requires time and resources for thorough discover phase
  • Less suitable for purely technical refactors without user focus

  • Time to validated learning

    Measures time from start of discover phase to a validated hypothesis.

  • Number of hypotheses tested

    Counts validated and discarded hypotheses in a cycle.

  • Prototype-to-release conversion rate

    Ratio of prototypes that lead to production releases.

Design Council case example

Description of Double Diamond use in public projects for user-centered design.

Product development in SME software

Using the model to quickly validate customer needs before development.

Innovation workshop at a bank

Series of workshops using discovery phases to identify new service offerings.

1

Set up an interdisciplinary core team and align sponsors.

2

Conduct focused discover activities: interviews, data analysis, observation.

3

Define workshops to synthesize and prioritize insights.

4

Develop iterations with prototypes and user tests.

5

Deliver piloting, monitoring and scaling of successful solutions.

⚠️ Technical debt & bottlenecks

  • Prototypes promoted to production without refactoring
  • Insufficiently documented research outcomes hinder later decisions
  • Outdated assumptions remain in backlog without review
Limited research resourcesStakeholder decision processesTechnical integration constraints
  • Using Double Diamond only as phase checklist without iteration
  • Labeling shallow research activities as discover
  • Forcing convergence before valid data is available
  • False expectation that the model always runs linearly
  • Premature resource commitment for implementation without validation
  • Unclear success criteria before starting phases
Facilitation and workshop moderationUser research and interviewing skillsRapid prototyping and testing
User-centricity in solution developmentRapid validation to reduce riskCross-functional collaboration
  • • Time constraints for thorough discovery
  • • Budget limits for prototyping
  • • Organizational silos hinder cross-functionality