Frequently Asked Questions About IDEO Design Thinking 7-Phase Process
21 answers covering everything from basics to advanced usage.
// Basics
What does 'human-centered' actually mean in design thinking?
Human-centered means every phase begins and ends with people. The goal is to understand what people really need — not what you assume they need — and to design solutions that serve those needs meaningfully. It's the opposite of technology-first or business-first thinking, where a solution is built and then a use is found for it afterward.
Is design thinking really linear, or can I skip around?
Although the seven phases are taught linearly, design thinking is fluid and iterative in practice. Expect to loop back, repeat phases, and refine ideas as new information emerges. No phase is a one-way door. For example, testing often sends you back to reframe your question or generate fresh ideas. Treating the sequence as rigid is a common pitfall.
What's the difference between an insight and an observation?
An observation is a raw fact — 'people struggle to track their medication.' An insight is a perspective shift that reveals an unmet emotional or functional need — 'people want medication management to feel effortless, not like another task.' Observations describe what happened; insights explain why it matters and point toward a solution direction. Only insights should drive ideation.
Does design thinking work for internal or operational problems, not just products?
Yes. Design thinking applies to any human-centered challenge, including employee onboarding, internal tools, service workflows, and process redesign. The IDEO onboarding example frames 'How might we make new employees feel confident and connected from their first day?' and prototypes a one-page 'first week map.' Anywhere real people experience friction, the seven phases apply.
// How To
How do I frame my first How Might We question if I don't know the problem yet?
Start with 'Why' questions to uncover root challenges, then shift to 'What if' questions to open the solution space, and finally land on a 'How Might We' prompt as your design challenge. If you're still unsure, keep the HMW broad initially — you'll refine it after Gather Inspiration and Synthesize for Action reveal a sharper focus.
How do I run a brainstorm using IDEO's seven rules?
Apply all seven rules: defer judgment, encourage wild ideas, build on others' ideas with 'yes, and,' stay focused on the topic, hold one conversation at a time, go for quantity by setting an ambitious count, and get visual by sketching. Diverge fully first, then switch to convergent thinking to select the most exciting, impactful, or resonant concepts.
How do I know what to prototype first?
Prototype whatever answers your biggest questions, assumptions, risks, or hypotheses. Ask 'What do I most need to learn?' then find the simplest way to test it without building the full solution. A prototype can be a sketch, storyboard, cardboard model, or roleplay. The rule is 'Spend a Little to Learn a Lot' — low cost, low risk, but real enough for meaningful feedback.
How do I use analogous industries to get better inspiration?
Study unrelated fields that solve structurally similar human problems. If you're designing a hospital experience to reduce anxiety, look at how theme parks guide large crowds to feel at ease. For onboarding, study how universities orient incoming students. Analogous research surfaces fresh insights precisely because those domains aren't burdened by your industry's assumptions.
How do I balance a broad versus focused How Might We question?
Make it broad enough to allow creative range but focused enough to inspire real solutions. Too broad ('How might we improve healthcare?') gives no direction; too narrow ('How might we add a chatbot to the check-in page?') pre-decides the solution. Aim for the middle: 'How might we ensure patients feel supported and informed during every step of their care?'
// Troubleshooting
My prototype test just confirmed what I already believed — did I do it wrong?
Possibly. The goal of testing is to learn, not to validate — you want to uncover what does NOT work so you can improve. If tests only confirm your beliefs, your prototype may be too polished, your questions too leading, or your testers too agreeable. Push for honest reactions, evaluate through all four innovation lenses, and expect to iterate multiple times.
My team keeps judging ideas during brainstorming — how do I stop it?
Make 'defer judgment' an explicit, non-negotiable rule before you start, and reframe critical comments in real time from 'but' to 'yes, and.' Set an ambitious quantity target so the focus stays on volume, not quality. Judgment belongs in the convergent phase that comes after divergence — never during it. Remind the group there are no bad ideas at this stage.
I framed my HMW as 'How Should We' — why is that a problem?
'Should' implies there's a single correct answer, which shuts down creative exploration before it starts. 'Might' removes that judgment and permits open, wide-ranging solutions. Rewrite 'How should we onboard employees?' as 'How might we make new employees feel confident and connected from day one?' The shift reopens the solution space and invites diverse ideas.
My stakeholders aren't buying into my solution — what went wrong?
You likely skipped or underinvested in the Share the Story phase. A great idea with no compelling narrative fails to inspire action. Structure your story around three elements: the challenge you set out to solve, the insights you uncovered, and the impact of your solution. Make the human need vivid — often through a single specific person's transformed experience — to earn buy-in.
// Comparisons
How does design thinking compare to Agile or Lean Startup?
Design thinking, Agile, and Lean Startup all embrace iteration and early testing, but they emphasize different things. Design thinking front-loads empathy and problem framing to ensure you build the right thing. Lean Startup focuses on validated learning through build-measure-learn loops around a business model. Agile organizes iterative delivery of software. They complement each other: design thinking often defines what to build before Agile builds it.
How is design thinking different from just doing user research?
User research is one input; design thinking is the full end-to-end process that turns research into tested solutions. Research maps to the Gather Inspiration phase, but design thinking also frames the question, synthesizes insights, ideates, prototypes, tests across four lenses, and tells the story. Research alone tells you what people do; design thinking uses it to actually create and validate something new.
How does 'Spend a Little to Learn a Lot' differ from building an MVP?
Both aim to learn cheaply before full investment, but a design thinking prototype is typically lower fidelity and earlier — a sketch, storyboard, or roleplay meant to test assumptions in hours or days. An MVP is a functional, shippable product used to test market demand. Prototypes answer 'is this idea worth pursuing?'; MVPs answer 'will people actually adopt and pay?'
// Advanced
How do I apply the four innovation lenses to a nonprofit or social project?
Weight Responsibility and Desirability heavily. Desirability asks whether the solution meets real human needs; Responsibility asks whether it could harm people or the planet — critical for social impact. Feasibility checks you can deliver with available skills and resources. Viability may focus on sustainable funding or operational models rather than profit. All four still apply; the emphasis shifts to mission and stakeholder wellbeing.
Can design thinking be done solo, or does it require a team?
It can be done solo but shouldn't be, especially during ideation. The best ideas emerge from diverse perspectives — different backgrounds, experiences, and mindsets. Wild ideas from unexpected contributors often unlock the most innovative solutions. Brainstorming alone is a named pitfall. If you must work solo, deliberately seek outside input during Gather Inspiration, Generate Ideas, and Test to Learn.
How many iteration cycles should I expect before landing on a solution?
There's no fixed number, but expect several. Most great products and services evolve through multiple cycles of prototyping, testing, and refining. Each Test to Learn phase may send you back to reframe, re-empathize, or re-ideate. Plan for iteration rather than a single pass. The number of cycles depends on how much you learn and how far your early assumptions were off.
When should I convert an insight into a new How Might We question?
Convert each strong insight into a refined HMW immediately after synthesis, before you begin ideation. The insight reframes the problem, and the new HMW turns that reframe into an actionable brainstorm prompt. For example, the insight 'patients need to feel accompanied, not just informed' becomes 'How might we make every patient feel accompanied, not alone?' — a sharper challenge to ideate against.
What's the biggest mistake beginners make with design thinking?
Jumping to solutions before properly framing the question. Skipping Phase 1 means you risk solving the wrong problem entirely. Beginners often arrive with a fix in mind and treat the process as justification. The discipline is to resist that — frame the right HMW, build genuine empathy, and let insights, not assumptions, drive what you design.