Design Thinking
Design Thinking is a five-stage process, empathise, define, ideate, prototype, test, for solving problems by starting from what users actually do rather than what you assume they need.
Five stages run in a loop rather than a straight line, with an arrow curling back from test to empathise.
Reach for this when…
- You've built something to spec and users still don't want it.
- Nobody agrees what the real problem is, so every meeting produces a different fix.
- You need to test a rough idea before committing serious money to it.
How to run it
- Empathise: watch and talk to the people who have the problem, not just those describing it.
- Define: state the real problem in one sentence, from the user's side.
- Ideate: generate a wide range of possible solutions before judging any of them.
- Prototype: build the cheapest, roughest version that tests the idea.
- Test: put it in front of real users and watch what actually happens.
A worked example
Situation. Neema Mushi ran Maji Bora, a small water-access NGO working in villages outside Dar es Salaam, Tanzania, whose new filter design kept sitting unused in people's homes.
Applied. Instead of redesigning the filter again, her team spent a week properly doing the empathise and define stages, sitting with households and learning the problem wasn't the water, it was that cleaning the filter took too long each morning.
Result. The prototype that tested well wasn't a better filter, it was a faster cleaning cradle. Adoption more than doubled within two months.
The catch
Design Thinking is often taught as five tidy stages when the real work loops back constantly - teams that treat it as a straight line skip back to empathise too rarely and ship a prototype nobody asked for. It's also weak on problems that need deep technical or regulatory expertise rather than user insight.
If your first idea survives untouched through 'ideate', you didn't really do it.
Origin: IDEO; Stanford d.school