Design Thinking: The Five Stages
Design Thinking is a human-centered, iterative problem-solving methodology. Rather than jumping straight to a solution based on untested assumptions, it deliberately builds in steps to validate understanding of the actual problem and test potential solutions cheaply before committing significant resources.
1. Empathize
Directly engage with and observe the actual people experiencing a problem -- interviews, observation, immersion -- to develop genuine, first-hand understanding rather than relying on assumptions. Role-play or 'walking a mile' immersion techniques (actually attempting the current clunky process yourself) can surface friction points that secondhand accounts alone miss.
2. Define
WEAK: "Make expense reports better."
BETTER: "Busy field sales reps need a faster way to log expenses
on the go, because they currently lose receipts and forget details
by the time they're back at a desk to file a report."
[User] needs [need] because [insight]3. Ideate
How Might We reframing -- turns the problem statement into an
open-ended, opportunity-focused question:
"How might we help field reps log expenses without
needing to keep physical receipts?"
Deliberately generate a LARGE quantity of ideas without judging
them as they're proposed -- premature evaluation converges too
fast on the obvious, conventional solution.4. Prototype
Build the cheapest, quickest version that can actually be tested -- a paper sketch, a rough clickable mockup, a simple physical model. Discovering a fundamental usability problem in an afternoon is far cheaper than discovering it after weeks of building a fully-functional version.
5. Test
Put the prototype in front of real users and observe their actual reactions. 5-8 representative users testing a prototype tends to surface most major usability problems. Feedback should loop back to earlier stages (Define, even Empathize) rather than being treated as a final, one-way checkpoint.
The Process Is Iterative, Not Linear
A team might prototype and test an idea, learn something that changes their understanding of the actual problem, and loop back to Define or even Empathize again -- this non-linear looping is deliberate, not a failure of the process.
Keep your own version of these notes — editable, searchable, and organised by your stack.
Start free