Design Thinking for Beginners: The 5 Stages, Examples and How to Start

Design thinking is a problem-solving method that starts with people rather than products. Its best-known version, taught by Stanford University’s d.school, has five stages: empathise, define, ideate, prototype and test. Teams use it to understand what users really need, generate many possible solutions, and test cheap prototypes before spending serious money. This beginner’s guide explains each stage, the tools that go with it, real examples of it working and the common mistakes to avoid.

What Is Design Thinking?

Design thinking borrows the way designers work and applies it to almost any problem: a new app, a hospital waiting room, a school timetable or a small business’s checkout process. It became widely known through the design firm IDEO and Stanford’s Hasso Plattner Institute of Design, known as the d.school, in the 2000s. In a 2008 Harvard Business Review article, IDEO’s then chief executive Tim Brown described it as a discipline that uses a designer’s sensibility and methods to match people’s needs with what is technologically feasible and commercially viable.

Those three tests, often summarised as desirability, feasibility and viability, are the core of the approach. A good solution has to be something people want, something that can be built and something that can sustain itself financially.

What Are the Five Stages of Design Thinking?

The d.school model breaks the process into five modes. They are often drawn as a straight line, but in practice teams loop back whenever they learn something new.

1. Empathise: Who Are You Designing For?

The first stage is about understanding the people affected by the problem. Instead of starting with assumptions, the team observes, interviews and, where possible, experiences the situation itself. The goal is to uncover needs that people may not say out loud.

• Interviews: open questions such as “Tell me about the last time you…” produce better stories than “Would you use…?”
• Observation: watching how people actually behave often reveals workarounds and frustrations.
• Empathy maps: a simple chart of what users say, think, do and feel.

2. Define: What Is the Real Problem?

Next, the team turns its research into a clear problem statement. A common format is a “point of view” statement: [user] needs [need] because [insight]. This is then reframed as a “How might we…?” question, which is broad enough to invite creative ideas but specific enough to be useful. For example: “How might we make the first week at a new job less overwhelming for remote hires?”

3. Ideate: What Are the Possible Solutions?

In the ideation stage, the team generates as many ideas as possible before judging any of them. Quantity matters, because the best idea is often an unexpected combination of several weaker ones. Popular techniques include brainstorming with sticky notes, sketching, “worst possible idea” exercises that loosen up a group, and “Crazy 8s”, in which each person sketches eight ideas in eight minutes.

4. Prototype: How Can You Make the Idea Real?

A prototype is anything a user can react to: a paper sketch of an app, a cardboard model, a role-played service or a simple landing page. The key is to keep it rough and cheap. A prototype is a question in physical form, and the less you have invested in it, the easier it is to change or throw away.

5. Test: What Do Users Think?

Finally, the team puts prototypes in front of real users and watches what happens. Testing is not about defending an idea; it is about learning. Ask users to complete a task, note where they hesitate, and invite honest feedback. The results usually send the team back to an earlier stage, perhaps to redefine the problem or try a different idea.

How Is Design Thinking Different From Other Approaches?

Traditional planning often starts with a solution and then builds it in full before customers see it. Design thinking reverses that order by testing ideas early, when changes are cheap. It overlaps with other methods:

• The Double Diamond, published by the UK Design Council in 2004, describes a similar process in four phases: discover, define, develop and deliver, alternating between broad exploration and narrowing down.
• Lean Startup, popularised by Eric Ries, applies a build-measure-learn loop to new businesses, focusing on a minimum viable product.
• Agile software development delivers work in short cycles with regular feedback. Many teams use design thinking to decide what to build and agile methods to build it.

What Are Real Examples of Design Thinking?

Some well-known cases show how the method works in practice:

• GE Healthcare’s MRI Adventure Series. Designer Doug Dietz noticed that children were frightened of the MRI machine he had helped design, and many needed sedation to stay still. After observing children and consulting experts, his team redesigned scanning rooms as adventures, such as a pirate ship or a jungle, with scripts for staff. GE and Dietz have reported that the change significantly reduced the need for sedation and improved patient satisfaction.
• Airbnb’s early growth. In the company’s early days, the founders noticed listings with poor photos were struggling. Instead of relying only on data, they visited hosts in New York and photographed homes themselves, and they have said bookings improved quickly. The lesson, now widely retold, was to do things that do not scale in order to understand users.
• Bank of America’s Keep the Change. Developed with IDEO in the mid-2000s, the service rounded up debit card purchases and moved the difference into savings. It grew from research into how people actually handled money, including the habit of rounding up payments.

How Can Beginners Start Using Design Thinking?

You do not need a workshop or a big budget. Try a small project:

• Pick a real, narrow problem, such as reducing no-shows at your clinic or making your newsletter sign-up easier.
• Talk to five users this week. Ask about recent experiences rather than hypothetical preferences.
• Write one “How might we…?” question based on what you learned.
• Spend 30 minutes sketching ideas alone or with colleagues, aiming for at least 20.
• Build the simplest prototype of your favourite idea: a paper mock-up, a mock email or a short script.
• Test it with three to five people and note what surprises you.

Free resources from the Stanford d.school and IDEO’s design thinking site offer worksheets and exercises. If you are working on a new venture, design thinking pairs well with our guide to starting a business with no money, which emphasises testing demand before spending.

What Are the Common Mistakes to Avoid?

• Skipping empathy. Teams often jump to solutions, which defeats the purpose.
• Treating stages as a checklist. The process is iterative; expect to loop back.
• Falling in love with a prototype. Prototypes are meant to be tested and changed.
• Ignoring feasibility and viability. A delightful idea still has to work and pay its way.
• Using it as theatre. Sticky notes and workshops are not the method; changing decisions based on what you learn is.

Design thinking has critics, who argue that it can be oversimplified into workshops that produce little real change. Used properly, though, it is a practical habit of understanding people before building for them. For more on how new products and ideas take shape, explore our innovation section.

Featured image: Design Thinking Workshop WMDE Prototypen, by Corinna Schuster (WMDE) / Wikimedia Commons, CC BY-SA 4.0. Cropped, colour-graded and combined with MediaPavilion branding.

Sources

• Stanford d.school — Resources and tools (accessed 26 October 2026).
• Harvard Business Review — Design Thinking, by Tim Brown (June 2008).
• Design Council — The Double Diamond (accessed 26 October 2026).
• IDEO — Design Thinking (accessed 26 October 2026).