Design Thinking isn’t dead — it was never what we thought it was

When the Harvard Business Review gave Tim Brown a feature spread in 2008, Design Thinking was still a term from the orbit of IDEO and the Stanford d.school. Ten years later it was a global phenomenon — complete with consulting firms, workshop certificates, and sticky-note excess in every other open-plan office from Hamburg to Singapore. Five more years, and it was publicly declared dead.

Both narratives — the messianic rise and the proclaimed death — miss what Design Thinking actually is as a practice. This article attempts a sober accounting: what has empirical evidence behind it, what doesn’t, and where the method’s lasting value lies.

Where the method comes from

The core idea traces back to two lines. First: Herbert Simon’s The Sciences of the Artificial (1969), which describes the designer as someone who changes “existing situations into preferred ones.” Second: the practice of industrial design in the 1980s, above all at IDEO — one of the first organizations to frame design as a problem-solving discipline rather than an aesthetic one.

Tim Brown’s 2008 HBR article condensed these lines into a three-stage cycle: Inspiration → Ideation → Implementation. The Stanford d.school later formalized five phases (Empathize, Define, Ideate, Prototype, Test) that have shown up in every bootcamp since. Both frameworks were conceived as pragmatic tools, not derived scientifically.

Where the critics have a point

Roger Martin, one of the method’s most prominent advocates, published one of its sharpest critiques in the MIT Sloan Management Review in 2019: inside companies, Design Thinking becomes performance — a ritual that simulates innovation without producing it. “Empathy maps” get filled in without anyone ever talking to a real customer. “How might we” questions emerge from the workshop facilitator’s gut feeling. Prototypes are presentation slides, not testable artifacts.

In 2023, Jon Kolko sharpened the debate in a widely cited Fast Company piece: Design Thinking, he argued, had been watered down into a marketing instrument — while the designers who took the method seriously had mostly stopped calling it that.

Both critiques hit something real. But what they hit is the pop Design Thinking workshop, not the method in its original form.

What the evidence shows

Jeanne Liedtka documented fifty Design Thinking projects across organizations of different sizes over seven years — one of the most substantial studies on the subject (HBR 2018). Her finding is nuanced: Design Thinking works, but not through the tools themselves. It works because it forces certain social dynamics:

1. It forces teams to talk to users before jumping to solutions.
2. It makes implicit assumptions explicit — and therefore debatable.
3. It shifts discussions from “Who is right?” to “What is the prototype teaching us?”

These three effects — user contact, explicit assumptions, prototype focus — are, empirically, the core of what Design Thinking delivers. Everything else — sticky notes, empathy canvases, the Five Whys — are tools that can enable these effects but don’t guarantee them.

Design Thinking is not a method. It is a social mechanism that forces teams into better behavior — when it is applied correctly.

The McKinsey Design Index study (2018) adds economic data: companies in the top quartile of design excellence achieved 32% higher revenue growth and 56% higher shareholder returns over five years than their industry averages. Note, though, that McKinsey’s “design excellence” did not mean “Design Thinking workshops” — it was operationalized through consistent user research, iterative prototyping, and measurable customer satisfaction metrics.

What actually delivers ROI — and what doesn’t

From the available evidence, five practices stand out as highly effective:

Effective:

• Structured user interviews at the start of a project (not: empathy maps without contact)
• Rapid prototyping at low fidelity, testable within a week
• Hypothesis-driven testing (with the assumption documented up front)
• Cross-functional teams collaborating continuously, not just at workshop moments
• Divergence before convergence in ideation rounds, cleanly separated

Less effective, or pure performance:

• Empathy maps without real interviews
• Persona workshops without validation
• How-might-we phrasing as an end in itself
• Design sprint rituals (five days, no follow-up iteration)
• Sticky-note walls standing in for deliverables

The second group isn’t worthless — but it only creates value in combination with the effective practices. In isolation, it becomes what Roger Martin calls design theatre.

Where empathy tools help — and where they don’t

Empathy maps, customer journey maps, and personas sit at the center of pop Design Thinking. They are also the method’s most abused tools.

They help in one specific configuration: after real user interviews, with a psychologically differentiated foundation, in dialogue with the product team. An empathy map built from three quotable user statements is a condenser. An empathy map built from assumptions is a mirror — it reflects what the team already thought.

The same principle applies to personas. We made the case in our article on what personas actually deliver that personas only work when they get quoted. The extended version of that thesis: every Design Thinking artifact only works when it gets quoted. A canvas nobody opens produces no insights.

Where the practice is heading

Three developments are emerging that complement Design Thinking rather than replace it:

First: more evidence up front, less ideation at the end. Teams are shifting resources into the problem-definition phase. The assumption behind it: teams that understand the problem precisely need less workshop creativity at the end.

Second: continuous prototype testing instead of sprints. Rather than five-day design sprints, teams work in rolling prototype cycles of two to three weeks. The sprint logic is increasingly seen as too episodic.

Third: AI-augmented research phases. Synthetic personas are increasingly used in the early phases — not as a replacement for real user research, but as a first filter. A team can stress-test ten hypotheses in an hour before committing to expensive, time-consuming interviews with real users. This development is recent enough that the empirical evidence is only now emerging (see Stanford HAI, Park et al., 2024).

What remains

Design Thinking is not dead. What’s dead is the promise that five days of sticking notes to a wall will save a business model. What remains is a set of social mechanisms that — applied consistently — raise the odds of user-centered decisions.

The most honest summary comes from Jeanne Liedtka’s 2018 HBR article, in essence: Design Thinking works because it functions as a social technology — what gets institutionalized is not the workflow but the permission to think differently.

That permission — the social license to question assumptions before writing code — is what the method delivers at its best. If you’re looking for it, you can find it without a certificate and without a workshop vendor. If you ritualize it, you won’t find it at all.

If you want to move faster in the empathy phase without losing quality, you can use our method: eight psychological layers per Persona, orchestrated in a logic that approximates real user complexity. No workshops, no sticky notes — and no substitute for talking to real people.