What is design thinking? User-centred design
Design thinking is a problem-solving method that starts with people, not with a product. Designers ask: who is the user, what do they really need, and why?
It is user-centred: users are involved at every stage. It is iterative: you go round the stages again and again, improving each time. A systems approach also looks at the whole: materials, making, cost, use and disposal.
Double diamond
Good designers open up (diverge: explore widely) and then narrow down (converge: choose) twice: first to find the right problem, then to find the right solution.
Empathise and define: understanding the user
Empathise means understanding someone's experience from their side. Methods: interviews, watching people use a product, trying it yourself (for example, opening jars wearing thick gloves), surveys.
Empathy map
An empathy map has four boxes about the user: what they Say, Think, Do and Feel. Gaps between them are clues. Asha says "I'm fine", but she does ask neighbours for help and feels embarrassed.
Define: write a short problem statement. A good one is about the user's need, not a fixed solution: "How might we help Asha open jars without pain?" (not "design a jar-opening machine"). This is problem finding.
Ideate: creative approaches and biomimicry
Ideate means create many ideas. Rules: quantity first, no judging yet, build on others' ideas, wild ideas welcome.
- Brainstorming and mind maps (visual thinking: put the problem in the middle and branch out).
- SCAMPER: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse.
- Sketching: quick drawings and sticky notes to organise ideas into groups.
- Biomimicry: copying solutions from nature. Burrs on a dog's fur → hook-and-loop fastener (Velcro). Kingfisher beak → quieter nose of Japan's Shinkansen bullet train. Gecko feet → grippy surfaces.
Then converge: compare ideas against the user's needs and pick the best one or two.
Prototype, test and iterate
A prototype is a quick, cheap model used to test an idea: paper, card, clay, foam, a 3D print, or a clickable screen sketch for an app. Low-fidelity (rough) prototypes are fast; high-fidelity ones look and work like the real thing.
Test with real users. Watch, do not explain too much, and ask open questions: "What was hard?" Record what works and what does not.
Feedback sends you back: maybe to ideate again, or even to redefine the problem. Each loop is an iteration. "Fail early, fail cheap" means finding problems with a card model, not after making 10,000 products.
Key formulas and definitions
- Design thinking stages = Empathise → Define → Ideate → Prototype → Test (and loop back)
- Empathy map = Says · Thinks · Does · Feels
- Problem statement = "How might we [help user] [do something] [so that need is met]?"
- Diverge = open up, many options; Converge = narrow down, choose
- Biomimicry = design ideas copied from nature
- Prototype = quick, cheap model to test an idea
- Iteration = one loop of test → learn → improve
Worked examples
1. Write a 'How might we' statement for students whose school bags are too heavy.
"How might we help students carry what they need each day without back pain?" It names the user and the need, and does not fix the solution (it could be lockers, a timetable change or a better bag).
2. Fill an empathy map for a new student on the first day.
Says: "Where is room 12?" Thinks: "Will anyone sit with me?" Does: stays near the door, checks the phone. Feels: nervous, lonely. Need found: a friendly guide and clear signs.
3. Give a biomimicry idea for a building that stays cool without air conditioning.
Termite mounds keep cool with air channels that let hot air rise out. A building can copy this with chimneys and vents (as the Eastgate Centre in Harare, Zimbabwe, does).
4. Your card prototype of a phone stand falls over when tested. What next?
This is useful feedback. Iterate: widen the base or lower the angle, make a new quick card model, and test again with the user before using real materials.
Common mistakes
- Jumping straight to a solution before understanding the user.
- Writing the problem as a fixed product ("design an app") instead of a need.
- Judging ideas during brainstorming, so fewer ideas are made.
- Making an expensive, perfect prototype first, so it is hard to change after testing.