Design Thinking: What It Is and How the Five Modes Work

Design thinking is a human-centered, iterative approach to solving problems. It starts by understanding the people affected, then frames the problem, explores possible solutions, makes ideas tangible and learns from testing. Stanford d.school commonly teaches five modes: Empathize, Define, Ideate, Prototype and Test.

The modes are a guide, not a rigid sequence. Teams often move backward and forward as new evidence changes what they understand.

What is design thinking?

Design thinking is a framework for problems where the right answer is not obvious. Rather than beginning with a preferred solution, it begins with people: their needs, experiences, constraints and context.

Different organizations describe the process differently. This guide uses Stanford d.school's five-mode version because it is a clear beginner model. IDEO describes the broader approach as human-centered and iterative, balancing what people need with what is feasible to build and viable to sustain.

Why does it matter?

Design thinking can help a team:

• Understand a problem before committing to a solution.
• Challenge assumptions with customer or user evidence.
• Generate several options instead of defending the first idea.
• Learn through simple prototypes before making a larger investment.

It is most useful when the problem is ambiguous, several solutions seem plausible or the team does not yet understand why people behave as they do.

The five modes

Empathize

Learn from the people affected. Observe what they do, ask about their experience and look for needs or workarounds that internal assumptions may miss.

Define

Turn the research into a focused problem statement. Describe the user, need and context without locking the team into a particular solution.

Ideate

Generate multiple possible answers. Create enough alternatives to move beyond the obvious idea, then choose a few worth exploring.

Prototype

Build the simplest version that can help the team learn. A prototype might be a paper screen, storyboard, service script, mock-up or role-play. It should answer a question, not impress people.

Test

Put the prototype in front of relevant users and observe what happens. Testing may expose a flaw or reveal that the original problem was framed incorrectly.

A simple example

Hypothetical example: A small coworking space notices that new members repeatedly ask staff how to find meeting rooms.

• Empathize: The manager observes first-day check-ins and asks new members where they become confused.
• Define: The team reframes the issue: "New members need a quick way to understand the building layout without interrupting staff."
• Ideate: It considers clearer wall signs, a one-page map, colored room zones and a short orientation route.
• Prototype: The team creates a paper map and temporary signs.
• Test: New members use the temporary system while staff observe where they still hesitate.

The test may show that the map helps but room names remain unclear, sending the team back to Define or Ideate. The process has still created useful evidence. This is an illustrative scenario, not a reported research result.

When should you use it?

Use design thinking when customer needs are unclear, a product or service has recurring friction, a team is considering a new offer or workflow, or several plausible solutions need exploration before a large commitment.

It is less useful when the problem and correct procedure are already known, such as following a mandatory compliance rule.

A Product Roadmap can show which product problems deserve attention over time. Design thinking can help explore one of those problems before the team commits to a particular solution.

How to interpret what you learn

Design thinking does not produce a score. The useful output is better evidence.

After a cycle, ask whether the problem is clearer, whether user evidence changed an assumption, whether the prototype answered a specific question and what should be changed, tested again or stopped.

A negative test is useful if it prevents a weak idea from receiving more time and money. For larger product investments, the Stage-Gate Process can formalize whether the available evidence justifies the next commitment.

Common confusion

Design thinking is not the same as brainstorming. Brainstorming can be one activity inside Ideate, but the framework also includes user understanding, problem framing, prototyping and testing.

Design thinking is also closely related to human-centered design. IDEO describes human-centered design as starting with people, while design thinking is one way of putting that orientation into practice through methods and iteration.

Common mistakes

• Starting with a preferred solution: research becomes a way to justify an idea.
• Skipping real users: internal opinions are not a substitute for observation or feedback.
• Choosing the first idea too early: alternatives are never explored.
• Making prototypes too polished: teams become reluctant to change them.
• Treating the five modes as linear: new evidence may require returning to an earlier mode.

Limitations

Design thinking depends on the quality and diversity of the evidence collected. A small or biased sample can mislead. The framework also does not prove market demand, financial viability, technical feasibility, safety or regulatory compliance on its own.

Quick checklist

Put it to work

Run a 25-minute mini design thinking cycle

Choose one small customer or user friction that your team already has some evidence for. If no evidence exists, do not invent the problem: use the exercise to define what you need to observe or ask.

1. Empathize - 5 minutes. Review two or three real observations, support messages, interview notes or examples of the friction. Write what the person was trying to do, what happened and what remains uncertain.
2. Define - 4 minutes. Write one sentence in this form: [User] needs a way to [need] because [evidence-based reason]. Remove any solution from the statement.
3. Ideate - 5 minutes. Generate at least eight possible responses. Include simple process changes as well as product or service ideas.
4. Prototype - 6 minutes. Choose one idea and make the smallest representation that can answer one question: a sketch, paper screen, short service script, mock email or storyboard.
5. Test plan - 5 minutes. Write who should interact with the prototype, what you will observe and what result would make you change the idea or the problem definition.

Eight ideas is a target for this short exercise, not a universal rule for design thinking. The last activity creates a test plan; it does not mean that testing has already happened.

Finish with two lines:

We currently believe: ________

The next evidence we need is: ________

The exercise is complete when the next learning question is clearer, not when the team has chosen a final solution.

Your next learning question

EmpathizeDefineIdeatePrototypeTest

Small friction / problem

People affected

Evidence typeSelect evidence typeReal evidenceNot yet collectedHypothetical example

Observations / evidence to collect

What remains uncertain?

Real user evidence has not been recorded. Return to Empathize before drawing conclusions.

A test plan is not a completed test. No results or validated solution are inferred.

Key takeaways

• Design thinking is a human-centered, iterative framework for unclear problems, not a fixed five-step recipe.
• A common Stanford d.school version uses five modes: Empathize, Define, Ideate, Prototype and Test.
• Prototypes are learning tools; they should be simple enough to change when evidence contradicts an idea.
• Testing can send a team back to an earlier mode, and a negative result can still be valuable.
• The framework supports problem exploration but does not replace financial, technical, safety, regulatory or market evidence.

Final takeaway

Design thinking helps teams move from assumptions to evidence through five flexible modes: Empathize, Define, Ideate, Prototype and Test.

Its value is not in completing five labels once. It comes from learning what people need, testing ideas early and changing direction when the evidence says the team should.