Design Thinking

Design thinking is a human-centered problem-solving approach that moves through five stages: empathise, define, ideate, prototype and test.

beginner

It combines empathy for users, creativity in generating solutions, and rationality in testing them. The point is to solve the right problem, not the first one that came to mind. It is iterative by nature, because the first understanding of a problem is usually incomplete.

How it works

The five stages are not a straight line. They loop.

Empathise. Understand the people you are designing for through observation, interviews and immersion. The goal is to understand what they actually do and struggle with, not what they say they would do.
Define. Turn those insights into a clear problem statement. A good problem statement focuses the work without prescribing the solution. "Freelancers lose invoices in their inbox" points somewhere. "Freelancers need a better inbox" points at a feature.
Ideate. Generate many ideas without judging them early. The goal is coverage, not quality. The best idea rarely appears on the first pass.
Prototype. Build quick, inexpensive representations of the most promising ideas. A sketch, a wireframe, a clickable prototype. The goal is to make the idea tangible enough to test.
Test. Put the prototype in front of real users and watch what happens. The goal is evidence, not approval. Findings loop back to any earlier stage.

When to use it

Design thinking is most useful when the problem is genuinely uncertain and the cost of getting it wrong is meaningful.

Early in a product or feature, before the solution is known.
When existing data and assumptions are contradictory.
When the team keeps arriving at the same first idea and wants to push past it.

It is less useful when the problem is well understood and the work is execution. Applying a five-stage process to a login screen that needs a contrast fix is overkill.

Common mistakes

Confusing ideation with the whole process. Generating ideas is one stage. Skipping empathy and definition means you are solving the wrong problem creatively.
Requiring consensus in ideation. Early ideas are meant to be diverse, not approved. Judging during ideation kills the ideas that look strange but might be right.
Testing with people who are not the users. A team testing its own prototype validates what the team already believes. Five people from the target audience will surface problems the team cannot see.
Stopping at the prototype. A prototype that is never tested is just an expensive sketch. The test is the point.
Treating it as a one-time exercise. Design thinking is a habit, not an event. Problems reappear as products evolve.

Key takeaways

Design thinking is a five-stage loop: empathise, define, ideate, prototype, test.
The stages are not sequential. Findings from testing often send you back to redefine the problem.
Empathy is not a nicety. It is the stage that prevents building the wrong thing well.
Ideation is for coverage, not approval. Judging early kills the ideas that look strange.
A prototype without a test is a sketch with a higher price tag.

No lessons cover this yet

This term is defined ahead of the curriculum — the definition above stands on its own, and lessons will link here once they exist.

Browse what is published

Common questions

How is design thinking different from user-centered design?: They overlap heavily, and the terms are often used interchangeably. User-centered design is the broader principle that products should be built around the needs and behaviour of real users. Design thinking is one specific methodology for doing that work, with its own stages and techniques. You can practice user-centered design without calling it design thinking, and you can use design thinking without fully living the principle. The difference is in the label, not the goal.
Does design thinking produce better ideas or just more ideas?: Both, but only when the earlier stages are done seriously. Empathy and definition ensure you are generating ideas for the right problem. Ideation produces volume. Testing filters that volume down to what actually works. Skip empathy and you get many ideas for the wrong problem. Skip testing and you get many ideas with no evidence. The value of the process is the loop, not any single stage.
When is design thinking overkill?: When the problem is well understood and the work is execution. A team applying a five-stage process to a button that needs a colour contrast fix is wasting time. Design thinking is worth the overhead when the problem is genuinely uncertain, the cost of getting it wrong is meaningful, and the team keeps arriving at the same first answer. Otherwise the discipline is heavier than the problem.