5 Stages In The Design Thinking Process
A comprehensive guide to understanding and applying the user-centered innovation framework that transforms how teams solve complex problems
What Is Design Thinking
Design thinking is a methodology that provides a solution-based approach to solving complex problems. Originally developed at the Stanford d.school and popularized by IDEO, this human-centered approach has become fundamental to innovation across industries from technology to healthcare, education to government services. Unlike traditional problem-solving methods that jump directly to solutions, design thinking begins with deeply understanding the people you're designing for and ends with innovative solutions tailored to their needs, behaviors, and contexts.
The power of design thinking lies in its ability to help teams break free from conventional assumptions and explore new possibilities. By following a structured yet flexible process, organizations can create products, services, and experiences that genuinely resonate with users while addressing real business challenges. Whether you're developing a new digital product, improving a service experience, or tackling systemic social challenges, design thinking offers a proven methodology for generating solutions that are both desirable from a user perspective and viable from a business perspective.
One of the most important characteristics of design thinking is its iterative nature. While the five stages are often presented sequentially, successful design thinking projects frequently involve returning to earlier stages as new insights emerge. This flexibility is not a weakness but a strength, ensuring that the final solution is informed by continuous learning and refinement. For a deeper exploration of how these principles translate into digital interfaces, see our guide on UX design fundamentals.
User-Centered
Places genuine human needs at the center of every decision, ensuring solutions resonate with the people they're designed for rather than what designers assume they want.
Iterative Approach
Embraces continuous testing and refinement rather than seeking perfect solutions on the first attempt, allowing teams to learn and improve with each iteration.
Encourages Innovation
Creates psychological safety for exploring unconventional ideas without fear of immediate rejection, unlocking creative potential that might otherwise remain hidden.
Cross-Functional Collaboration
Brings diverse perspectives together, breaking down silos between departments and disciplines to generate richer, more innovative solutions.
Stage 1: Empathize
Understanding your users on a deeper level
The empathize stage is the foundation of the entire design thinking process. Before any solution can be developed, designers must develop a genuine understanding of the people they are designing for. This goes far beyond basic market research or demographic analysis--empathy requires entering into the user's world, observing their behaviors, understanding their emotions, and appreciating the context in which they live and work.
Empathy allows designers to set aside their own assumptions about the world and gain real insight into users and their needs. This is crucial because designers, like all humans, carry unconscious biases that can lead them to create solutions based on what they think users want rather than what users actually need. By systematically developing empathy, designers can ensure that their solutions are grounded in genuine user understanding rather than designer intuition.
The empathize stage typically involves multiple research methods conducted in the user's environment. These might include direct observation, where designers watch users interact with products or services in their natural context; ethnographic interviews, where designers engage users in conversations about their experiences, motivations, and challenges; and immersion, where designers temporarily adopt the user's perspective to gain first-hand experience of their challenges.
Stage 2: Define
Framing the right problem to solve
The define stage is where the insights gathered during empathize are synthesized into a clear and actionable problem statement. This statement, often called a Point of View (POV) in design thinking terminology, captures the essence of the user need that the design will address. A well-crafted problem statement is both human-centered--focused on user needs rather than business requirements--and broad enough to allow for creative freedom in generating solutions.
Defining the problem correctly is crucial because it sets the direction for the entire ideation phase. If the problem statement is too narrow, the team may miss innovative solutions that fall outside its boundaries. If it is too broad, the team may struggle to generate focused ideas that can be effectively prototyped and tested. The goal is to find a sweet spot that captures the essential challenge while leaving room for creative exploration.
A common mistake in this stage is defining the problem from the organization's perspective rather than the user's perspective. For example, a problem statement like "We need to increase our market share among young adults" is not a good design thinking problem statement because it focuses on business goals rather than user needs. A better formulation would be "Young adults need a way to accomplish a specific goal because of their current situation or frustration."
Once the problem statement is established, it is often helpful to convert it into "How Might We" (HMW) questions. This format acknowledges that solutions are not immediately obvious while also framing the problem as an opportunity for creative solutions.
Stage 3: Ideate
Generating a breadth of creative solutions
The ideation stage is where creativity takes center stage. Having developed a deep understanding of user needs and clearly defined the problem to solve, the team now generates as many ideas as possible for potential solutions. The goal is quantity over quality at this stage--the more ideas generated, the greater the chance of discovering innovative solutions that would never emerge from a more constrained brainstorming process.
Ideation is fundamentally about challenging assumptions. Every design problem comes with a set of implicit assumptions--about what users want, what is technically possible, what the market will accept--and ideation is the stage where these assumptions are questioned and potentially broken. By deliberately encouraging wild and unconventional ideas, teams can push beyond their habitual ways of thinking and discover breakthrough solutions.
There are many different ideation techniques that can be used depending on the team's preferences and the nature of the problem. Brainstorming is the most well-known, but other techniques like brainwriting (where participants write ideas silently before sharing), the worst possible idea technique (generating intentionally bad ideas to spark creative alternatives), SCAMPER (a checklist-based method for generating variations), and mind mapping can all be valuable depending on the context.
A key principle of ideation is deferring judgment. This means that during the idea generation phase, all ideas are welcomed without criticism, even those that seem impractical or unconventional. Judgment comes later, during the prototyping and testing stages. By creating a safe space where team members feel free to share even the most unusual ideas, facilitators can unlock creative potential that might otherwise remain hidden.
Brainstorming
Traditional group ideation with ground rules: defer judgment, encourage wild ideas, build on others' contributions, stay focused on the topic, and have one conversation at a time.
Brainwriting
Silent ideation where participants write ideas individually before sharing, preventing groupthink and giving introverted team members equal voice in the process.
SCAMPER
Prompt-based technique asking: Substitute, Combine, Adapt, Modify, Put to another use, Eliminate, Reverse. A systematic way to reimagine existing solutions.
Worst Possible Idea
Deliberately generating terrible ideas removes fear of judgment and often leads to unexpectedly good solutions through the contrast effect.
Stage 4: Prototype
Turning ideas into tangible representations
Prototyping is where ideas begin to take physical or digital form. The purpose of a prototype is not to create a finished product but to make an idea tangible enough that it can be tested and refined. Prototypes can range from simple paper sketches to interactive digital mockups, from physical models to service simulations--the appropriate level of fidelity depends on the nature of the idea and what needs to be learned from testing it.
Prototypes should be created quickly and inexpensively. The goal is to learn as much as possible about whether an idea works while investing as little time and resources as possible. This approach allows teams to test multiple ideas in parallel and quickly eliminate those that don't work, focusing refinement effort on the most promising concepts.
This experimental approach helps designers identify the best possible solution for each of the problems identified during the first three stages. The solutions are implemented within the prototypes, and one by one, they are investigated and then accepted, improved, or rejected based on the users' experiences. By the end of the prototype stage, the design team will have a better understanding of the product's limitations and the problems it faces, as well as a clearer view of how real users would behave, think, and feel when they interact with the end product.
The appropriate level of prototype fidelity depends on what you need to learn. Low-fidelity prototypes like paper sketches or wireframes are good for testing basic concepts and user flows without investing significant effort. Higher-fidelity prototypes that more closely resemble the final product are appropriate when you need to test specific interactions, visual design elements, or technical feasibility. For digital products, understanding responsive design principles is essential when moving from prototype to production.
| Fidelity Level | Examples | Best For |
|---|---|---|
| Low | Paper sketches, storyboards, card sorting, role-playing | Early exploration, testing concepts, getting stakeholder alignment |
| Medium | Wireframes, mockups, HTML prototypes, 3D prints | Refining interactions, testing usability, visual design feedback |
| High | Interactive prototypes, coded MVPs, production-like mockups | User testing with real tasks, stakeholder demos, late-stage validation |
Stage 5: Test
Gathering feedback to refine solutions
Testing is where prototypes meet real users. This stage is critical because it provides direct feedback on whether the solutions developed actually work for the people they are intended to serve. Testing should never be skipped or rushed--even the most promising prototype might reveal significant problems when exposed to real users.
Designers rigorously test the complete product using the best solutions identified during the prototype stage. This is the final stage of the five-stage model; however, in an iterative process such as design thinking, the results generated are often used to redefine one or more further problems. This increased level of understanding may help you investigate the conditions of use and how people think, behave, and feel toward the product, and even lead you to loop back to a previous stage in the design thinking process.
Testing should be conducted in realistic conditions whenever possible. This means observing users as they interact with the prototype in contexts that resemble how they would actually use the final product. If testing is being conducted in a workshop setting, role-play can be an effective technique for simulating realistic use contexts.
The feedback gathered during testing should be used to refine the solution and may even uncover insights that lead back to previous stages. This iterative loop is a fundamental characteristic of design thinking--it is not a failure to return to empathize or define but rather an indication that the process is working as intended, surfacing new insights that improve the final outcome.
The Non-Linear Nature of Design Thinking
Why the process isn't always sequential
While the five stages are often presented as a linear sequence, successful design thinking is fundamentally non-linear and iterative. In practice, different stages may be conducted concurrently, designers may move back and forth between stages, and insights from testing may trigger new rounds of ideation or even a return to empathizing with users.
This flexibility is one of the key strengths of the design thinking approach. By not being bound to a rigid sequence, teams can follow the logic of their discoveries rather than adhering to an arbitrary process. An insight about user behavior might spark a new round of ideation; a prototyping challenge might reveal that the problem needs to be redefined; testing feedback might suggest a return to user research to better understand an unexpected behavior.
The design thinking process should not be seen as a concrete and inflexible approach to design. The component stages identified should serve as a guide to the activities you carry out rather than a strict sequence to follow. The stages might be switched, conducted simultaneously, or repeated several times to gain the most informative insights about your users and develop the most innovative solutions.
Knowledge acquired in the latter stages of the process can inform repeats of earlier stages. Information is continually used to inform the understanding of the problem and solution spaces and to redefine the problem itself. This creates a perpetual loop in which designers continue to gain new insights, develop new ways of viewing the product or service and its possible uses, and develop a far more profound understanding of their real users and the problems they face.
The iterative design thinking model shows how stages overlap and connect, emphasizing that insights from any stage can inform any other
Common Design Thinking Challenges
Navigating obstacles teams encounter
Even well-intentioned teams face challenges with design thinking. One of the most common misconceptions is that it is a linear process--remember, it is not unusual or wrong to circle back to previous steps. Time constraints pressure teams to skip empathize and ideate, jumping straight to solutions. Group dynamics can suppress diverse perspectives if senior leaders dominate discussions. Confirmation bias leads teams to seek evidence for their preferred solution rather than exploring alternatives.
Avoid making assumptions and stay true to the user insights you have gathered. It can be tempting to let your own preferences or organizational priorities influence your understanding of user needs, but this undermines the entire methodology. If you find yourself making assumptions, challenge yourself to go back to the research and verify your conclusions with additional user engagement.
Finally, do not be pressured to race through the steps. The goal of design thinking is not speed--it is finding the right solution. Taking the time to genuinely understand users, carefully define problems, generate diverse ideas, thoroughly prototype, and rigorously test will ultimately lead to better outcomes than rushing through the process to reach a quick conclusion. This methodical approach directly supports conversion rate optimization by ensuring your solutions truly address user needs.
Time Pressure
Teams rush through early stages when deadlines loom. Mitigation: Build dedicated research and ideation time into project timelines from the start.
Groupthink
Vocal individuals dominate discussions. Mitigation: Use anonymous idea generation, round-robin sharing, and designated facilitation to ensure all voices are heard.
Confirmation Bias
Teams seek evidence for preferred solutions. Mitigation: Assign a devil's advocate and require teams to articulate evidence against ideas before moving forward.
Lack of Safety
Fear of judgment prevents idea sharing. Mitigation: Establish explicit ground rules at the start of sessions and model vulnerability as a leader.
Frequently Asked Questions
Sources
- Interaction Design Foundation - The 5 Stages in the Design Thinking Process - Comprehensive guide from the world's largest design community
- Miro - What are the Design Thinking Steps? - Practical guide for implementing design thinking in workshops
- Stanford d.school - An Introduction to Design Thinking Process Guide - Original academic source from Stanford University