The Implement Phase Most Teams Skip (and Why Products Die There)

Most design thinking curricula end with a prototype demo and applause. The team takes photos. Leadership nods. Then someone asks: Who owns launch? Silence.

That gap is not a minor oversight. It is where a large share of product failure actually happens - not in the workshop, but after it.

Where classic frameworks stop

Double Diamond ends at Deliver. The Stanford five-stage model ends at Test. Both are valuable. Both teach divergent and convergent thinking in Problem and Solution spaces.

But in real organizations, Test is not the finish line. Shipping is not adoption. Adoption is not sustained value. Teams that treat Deliver or Test as the end point often discover - six months later - that the product exists but nobody changed behavior.

The Growth Diamond Model adds Market space and an explicit Implement phase for exactly this reason.

What Implement actually covers

Implement is not "marketing owns it now." In the Growth Diamond Model, it includes:

• Prepare to launch - readiness, rollout plan, support model
• Influencing the decision - executive and stakeholder alignment so the solution survives contact with the org chart
• Crossing the chasm - moving from early adopters to mainstream users
• Solution enhancement - feedback loops after launch, not only before

These are design thinking activities in the sense that they stay user-centric - but they require product leadership, communication, and operational follow-through that workshops rarely practice.

Explore the full phase in the Academy Implement introduction and the chapter on Crossing the Chasm.

Three signs your team skipped Implement

• Launch is a date on a calendar, not a plan. There is no owner for adoption metrics, training, or post-launch support.
• Success is defined as "released," not "used." The team celebrates deployment; nobody tracks whether the user pain from Empathize was actually reduced.
• Enhancement is reactive firefighting. Without a structured feedback path from Market space back to Problem space, teams patch symptoms instead of learning.

If these sound familiar, the fix is not another ideation sprint. It is treating Implement with the same rigor you gave Define.

How Implement connects back to the rest of EDIDI

The Growth Diamond Model is iterative. Implement is not a one-way exit:

• Poor adoption may send you back to Define - was the problem statement wrong?
• Unexpected use patterns may require Ideate again
• Scale or quality gaps send you back to Develop

That is why PSM (Problem, Solution, Market) is a loop, not a line. Market space informs the next cycle of Problem space.

A practical starting point

Before your next release, answer these four questions:

1. Who is the first user segment we must win (not "everyone")?
2. What behavior change proves adoption in the first 90 days?
3. Who owns launch communication and post-launch feedback?
4. What is the enhancement backlog trigger - support tickets, usage data, or scheduled review?

If you cannot answer all four, you are not ready to leave Implement - even if Develop is done.

Bottom line

Products do not fail because teams skip empathy. They fail because they stop caring about the user the moment the prototype ships. Implement is where design thinking proves it was worth the workshop.

For the full framework, see the Methodology guide. To go deeper on why products fail upstream, read Why 80-95% of Products Fail. To compare frameworks, read Design Thinking vs Double Diamond.

Want help applying Implement with your team? Book a 15-minute call.