Design Thinking vs Double Diamond: Which Framework When?

If you search for design thinking frameworks, two names appear everywhere: the Double Diamond (British Design Council) and the five-stage model popularized by Stanford d.school (Empathize, Define, Ideate, Prototype, Test). Both are excellent. Both are widely taught. And both leave the same gap in real product work - which is why teams still ask which one to use, and what to do after the workshop ends.

This article compares the Double Diamond with mainstream design thinking practice, explains where each shines, and points to when you need a framework that extends into launch and market adoption.

What the Double Diamond actually is

The Double Diamond model divides work into four phases across two diamonds:

• Discover (diverge) - explore user context, observe pain, gather insight
• Define (converge) - synthesize into a clear problem statement
• Develop (diverge) - generate and explore multiple solution directions
• Deliver (converge) - test, refine, and ship the best solution

Its core strength is making divergent and convergent thinking explicit. Teams see when to expand options and when to narrow. That alone prevents many workshops from jumping to solutions too early.

The 2019 update added feedback loops from Develop and Deliver back to Define and Discover, plus emphasis on leadership and cross-functional engagement - acknowledging that design thinking is not a solo designer activity.

What "design thinking" usually means in practice

In most classrooms and companies, "design thinking" refers to a five-phase loop: Empathize, Define, Ideate, Prototype, Test. The phases map closely to the Double Diamond, but the naming emphasizes user empathy and rapid experimentation.

Double Diamond	Common design thinking (d.school)
Discover	Empathize
Define	Define
Develop	Ideate
Deliver	Prototype + Test

They are not competing religions. They are the same underlying logic with different labels and diagrams. Both stress user-centricity, iteration, and cross-functional collaboration.

For a deeper comparison of Honeycomb and Double Diamond models, see the Academy chapter on existing models.

Where both models work well

Use Double Diamond or classic design thinking when:

• The problem is fuzzy but human. You need to understand user pain before committing engineering effort.
• Stakeholders disagree on the problem. The first diamond forces shared language before solution debates.
• You have time for structured discovery. Even a compressed sprint benefits from explicit diverge/converge checkpoints.
• You are teaching the mindset. MBA classrooms, innovation labs, and early-stage product teams need a memorable, repeatable process.

In these contexts, either model builds the habits that matter: listen before you solve, define before you build, test before you scale.

Where both models fall short

After 20+ years leading product and program work at global MNCs, I have seen the same pattern repeat: teams finish a strong Discover/Define or Empathize/Define cycle, run a creative Ideate/Develop session, ship a prototype - and then lose the thread at launch.

Neither the Double Diamond nor the standard five-stage model fully addresses:

• Product management depth in Develop. Roadmaps, release planning, acceptance criteria, and build-test cycles at scale are thin in most design thinking curricula.
• Market space after Deliver. Adoption, positioning, crossing the chasm, and post-launch enhancement are rarely first-class phases.
• Operational governance. Large organizations need tools and mechanisms at each step - not just principles on a poster.
• Executive alignment through implementation. Influencing the decision, preparing to launch, and sustaining enhancement require explicit structure.

This is not a criticism of IDEO, Stanford, or the Design Council. Those models were built to teach creative problem-solving. Product organizations need that plus execution and market continuity.

Design thinking vs Double Diamond: which should you pick?

Short answer: For most teams, the choice between Double Diamond and five-stage design thinking is less important than how rigorously you run the first diamond (problem space) and whether you have a plan after Deliver.

Question	Lean toward Double Diamond	Lean toward five-stage (Honeycomb)
Audience is new to design thinking	Yes - the diamond visual teaches diverge/converge clearly	Yes - phase names are intuitive for workshops
You need government/enterprise language	Yes - widely used in UK/EU public sector	Less common in those contexts
You are running a university bootcamp	Either works; Double Diamond slides well in strategy courses	Either works; five-stage is familiar in US/Asia programs
You are a product team shipping software	Use either for discovery - then extend into build and launch explicitly	Same

If you are only choosing between these two, pick the one your stakeholders already recognize and execute it with discipline. The failure mode is not picking the wrong diagram. It is skipping Empathize/Discover and treating Define as a formality.

When you need a third path: Problem, Solution, and Market space

The Design Thinking Growth Diamond Model™ (PSM + EDIDI) is an evolution of the Double Diamond framework. It emphasizes solution growth through iterative design, development, testing, and implementation - and recognizes that solution development often requires a broader exploration space than problem discovery alone. For practitioners who respect Double Diamond and Honeycomb thinking, it offers an end-to-end path:

• Problem space - Empathize & Define (aligned with the first diamond)
• Solution space - Ideate & Develop (aligned with the second diamond, with deeper product development tooling)
• Market space - Implement (launch, adoption, enhancement - often missing from classic diagrams)

The five phases - Empathize, Define, Ideate, Develop, Implement - keep the iterative spirit of design thinking while naming the work product teams actually do after the whiteboards are cleared.

Each phase includes defined tools and mechanisms, not just mindset reminders. That is the gap I saw repeatedly across automotive, e-commerce operations, and platform governance environments serving tens of thousands of users.

Explore the full framework free in the Academy, starting with What is Design Thinking? and the Growth Diamond Model overview.

A practical decision guide for your next initiative

Before your next workshop or sprint, answer these four questions:

1. Do we truly understand user pain - or are we assuming it? If assuming, invest in Discover/Empathize regardless of framework.
2. Do we have a written problem statement with success criteria? If not, do not Ideate yet.
3. What happens after we prototype? If the answer is vague, add explicit Develop and Implement planning now.
4. Who owns adoption after launch? If no one, your framework ends too early.

If questions 3 and 4 expose gaps, complement Double Diamond or five-stage design thinking with a market-space lens - or adopt a model that includes Implement as a first-class phase.

Bottom line

Double Diamond and mainstream design thinking are complementary, not contradictory. Choose based on audience familiarity, teach diverge/converge seriously, and do not treat Deliver or Test as the finish line if you are building products that must survive contact with real markets.

The teams that win are not the ones with the prettiest framework poster. They are the ones that stay user-centric from first interview to post-launch enhancement - and use a process honest enough to name every phase in between.

Want to go deeper? Read the Honeycomb / Double Diamond Academy chapter, explore the Growth Diamond Model methodology, compare Growth Diamond Model vs IDEO, or book a 15-minute call to discuss applying this with your team or classroom.