Design Thinking
A human-centred, five-stage process for uncovering real problems and prototyping solutions with users
8 min · IDEO / Stanford d.school
What is this framework?
Design Thinking is a step-by-step way to solve problems by starting with people, not ideas. You empathise with users, define their real problem, brainstorm ideas, build rough prototypes, then test them and repeat until something genuinely works for the people you're helping.
Design Thinking became popular through IDEO and Stanford's d.school as a way to make innovation more reliable and less reliant on lone genius. Instead of jumping straight to a solution, teams are trained to slow down at the front end and deeply understand the humans they are designing for, using observation and conversation rather than assumption.
The five stages — Empathise, Define, Ideate, Prototype, Test — are not strictly linear. Teams loop back constantly: a failed test might send you back to redefine the problem, and a surprising interview might spark a completely new idea. This iterative, non-linear rhythm is the point, because early ideas are rarely the right ones.
For student entrepreneurs, Design Thinking is valuable because it forces contact with real users before money and time are spent building. A rough cardboard prototype tested with five real customers usually reveals more than weeks of solo planning.
What problem does it help solve?
- Avoid building something nobody actually wants
- Turn vague frustrations into a clear, testable problem statement
- Generate a wide range of possible solutions before committing to one
- Get honest, cheap feedback before investing real money
- Build empathy and reduce your own biased assumptions about users
The framework
The process loops back at any stage when new insight appears.
Every part explained
Empathise
Immerse yourself in the world of the user through observation, interviews and shadowing to understand their real experience.
Ask: What do people actually do, say, think and feel — not what do I assume they feel?
Example: Watching students queue for lunch and noticing they check their phones anxiously as class time approaches.
Define
Synthesise your observations into a single, sharp problem statement focused on a specific user and need.
Ask: What is the real, specific problem worth solving here?
Example: "Second-year students need a faster way to get affordable lunch because their 50-minute break isn't enough to queue and eat."
Ideate
Generate a large volume of possible solutions without judging them, deferring criticism to encourage bold thinking.
Ask: What are as many ways as possible we could address this problem?
Example: Brainstorming pre-ordering apps, vending machines, meal subscriptions and shared delivery runs.
Prototype
Build the cheapest, fastest version of an idea that lets you learn something — sketches, paper mock-ups, or a simple landing page.
Ask: What is the smallest thing we can make to test this idea?
Example: A paper mock-up of an app screen showing a pre-order menu, shown to classmates for reaction.
Test
Put the prototype in front of real users, observe their reactions, and use what you learn to revise or rethink.
Ask: What did users actually do, and what does that tell us to change?
Example: Students loved pre-ordering but were confused about pickup location, prompting a redesign of that screen.
Worked example — CampusEats
The CampusEats founders used Design Thinking to move from a vague idea of "campus food is annoying" to a testable app concept.
Empathise
Interviewed 20 students and 5 nearby vendors; shadowed lunch queues for three days.
Key observation
Students often skip lunch or eat unhealthily because queues eat their entire break.
Define
Busy students need a way to secure affordable food without losing their break time to queuing.
Ideate
Generated 18 ideas including lockers, pre-order apps, staggered class-based ordering, and vendor bundling.
Prototype
Built a clickable Figma mock-up of a pre-order and pickup-slot app.
Test
Ran the mock-up past 15 students; most wanted a live queue counter, which wasn't in the first design.
Iteration
Added a live pickup countdown to the next prototype version before any code was written.
Only after two prototype-test loops did the team commit to building the real app, saving months of wasted development.
How to use it
- 1Set aside assumptions and go observe or talk to real users in their own context.
- 2Cluster your notes and write one focused problem statement about a specific user.
- 3Run a timed brainstorm generating quantity over quality, deferring judgement.
- 4Pick 1-3 promising ideas and build the cheapest possible prototype of each.
- 5Show prototypes to real users and watch what they do, not just what they say.
- 6Capture what you learned and decide whether to refine, pivot or move forward.
- 7Repeat the loop until the solution reliably solves the defined problem.
Try it yourself
Work through each stage for your own venture idea.
Empathise
Define
Ideate
Prototype & Test
Your work stays on this device. Nothing is uploaded, so use the same browser to come back to it.
When to use it
- At the very start of exploring a new venture idea
- When you suspect you're solving a problem you don't fully understand yet
- Before writing code or spending money on a full build
- Whenever a launched product isn't getting the reaction you expected
When not to rely on it
This framework does not prove:
- • It does not prove that people will pay for the solution, only that they respond well to it
- • It does not guarantee a workable business model or unit economics
- • It does not replace market-sizing or competitive analysis
- • Small numbers of interviewed users may not represent the wider market
Common mistakes
- Skipping straight to Ideate or Prototype without genuine empathy work
- Writing a solution disguised as a problem statement (e.g. "users need an app")
- Testing prototypes only with friends and family who won't give honest feedback
- Treating the process as strictly linear instead of looping back when needed
Connections
Related concepts
Related frameworks
Quick check
In Design Thinking, what should happen immediately after Empathise?
Remember this
Design Thinking succeeds when you fall in love with the problem before you fall in love with any solution.