What Design Thinking Actually Is
Design thinking is a five-stage problem-solving process - Empathize, Define, Ideate, Prototype, Test - developed and popularized by Stanford's Hasso Plattner Institute of Design (the d.school) and IDEO. Its core claim is narrow and useful: teams fail more often by solving the wrong problem well than by solving the right problem badly, so the framework front-loads understanding before anyone is allowed to propose a solution. It governs problem definition, not delivery (agile's job) or market validation (lean's job).
The Five Stages
- Empathize: interviews, observation, diary studies - real qualitative research, not a brainstorm about what users probably want. Output: raw notes and recordings, not conclusions yet.
- Define: synthesize the research into one problem statement, specific and human-centered. "Frequent travelers need a way to expense multi-currency receipts without manual entry - every hour spent on expenses is an hour not spent with a client" gives a team something to solve. "We need a mobile app for expenses" already assumes the answer.
- Ideate: generate volume before judgment. Brainstorming, crazy eights, forced analogies - the goal is quantity, because early evaluation anchors a team on its first idea.
- Prototype: build the lowest-fidelity version that tests the assumption in question. A prototype is a learning tool, not a deliverable - a paper sketch that answers the question beats a polished mockup that doesn't.
- Test: put it in front of real users. You're stress-testing the problem definition, not validating your solution. A failed test usually means looping back to Define, not iterating the prototype.
Where It Breaks in Practice
- Skipping Empathize: teams write a Define statement from what they already assume, then call it "user-centered" because a workshop happened.
- Solution-shaped problem statements: "users need a better dashboard" isn't a problem statement - it's a solution wearing a problem's clothing, and it forecloses the exploration the framework exists to protect.
- Treating five stages as five sequential steps: a test result that contradicts the Define stage should send the team backward. Run as a waterfall, design thinking keeps the ritual and loses the value.
- Polished prototypes tested too early: a finished-looking mockup signals sunk investment, and users hesitate to criticize something that looks done.
The Backlash Is Real, and Worth Taking Seriously
Design thinking's reputation took a real hit starting around 2018, when Pentagram partner Natasha Jen gave a widely circulated talk - "Design Thinking Is Bullshit" - arguing the framework had calcified into a Post-it-note ritual that substitutes process for rigor. The critique sharpened in 2023: MIT Technology Review's retrospective, "Design thinking was supposed to fix the world. Where did it go wrong?", traced how design-thinking engagements routinely produced workshops full of ideas and few implemented solutions, because the method addresses the front end of innovation without touching the organizational and budget constraints that actually kill projects. That October, IDEO - the firm most responsible for popularizing the method - cut roughly a third of its staff and closed its Munich and Tokyo studios, on top of an earlier 2023 round that had already shrunk headcount; the firm's revenue had fallen from roughly $300 million to $100 million in a few years, partly because companies had absorbed design thinking in-house and no longer needed to buy it as a service.
None of this means the five stages are wrong. It means the framework isn't self-executing: it structures how a team investigates a problem, but it has no answer for what happens when the organization around that team won't fund or ship what the investigation finds. Treat it as a discovery tool with a known failure mode, not a guarantee.
Design Thinking vs. Agile vs. Lean
These operate at different altitudes and aren't in competition. Design thinking defines the right problem. Lean tests whether a proposed solution is viable in the market. Agile delivers it iteratively. A team that only ever runs design thinking, without lean's market pressure-testing or agile's delivery discipline, is the team most likely to end up in a well-facilitated workshop that ships nothing.
Key Takeaways
- The five stages - Empathize, Define, Ideate, Prototype, Test - are iterative, not sequential; a bad test result should send you back to Define.
- The most common failure is skipping Empathize and writing a problem statement that already assumes its solution.
- The framework's real-world backlash - Natasha Jen's 2018 critique, IDEO's 2023 layoffs - is about implementation and organizational follow-through, not the five stages themselves.
- Design thinking governs discovery. It needs lean and agile alongside it to actually ship something.
