process & strategy
Design thinking
What is design thinking?
Design thinking is a human-centred way to tackle messy problems: understand real people, sharply define their problem, generate lots of ideas, build rough prototypes and test them - looping back as you learn. The point is to start from the human, not the solution.
Also known as: design thinking process, human-centred design process
Prefer to watch?
Watch the recap 0:39
The demo
The five stages of design thinking. Click through them - and notice how often a stage's real job is to send you back to an earlier one.
Empathise
Get close to the people you are designing for - interviews, observation, living with the problem - so you understand their world before you touch a solution. Everything downstream is only as good as this.
The arrows are not one-way: test routinely loops back to define or ideate, and a fresh insight can send you all the way back to empathise. It is a cycle, not a line.
What this demo shows (text version)
The five stages of design thinking, each selectable to reveal what it involves: empathise (understand real people), define (frame the right problem), ideate (generate many possible solutions), prototype (build rough, cheap versions) and test (put them in front of users).
Although usually drawn as a sequence, the process is iterative: testing feeds back into defining and ideating, and new understanding can restart the whole loop. The model is a guide to the kinds of thinking involved, not a fixed order to march through once.
Design thinking tackles messy problems by starting from real people rather than a solution: understand them, sharply define the problem, generate ideas, prototype roughly, test, and loop back as you learn. Its value is the discipline of staying with the human's problem long enough to solve the right thing, not the first thing.
You walked the five stages and saw the arrows run backwards as often as forwards. That is the whole idea: design thinking is not a tidy production line but a loop you ride until the problem and the solution genuinely fit.
The five stages - empathise, define, ideate, prototype, test - are a scaffold, not a schedule. In practice you jump and double back constantly: a test sends you back to redefine, a prototype reveals you misread the user. Treating the sequence as strictly linear is the most common way to do design thinking badly.
Its real value sits upstream, in empathise and define. Most failed products solve a problem nobody had, beautifully. Time spent making sure you are solving the right problem is worth more than any amount of polish on the wrong one.