IDEO Design Thinking 7-Phase Process
Transform any complex human-centered challenge into an innovative, testable solution by moving through IDEO's seven-phase design thinking process — from framing the right question to sharing a compelling story.
// TL;DR
IDEO's Design Thinking 7-Phase Process is a human-centered framework for turning ill-defined problems into innovative, tested solutions. It moves through seven phases: Frame a Question, Gather Inspiration, Synthesize for Action, Generate Ideas, Make Ideas Tangible, Test to Learn, and Share the Story. Use it whenever you face an open-ended challenge affecting real people, where assumptions are untested and creative collaboration is possible. It's especially powerful for product design, service redesign, employee experience, and any problem where understanding what people actually need — not what you assume — is the key to a solution that works.
// When should you use IDEO's design thinking process?
Use this skill whenever you face an ill-defined problem that affects real people and demands creative, human-centered solutions. It is especially powerful when assumptions are untested, the solution space is open, and collaboration is possible.
// What do you need before starting the design thinking process?
- Challenge domainrequired
The broad area or system you are trying to improve (e.g., patient experience, employee onboarding, product usability). - People you are designing forrequired
Who are the end users or people most affected by this problem? Be as specific as possible. - Current pain point or opportunityrequired
What is broken, frustrating, or underserved right now? A rough problem statement or observation is enough to start. - Constraints
Any known resource, time, technology, or ethical boundaries that limit the solution space. - Existing research or data
Any prior interviews, observations, surveys, or data already gathered about the people and problem.
// What core principles guide IDEO design thinking?
Human-Centeredness
Every phase begins and ends with people. The goal is to understand what people really need — not what we assume they need — and to design solutions that serve those needs meaningfully.
Iterative Fluidity
Although the seven phases are taught linearly, in practice design thinking is fluid and iterative. Expect to loop back, repeat phases, and refine ideas as new information emerges. No phase is a one-way door.
Empathy Over Assumption
Empathy is the intuitive ability to identify and understand what other people see, feel, think, and experience. It helps designers move beyond assumptions they didn't even know they had, motivating solutions that better serve real needs.
Diverge Then Converge
Idea generation requires two distinct modes: divergent thinking (going wide, suspending judgment, embracing wild ideas, aiming for quantity) followed by convergent thinking (evaluating and selecting the most exciting, impactful, or resonant concepts).
Spend a Little to Learn a Lot
Prototyping is not about perfection — it is about learning. Build the smallest, lowest-cost version of your idea that is real enough to generate feedback, before investing in full development.
The Four Innovation Lenses
Every solution must be evaluated across four dimensions: Desirability (do people want it?), Feasibility (can you build it?), Viability (is it economically sustainable?), and Responsibility (does it avoid harm to people and the planet?).
Creative Collaboration
The best ideas emerge from diverse perspectives. Bring together people with different backgrounds, experiences, and mindsets — the solution comes from working together, not alone.
// How do you apply IDEO's design thinking process step by step?
- 1
Frame a How Might We Question
Start with 'Why' questions to uncover root challenges. Shift to 'What if' questions to open the solution space. Then land on a 'How Might We' (HMW) question as your design challenge. The word 'How' signals a solution exists; 'Might' removes judgment and permits open exploration; 'We' declares this a collaborative effort. Make sure the HMW is broad enough to allow creative range but focused enough to inspire real solutions. Avoid 'How Should We' — it implies only one correct answer. Example structure: 'How might we ensure [target person] feels [desired emotional or functional outcome] during [specific context]?'
- 2
Gather Inspiration Through Empathy
Immerse yourself in the world of the people you are designing for. Use a mix of methods: interviews, direct observation, surveys, immersive empathy exercises, and analogous industry research (studying how unrelated domains solve similar human problems). Observe behaviors, emotions, and patterns — not just stated words. Remember: people don't always say what they mean, and they don't always do what they say. Look beyond words to emotional cues and behavioral patterns.
- 3
Synthesize for Action Using Insight Statements
Sort your research into themes and patterns — treat it like assembling a puzzle. Identify what surprising challenges keep recurring. Distill findings into Insight Statements: clear, concise summaries that (1) Inform — shed light on what people need and want; (2) Inspire — motivate action by surfacing an emotional need; (3) are Memorable — phrased to stick and be easy to share. An insight is not a raw observation or data point. It is an 'aha moment' — a perspective shift that reveals an unmet need. Bad: 'People find it hard to track their medication.' Good: 'People want medication management to feel effortless, not like another task on their to-do list.' Once you have strong insights, convert each one into a new or refined HMW question to guide ideation.
- 4
Generate Ideas Using the Seven Brainstorm Rules
Enter divergent thinking mode. Apply IDEO's seven brainstorm rules: (1) Defer judgment — no bad ideas at this stage; (2) Encourage wild ideas — bold, edgy, out-there ideas open the door to innovation; (3) Build on the ideas of others — say 'yes, and' instead of 'but'; (4) Stay focused on the topic; (5) One conversation at a time; (6) Go for quantity — set an ambitious idea count and aim to surpass it; (7) Get visual — sketch ideas to engage different parts of the brain. After diverging, switch to convergent thinking: evaluate ideas against what feels most exciting, intriguing, impactful, resonant, or even productively risky. Select the most promising concepts to carry forward.
- 5
Make Ideas Tangible Through Prototyping
Build a rough, low-fidelity representation of your chosen idea. A prototype can be anything: a sketch, storyboard, cardboard model, mockup, or roleplay simulation. Ask yourself: what do you want to learn? Start with your biggest questions, assumptions, risks, hunches, and hypotheses. Find the simplest way to test them without building the full solution. The guiding rule is 'Spend a Little to Learn a Lot' — low cost, low risk, but real enough to generate meaningful feedback. Do not over-complicate it. Build just enough to learn from.
- 6
Test to Learn Across the Four Innovation Lenses
Put your prototype in front of real people and observe how they interact with it. The goal is not just to validate what works — it is to uncover what does not work so you can improve. Evaluate feedback through all four lenses: Desirability ('Does it speak to human needs?'), Feasibility ('Can you actually make it with available skills, technology, and resources?'), Viability ('Is there a sustainable model?'), Responsibility ('Could this cause harm to people or the planet?'). Keep an open mind — the best insights often come from unexpected places. Iteration is key: most great products and services evolve through multiple cycles of prototyping, testing, and refining. After testing, loop back to earlier phases as needed.
- 7
Share the Story to Inspire Action
Craft a human-centered narrative around your solution. Structure the story around three elements: (1) the challenge you set out to solve, (2) the insights you uncovered, and (3) the impact of your solution. Stories connect people to ideas — they help others understand why your solution matters and inspire them to take action. If you want people to care, tell them a story. The story should make the human need vivid and the solution feel both necessary and achievable.
// What does design thinking look like in real projects?
A healthcare organization wants to reduce patient anxiety during hospital stays.
Frame the HMW: 'How might we ensure patients feel supported and informed during every step of their care journey?' Gather inspiration by observing patients navigating waiting rooms, hallways, and patient rooms — noting emotional states, not just logistical friction. Also study analogous industries such as how theme parks guide large crowds to feel at ease. Synthesize an insight like: 'Patients don't just need information — they need to feel like someone is with them.' Convert to a new HMW: 'How might we make every patient feel accompanied, not alone?' Brainstorm widely (wayfinding signage, dedicated liaison roles, app check-ins, ambient environment changes). Prototype a low-fidelity version — e.g., a paper journey map handed to patients on arrival — and test it on a single ward. Evaluate across all four lenses (is it desirable, feasible, viable, responsible?), iterate, then share the story of a specific patient whose experience transformed.
A software company wants to improve new-employee onboarding.
Frame the HMW: 'How might we make new employees feel confident and connected from their very first day?' Gather inspiration through interviews with recent hires and observations of their first two weeks — looking for emotional low points, not just process gaps. Study analogous spaces such as how universities orient incoming students. Synthesize an insight: 'New employees don't just need information — they need to feel like they belong before they can perform.' Generate ideas using the seven brainstorm rules, encouraging wild ideas like 'a buddy-for-life system' or 'a choose-your-own-adventure onboarding path.' Prototype the simplest version — a one-page 'first week map' given on day one — and test with the next incoming cohort. Evaluate desirability, feasibility, viability, and responsibility. Iterate. Share the story of how one employee's experience changed to inspire leadership buy-in.
// What mistakes should you avoid in design thinking?
- Jumping to solutions before properly framing the question — skipping Phase 1 means you may solve the wrong problem entirely.
- Asking 'How Should We' instead of 'How Might We' — 'should' implies a single correct answer and shuts down creative exploration.
- Treating research as data collection rather than empathy-building — ignoring emotional and behavioral signals in favor of only what people say.
- Writing observations instead of true Insight Statements — a raw fact ('people struggle with X') is not an insight. An insight shifts perspective and reveals an unmet emotional or functional need.
- Over-complicating prototypes — building too much before testing wastes resources and delays learning. Build the smallest version that is real enough to generate feedback.
- Treating testing as validation rather than learning — the goal of testing is to discover what does NOT work, not just to confirm what does.
- Treating the seven phases as a strict linear sequence — in practice, you should expect and embrace looping back, repeating phases, and refining ideas as you go.
- Brainstorming alone — creative collaboration and diverse perspectives are essential. Wild ideas from unexpected contributors often unlock the most innovative solutions.
- Judging ideas during divergent brainstorming — deferring judgment is non-negotiable during idea generation. There are no bad ideas at that stage.
- Skipping the storytelling phase — a great idea with no compelling story will fail to inspire action or gain stakeholder support.
// What are the key design thinking terms you should know?
- How Might We (HMW)
- The canonical question format used to frame design challenges. 'How' signals a solution exists; 'Might' removes judgment and permits open exploration; 'We' declares collaborative intent. Used both to open the process and to convert insights into actionable brainstorm prompts.
- Frame a Question
- Phase 1 of the design thinking process. Identifying the right problem to solve by crafting a question — moving from 'Why' to 'What if' to 'How Might We' — that sparks creative solutions rather than locking in premature answers.
- Gather Inspiration
- Phase 2. The empathy-immersion stage where designers observe, interview, and step into the world of the people they are designing for, uncovering what people really need beyond their stated words.
- Synthesize for Action
- Phase 3. The sense-making stage where raw research is organized into themes, patterns, and Insight Statements that shift perspective and identify a strategic focus for ideation.
- Insight Statement
- A clear, concise summary of a key research finding that (1) informs by revealing a real human need, (2) inspires by surfacing the emotion behind the need, and (3) is memorable enough to be easily shared. Distinct from a raw observation — it is an 'aha moment' that reframes how you see the problem.
- Generate Ideas
- Phase 4. The structured brainstorming stage governed by IDEO's seven rules, combining divergent thinking (going wide, suspending judgment, quantity over quality) with subsequent convergent thinking (selecting the most promising concepts).
- Divergent Thinking
- The expansive mode of ideation used during brainstorming — going wide, suspending judgment, embracing wild ideas, and prioritizing quantity of ideas over immediate quality.
- Convergent Thinking
- The evaluative mode used after divergent brainstorming — narrowing down ideas by selecting those that feel most exciting, intriguing, impactful, resonant, or productively risky.
- Wild Ideas
- Deliberately bold, edgy, or 'out there' ideas encouraged during brainstorming. IDEO treats them as essential because the most unconventional ideas often open doors to the most innovative solutions.
- Make Ideas Tangible
- Phase 5. The prototyping stage where ideas are given physical or experiential form — sketches, storyboards, cardboard models, mockups, or roleplay simulations — to enable rapid learning.
- Spend a Little to Learn a Lot
- IDEO's guiding prototyping principle: build the lowest-cost, lowest-risk version of an idea that is real enough to generate meaningful feedback, rather than investing in full development before validating assumptions.
- Test to Learn
- Phase 6. The feedback-and-iteration stage where prototypes are evaluated with real people. The goal is not validation but discovery — uncovering what does not work in order to improve.
- Four Innovation Lenses
- IDEO's framework for evaluating ideas across four dimensions: Desirability (does it meet human needs?), Feasibility (can it be built with available resources?), Viability (is it economically sustainable?), and Responsibility (does it avoid harm to people and the planet?).
- Desirability
- One of the Four Innovation Lenses. Asks: does this solution speak to genuine human needs? What do the people who will use or be impacted by it actually want?
- Feasibility
- One of the Four Innovation Lenses. Asks: can you actually build this given your available skills, technology, resources, and infrastructure?
- Viability
- One of the Four Innovation Lenses. Asks: is there a business or economic model that makes this solution sustainable over time?
- Responsibility
- One of the Four Innovation Lenses. Asks: could this cause harm? What are the responsible choices for both people and the planet?
- Share the Story
- Phase 7. The communication stage where designers craft a human-centered narrative — covering the challenge, the insights uncovered, and the impact of the solution — to inspire others toward action.
- Analogous Industries
- Unrelated fields or domains studied during the Gather Inspiration phase to surface fresh insights by observing how different contexts solve structurally similar human problems.
// FREQUENTLY ASKED QUESTIONS
What is IDEO's design thinking process?
IDEO's design thinking process is a seven-phase, human-centered framework for solving complex problems: Frame a Question, Gather Inspiration, Synthesize for Action, Generate Ideas, Make Ideas Tangible, Test to Learn, and Share the Story. It starts and ends with people, emphasizes empathy over assumption, and treats prototyping and testing as tools for learning rather than validation.
What are the 7 phases of design thinking?
The seven phases are: (1) Frame a Question using a 'How Might We' prompt, (2) Gather Inspiration through empathy and observation, (3) Synthesize for Action into insight statements, (4) Generate Ideas via structured brainstorming, (5) Make Ideas Tangible through low-fidelity prototypes, (6) Test to Learn across four innovation lenses, and (7) Share the Story to inspire action.
How do I write a good How Might We question?
Write a How Might We question that is broad enough for creative range but focused enough to inspire real solutions. Use the structure 'How might we ensure [target person] feels [desired outcome] during [specific context]?' 'How' signals a solution exists, 'Might' removes judgment, and 'We' signals collaboration. Avoid 'How Should We' — 'should' implies only one correct answer and shuts down exploration.
How do I turn research into insight statements?
Sort your research into themes and patterns, then distill findings into insight statements that inform, inspire, and are memorable. An insight is not a raw observation — it's an 'aha moment' that reveals an unmet emotional or functional need. Instead of 'People find it hard to track medication,' write 'People want medication management to feel effortless, not like another to-do.'
How does design thinking compare to traditional problem solving?
Traditional problem solving often jumps straight to solutions based on assumptions, while design thinking insists on framing the right question and building empathy first. It replaces linear planning with iterative loops, prioritizes divergent brainstorming before converging, and evaluates ideas across desirability, feasibility, viability, and responsibility — not just whether they technically work or turn a profit.
When should I use design thinking?
Use design thinking whenever you face an ill-defined problem affecting real people that demands creative, human-centered solutions. It's most powerful when assumptions are untested, the solution space is open, and collaboration is possible. Avoid it for well-defined, purely technical problems with a single known answer — it thrives on ambiguity and human need.
What are the four innovation lenses in design thinking?
The four innovation lenses are Desirability (do people want it?), Feasibility (can you build it with available resources?), Viability (is it economically sustainable?), and Responsibility (does it avoid harm to people and the planet?). IDEO uses them during the Test to Learn phase to evaluate whether a solution is worth carrying forward or refining.
What is the difference between divergent and convergent thinking?
Divergent thinking is the expansive brainstorming mode — going wide, suspending judgment, embracing wild ideas, and prioritizing quantity. Convergent thinking is the evaluative mode that follows — narrowing down by selecting ideas that feel most exciting, impactful, resonant, or productively risky. Design thinking requires you to diverge first, then converge, never mixing the two at once.
What results can I expect from using design thinking?
Expect solutions that genuinely serve human needs, fewer wasted resources from testing early with cheap prototypes, and stronger stakeholder buy-in through compelling storytelling. You'll likely uncover unmet needs you didn't know existed and avoid solving the wrong problem. Results improve across iterations — most great products evolve through multiple cycles of prototyping, testing, and refining.
Why is empathy so important in design thinking?
Empathy matters because people don't always say what they mean or do what they say. It's the ability to understand what others see, feel, think, and experience, helping designers move beyond hidden assumptions. By observing emotional and behavioral cues — not just stated words — you uncover the real needs that drive meaningful, well-fitting solutions.