What is design thinking?

Design thinking is a human-centered approach to problem-solving that prioritizes understanding the people who experience a problem before attempting to solve it. Rather than jumping straight to solutions, design thinking asks teams to slow down, build genuine empathy with users, and reframe problems in ways that lead to more effective, meaningful outcomes.

The approach emerged from design practice but has been widely adopted across product development, business strategy, healthcare, education, and public policy. Its appeal lies in its structured flexibility—it offers a clear process without being prescriptive about the solutions teams reach.

The five stages of design thinking

Design thinking is commonly described as a five-stage process. These stages are iterative rather than sequential, and teams frequently revisit earlier stages as new information surfaces.

1. Empathize

The first stage involves building a deep understanding of the people you are designing for. This means conducting user interviews, observing behavior in context, and setting aside your own assumptions about what users need. The goal is not to collect data points but to develop genuine insight into the motivations, frustrations, and goals of real people.

Methods commonly used in this stage include ethnographic research, contextual inquiry, diary studies, and user interviews. The richer and more specific your understanding of users at this stage, the more grounded your eventual solutions will be.

2. Define

Once you have gathered empathy research, the define stage asks you to synthesize what you learned into a clear problem statement. This is sometimes called a point of view statement or problem frame. A well-crafted problem statement names a specific user, their need, and the insight that makes that need interesting or important.

Crucially, the define stage is about identifying the right problem—not the most obvious one. Teams often discover that the problem users actually experience is different from what stakeholders assumed at the outset.

3. Ideate

With a clear problem statement in hand, teams move into ideation. This stage is about generating a wide range of potential solutions without judging them prematurely. Techniques like brainstorming, worst possible idea, mind mapping, and SCAMPER help teams think beyond conventional responses.

The emphasis in ideation is on quantity and variety. Even ideas that seem impractical can spark useful directions, and premature evaluation tends to narrow thinking too quickly.

4. Prototype

Prototyping means making ideas tangible so they can be tested and learned from. Prototypes do not need to be polished or functional—their purpose is to create something concrete enough that real users can react to it. Paper sketches, clickable wireframes, storyboards, and physical mockups all count.

The guiding principle is to build cheaply and quickly so that failures cost little. A prototype that reveals a flaw in your thinking is a success, not a failure.

5. Test

Testing involves putting your prototypes in front of real users and observing what happens. The goal is not validation but learning. Teams watch how users interact with prototypes, listen to their questions and confusion, and use what they observe to refine their understanding of both the problem and the solution.

Insights from testing often send teams back to earlier stages—redefining the problem, generating new ideas, or building a different prototype. This iteration is what makes the process effective.

How design thinking differs from traditional approaches

Conventional problem-solving tends to start with a problem that has already been defined by stakeholders or subject matter experts. Solutions are evaluated primarily against technical feasibility and business requirements.

Design thinking deliberately inverts this. It starts with the assumption that the right problem has not yet been identified, and that users hold the key to understanding what it actually is. This shift in starting point changes everything—it means that requirements emerge from research rather than being handed down, and that feasibility is considered after desirability.

This makes design thinking especially useful for ambiguous problems, where the path forward is unclear and standard playbooks do not apply.

When to use design thinking

Design thinking is most valuable when a team is working on a problem that involves human behavior, when existing solutions are not working well, or when the problem itself is poorly understood. It is less suited to situations where the problem is already well-defined and the solution space is known.

Common applications include redesigning product onboarding flows, understanding why users churn, developing new product features, improving internal workflows, and exploring unmet needs in a market.

The role of research in design thinking

User research is not a preliminary step in design thinking—it is the foundation the entire process rests on. Without genuine insight into user needs and behavior, the define stage produces assumptions dressed up as problem statements, and ideation generates solutions that miss the mark.

This is why teams that practice design thinking invest seriously in qualitative research methods: interviews, observation, and synthesis techniques like affinity mapping and journey mapping. The quality of the research shapes the quality of everything that follows.