A Step-by-Step Guide
by Braden Kelley and Chateau G Pato
Design thinking is the framework I get asked about more than any other — and also the one most likely to be applied badly. After two decades of watching organizations adopt it, abandon it, and occasionally get it brilliantly right, I want to walk through what the process actually looks like in practice — not just the five-stage diagram everyone’s seen, but what each stage really demands of a team, and where most implementations quietly fall apart.
Understanding Design Thinking
Design thinking is not just a problem-solving tool; it is a way to infuse innovation into the cultural fabric of an organization. At its core, design thinking is about harnessing empathy to understand user needs deeply, ideating solutions collaboratively, and iterating continuously to refine those solutions.
What is the Design Thinking Process?
The design thinking process is a human-centered, iterative approach to problem-solving that prioritizes deep understanding of user needs before generating and testing solutions. Unlike traditional linear problem-solving methods that move from problem definition directly to solution implementation, design thinking embraces ambiguity, encourages experimentation, and treats early failures as essential learning rather than setbacks to avoid.
Design thinking was formalized as a methodology at Stanford’s d.school and popularized by the design firm IDEO, but its roots go back decades in engineering, architecture, and cognitive science. Today it is applied across industries — from product design and software development to organizational change, healthcare, education, and public policy — wherever complex, human-centered problems need to be solved creatively.
The five stages of the design thinking process are: Empathize, Define, Ideate, Prototype, and Test. These stages are not strictly sequential — design thinking is an iterative process, meaning teams regularly cycle back through earlier stages as new insights emerge. A prototype that fails in testing, for example, typically sends the team back to Define or even Empathize to reexamine their understanding of the problem.
The Five Stages of Design Thinking — In Depth
Stage 1: Empathize
Empathy is the foundation of design thinking and the stage that most distinguishes it from conventional problem-solving approaches. In the Empathize stage, the goal is to develop a deep, genuine understanding of the people you are designing for — their needs, motivations, frustrations, behaviors, and the context in which they live and work.
This understanding is built through direct engagement rather than assumption. Common empathy methods include:
- Observation — watching people in their natural environment to understand how they actually behave, as opposed to how they say they behave
- Interviews — open-ended conversations designed to surface feelings, motivations, and needs that users themselves may not consciously articulate
- Immersion — experiencing the user’s situation firsthand, where possible, to develop visceral understanding of their context
- Journey mapping — documenting the end-to-end experience of a user to identify pain points, friction, and moments of delight
The most common mistake in this stage is shortcutting it. Organizations under pressure to deliver solutions quickly often skip deep empathy work and rely on assumptions, surveys, or existing data instead. The result is solutions that are technically functional but miss the actual human need — or solutions that solve the wrong problem entirely.
What good looks like: A team that has spent significant time with real users, has specific stories and observations (not just data summaries), and can articulate not just what users do but why they do it and how they feel about it.
Stage 2: Define
The Define stage synthesizes everything learned in the Empathize stage into a clear, actionable problem statement — often called a Point of View (POV) or How Might We (HMW) statement. This is the bridge between understanding the user and generating solutions, and it is arguably the most consequential stage in the process.
A well-crafted problem definition is specific enough to provide meaningful direction for ideation but open enough not to prematurely constrain the solution space. Compare:
- Weak definition: “How might we improve our onboarding process?”
- Strong definition: “How might we help new employees who feel overwhelmed by information in their first two weeks develop the confidence and connections they need to contribute meaningfully within 30 days?”
The strong definition is grounded in a specific human insight (feeling overwhelmed, needing confidence and connection), targets a specific outcome (contribute meaningfully within 30 days), and opens multiple solution directions without prescribing any of them.
Common tools used in the Define stage include affinity mapping (organizing observations into themes), persona development (creating composite user archetypes that capture key insights), and empathy maps (visual tools for synthesizing what users say, think, do, and feel).
What good looks like: A problem statement that the whole team finds genuinely energizing and that opens more solution directions than the team initially anticipated.
Stage 3: Ideate
Ideation is the generative stage of design thinking — the phase dedicated to producing a wide range of possible solutions to the defined problem. The guiding principle is quantity before quality: the goal is to generate as many ideas as possible before evaluating any of them.
This runs counter to how most organizations approach problem-solving, where the first plausible solution is often adopted without exploration of alternatives. Design thinking’s insistence on wide ideation before evaluation is grounded in research showing that the best ideas rarely emerge first — they emerge after the obvious solutions have been exhausted and the team is forced to think more creatively.
Effective ideation techniques include:
- Brainstorming — structured group ideation with explicit rules (defer judgment, build on others’ ideas, stay focused, go for quantity)
- Brainwriting — silent individual ideation before group sharing, which reduces groupthink and surfaces more diverse ideas
- Worst possible idea — deliberately generating terrible solutions, then inverting them to find unexpected approaches
- Analogous inspiration — looking at how similar problems are solved in completely different industries or contexts
- SCAMPER — a structured prompt framework (Substitute, Combine, Adapt, Modify, Put to other uses, Eliminate, Reverse) for generating variations on existing ideas
After ideation, ideas are clustered, evaluated against the problem definition and user needs, and narrowed to the most promising candidates for prototyping. Evaluation criteria should include desirability (do users want this?), feasibility (can we build it?), and viability (does it make business sense?).
What good looks like: A team that has generated 50–100+ ideas, including some that seem absurd, before narrowing to 3–5 candidates for prototyping.
Stage 4: Prototype
Prototyping is the stage where ideas become tangible enough to be tested and learned from. The central principle of design thinking prototyping is: build to think, not to present. A prototype is not a polished deliverable — it is a learning tool designed to test a specific assumption or hypothesis as quickly and cheaply as possible.
Prototypes in design thinking can take many forms depending on what you are trying to learn:
- Paper prototypes — hand-drawn sketches of interfaces, products, or experiences that can be tested with users in minutes
- Role-play and bodystorming — physically acting out a service or experience to identify friction points and opportunities
- Storyboards — visual narratives that walk through a user’s experience with a proposed solution
- Wireframes and mockups — low-fidelity digital representations of digital products
- Physical models — rough three-dimensional representations of physical products built from inexpensive materials
- Service blueprints — detailed maps of how a service experience would work, including frontstage user interactions and backstage operational requirements
The critical discipline in this stage is maintaining low fidelity until you have validated the core concept. Organizations that invest in high-fidelity prototypes before testing basic assumptions waste time and money — and create psychological investment in the prototype that makes it harder to abandon when testing reveals fundamental flaws.
What good looks like: Multiple rough prototypes built in hours or days rather than weeks, each designed to test one specific assumption, with teams that are emotionally willing to discard any of them based on what they learn.
Stage 5: Test
Testing brings prototypes back to real users to gather feedback, validate assumptions, and generate new insights. In design thinking, testing is not a validation exercise — it is a learning exercise. The goal is not to prove that your solution works; it is to discover what you got right, what you got wrong, and what you still don’t understand.
Effective testing in design thinking involves:
- Observing how users interact with the prototype rather than just asking them if they like it
- Asking open-ended questions that surface underlying needs and reactions rather than leading questions that confirm existing assumptions
- Paying particular attention to confusion, hesitation, and workarounds — these are often more informative than direct feedback
- Testing with people who represent the actual target user, not just the most convenient available participants
What you learn in testing typically sends you back through the process — refining the prototype, redefining the problem, or in some cases returning to empathy work to investigate unexpected user reactions. This iterative cycling is not a sign that the process is failing; it is the process working exactly as intended.
What good looks like: A team that treats negative feedback as valuable data, that can clearly articulate what they learned from each test, and that is willing to significantly change direction based on what they observe.
Design Thinking vs. Traditional Problem-Solving
|
Design Thinking |
Traditional Problem-Solving |
| Starting point |
Deep understanding of the human need |
Definition of the technical problem |
| Problem definition |
Emerges from empathy research; often reframed |
Defined upfront, rarely revisited |
| Solution generation |
Wide ideation before evaluation |
First plausible solution often adopted |
| Validation approach |
Cheap, fast prototypes tested with real users |
Detailed specification followed by full build |
| Attitude to failure |
Failure is learning; fail early and cheaply |
Failure is to be avoided; risk is minimized upfront |
| Process structure |
Iterative; regularly cycles back through stages |
Linear; stages completed sequentially |
| Success metric |
Solutions that genuinely serve human needs |
Solutions that meet technical specifications |
Design Thinking in Organizational Change and Innovation
Design thinking was developed in the context of product and service design, but its principles transfer directly to organizational change and innovation leadership — which is where it becomes most powerful for readers of this blog.
Applied to change management: The most common failure in organizational change is designing change programs around the organization’s needs rather than the needs of the people experiencing the change. Applying the Empathize stage to change management means spending real time understanding how employees experience the current state — what works, what doesn’t, what they fear losing, and what they hope to gain. This human insight then informs a change approach that is more likely to earn genuine adoption rather than grudging compliance.
Applied to innovation programs: Design thinking provides innovation teams with a structured methodology for moving from insight to validated concept without the enormous upfront investment that traditional innovation processes require. The prototype-test cycle enables organizations to explore many more potential innovations at low cost, failing fast on the ones that don’t work and doubling down on the ones that do.
Applied to leadership: The mindsets that design thinking develops — empathy, comfort with ambiguity, bias toward action, learning orientation — are exactly the mindsets that effective change and innovation leaders need. Organizations that embed design thinking not just as a process but as a way of working develop leaders who are fundamentally better equipped for the complexity of modern organizational challenges.
Braden Kelley’s Human-Centered Change™ methodology draws directly on design thinking principles — particularly the emphasis on deep empathy with the people experiencing change, collaborative visual planning, and iterative refinement. The Change Planning Toolkit™ provides the visual, collaborative tools that bring these principles into practice for change leaders and their teams.
Where I’ve Seen This Break Down in Practice
I’ve facilitated design thinking with organizations ranging from Fortune 500 innovation labs to nonprofit boards trying to redesign a single program, and the failure pattern is remarkably consistent: teams treat Empathize as a formality to get through before the “real work” of Ideate and Prototype begins. I’ve sat in kickoff meetings where a team wanted to skip straight to brainstorming solutions because they were confident they already understood the problem. Every time that happens, the solutions that emerge solve a problem the team assumed existed — not the one that actually does. The teams that get the most value from design thinking are the ones willing to sit with genuine discomfort in Empathize and Define, resisting the pull toward action until the problem itself is truly understood.
Design Thinking in the Age of AI
AI tools now help teams synthesize interview transcripts, generate rapid prototype mockups, and simulate user testing scenarios — and I get asked constantly whether that makes the human-centered core of design thinking less necessary. It doesn’t. AI can accelerate the mechanics of each stage, but it can’t sit in a room with an anxious hospital patient or a frustrated new employee and notice what they’re not saying. The technology changes how fast you move through the five stages. It doesn’t change why Empathize has to come first. For more on this, see my full take on whether AI has changed design thinking.
Case Study 1: Empathy in Healthcare Design
Consider the case of IDEO’s redesign of hospital patient admission processes. The team immersed themselves in the healthcare environment, observing, interviewing, and shadowing patients, nurses, and doctors. They discovered that anxiety stemmed not just from medical concerns but from inadequate communication and disorganized workflows. By empathizing deeply with patients and healthcare workers, IDEO identified nuanced pain points—insights that underpinned innovative solutions.
Case Study 2: Redesigning the Banking Experience
Another illuminating example is the redesign of the financial services experience by Bank of America. To capture the essence of user needs, their design team spent extensive time interviewing and observing customers and bank employees.
After empathizing and defining the core problems—such as the stress surrounding financial management and the intimidating nature of banking for new customers—they ideated solutions focusing on ease and trust.
Prototypes included simplified online interfaces, interactive financial planning tools, and revamped branch layouts to promote a welcoming atmosphere. Testing these prototypes with users led to iterative enhancements, eventually culminating in features like the “Keep the Change” program, which rounds up debit-card purchases to the nearest dollar and deposits the difference into a savings account—making saving effortless and habitual.
Conclusion
Design thinking is more than a methodological approach; it is a philosophy that places human needs at the epicenter of problem-solving. By embodying empathy, framing actionable challenges, embracing diverse ideas, and iterating through prototypes and tests, organizations can unlock unprecedented creativity and innovation.
As witnessed through IDEO’s healthcare intervention and Bank of America’s user-centric banking overhaul, design thinking can drive meaningful change across industries. It is a beacon guiding us toward innovations that resonate profoundly with end-users, creating solutions that are not only successful but also deeply impactful.
Let us continue to champion design thinking, fostering a world where creative solutions and human-centered innovations usher in a future replete with possibilities.
Frequently Asked Questions About the Design Thinking Process
What are the 5 stages of the design thinking process?
The five stages of the design thinking process are: Empathize (developing deep understanding of the people you are designing for), Define (synthesizing empathy insights into a clear problem statement), Ideate (generating a wide range of possible solutions), Prototype (building rough, testable representations of the most promising solutions), and Test (gathering feedback from real users to learn and refine). These stages are iterative rather than strictly sequential — teams regularly cycle back through earlier stages as new insights emerge from testing and prototyping.
What is design thinking used for?
Design thinking is used to solve complex, human-centered problems across virtually any domain. It originated in product and service design but is now applied to software development, organizational change, healthcare system design, education, public policy, social innovation, and business model development. The methodology is most valuable when the problem is not fully understood at the outset, when the solution needs to work for real humans rather than just meeting technical specifications, and when early-stage experimentation is preferable to large upfront investments in unvalidated solutions.
What is the difference between design thinking and agile?
Design thinking and agile are complementary but distinct methodologies. Design thinking focuses on understanding the problem and generating validated concepts — it is most powerful in the early, exploratory phases of innovation when the right solution is not yet known. Agile focuses on building and delivering working solutions iteratively — it is most powerful once the direction is established and the challenge is execution. Many organizations combine both: using design thinking to discover and define the right problem and solution concept, then using agile to build and deliver it efficiently.
Is design thinking only for designers?
No — design thinking is for anyone who needs to solve complex problems that involve human needs. The methodology is widely taught in business schools (Stanford, Harvard, MIT), used by management consultants, applied by change leaders and HR professionals, and practiced in government and nonprofit organizations. The “design” in design thinking refers to a way of thinking and working — human-centered, iterative, prototype-driven — not to visual or aesthetic design skills. Leaders, managers, strategists, and practitioners in any field can learn and apply design thinking effectively.
How long does the design thinking process take?
The design thinking process can be compressed into a single day for simple challenges or run over months for complex ones. Design sprints — a popular format developed at Google Ventures — complete the full five-stage process in five days. For organizational change or complex innovation challenges, deep empathy research alone may take several weeks, with the full process running three to six months before a validated concept is ready for scaling. The key principle is that speed in prototyping and testing saves time overall — organizations that build cheap prototypes and test quickly consistently outperform those that spend months specifying solutions before any user validation.
What are the most common mistakes in applying design thinking?
The most common mistakes are: shortcutting the Empathize stage by relying on assumptions or surveys instead of direct user engagement; treating the process as linear and not returning to earlier stages when new insights emerge; building high-fidelity prototypes before validating the core concept; testing with internal stakeholders instead of real users; and treating design thinking as a one-time workshop rather than an ongoing practice. The organizations that get the most value from design thinking are those that embed it as a regular way of working — not a special event — and that build the empathy, curiosity, and comfort with ambiguity that the methodology requires across their leadership teams.
SPECIAL BONUS: The very best change planners use a visual, collaborative approach to create their deliverables. A methodology and tools like those in Change Planning Toolkit™ can empower anyone to become great change planners themselves.
Image credit: Pixabay
Sign up here to get Human-Centered Change & Innovation Weekly delivered to your inbox every week.
