Frequently Asked Questions About IDEO Design Thinking 7-Phase Process
20 answers covering everything from basics to advanced usage.
// Basics
What's the difference between an observation and an insight in design thinking?
An observation is a raw fact — 'People struggle to find the checkout button.' An insight reframes that observation to reveal an unmet need — 'People want the purchase journey to feel like a natural next step, not a hunt.' Insights shift perspective, surface the emotion behind the behavior, and are memorable enough to rally a team. If your statement doesn't produce an 'aha moment' or can't be converted into a How Might We question, it's still an observation, not an insight.
How long does the full IDEO design thinking process take?
It depends on the complexity of the challenge. A focused sprint can compress all seven phases into 3-5 days for a well-scoped problem. More complex organizational or product challenges may take 6-12 weeks with multiple iteration cycles. The process is not strictly linear — expect to loop back through phases. The key is not to rush empathy and synthesis (phases 2-3), as shortcutting these leads to solving the wrong problem. Prototyping and testing should be fast and iterative.
What's the difference between divergent and convergent thinking?
Divergent thinking is the expansive mode — go wide, suspend judgment, embrace wild ideas, prioritize quantity over quality. It's used during brainstorming to generate the maximum range of possibilities. Convergent thinking is the evaluative mode — narrow down ideas by selecting those that are most exciting, impactful, resonant, or productively risky. IDEO insists these modes must be separated. Judging ideas during divergent thinking kills creativity. Converge only after divergence is complete.
What's the role of 'Responsibility' as an innovation lens?
Responsibility is IDEO's fourth innovation lens, asking: could this solution cause harm to people or the planet? It covers ethical implications, unintended consequences, environmental impact, accessibility, bias, and equity. Unlike Desirability, Feasibility, and Viability, Responsibility acts as a guardrail — a solution that scores well on the other three but fails on Responsibility should not move forward. Examples include checking whether an AI feature introduces bias or whether a product creates unnecessary waste.
// How To
How many ideas should we aim for in a brainstorming session?
IDEO recommends setting an ambitious quantity target and trying to surpass it. For a 30-minute session with 5-8 people, aim for 50-100 ideas. Quantity drives quality — the best ideas often emerge after the obvious ones are exhausted. Use IDEO's rule 'go for quantity' to push past comfort zones. Don't filter during divergent thinking. The convergent evaluation phase comes after, where you select the most exciting, impactful, and productively risky concepts.
How do you know when your How Might We question is too broad or too narrow?
A good HMW question is broad enough to allow creative range but focused enough to inspire actionable solutions. Too broad: 'How might we fix healthcare?' — this is unactionable. Too narrow: 'How might we add a chatbot to our patient portal?' — this presumes a solution. Right balance: 'How might we ensure patients feel supported and informed during every step of their care journey?' Test your HMW by brainstorming for 5 minutes — if ideas flow freely but stay relevant, the scope is right.
How do you prototype a service instead of a physical product?
Service prototyping uses experience simulations rather than physical models. Common methods include roleplay (acting out the service interaction), storyboards (illustrating the user journey step by step), paper journey maps (handed to test participants), or wizard-of-oz prototypes (where a human secretly performs the service behind the scenes to simulate automation). The principle is the same: build the smallest version that's real enough to generate feedback. For services, focus on prototyping the key moments of interaction, not the entire end-to-end experience.
How do you evaluate which ideas to take forward after brainstorming?
During convergent thinking, evaluate ideas against criteria like excitement ('Does this make us want to build it?'), impact ('Could this meaningfully change the experience?'), resonance ('Does it connect to a real insight?'), and productive risk ('Is this bold enough to be worth testing?'). Dot voting works well for quick prioritization in groups. Then pressure-test top ideas against the four innovation lenses. Avoid defaulting to the safest or most familiar idea — that usually means you're not pushing far enough.
How do you teach design thinking to a team that's never used it?
Start with a hands-on workshop, not a lecture. Choose a relatable challenge (like improving the team's own meeting experience), then walk through all seven phases in a compressed 2-4 hour sprint. Experiencing the process is more persuasive than explaining it. Emphasize the brainstorm rules physically — post them on the wall. Let people feel the difference between divergent and convergent modes. After the workshop, apply the process to a real project within two weeks while the experience is fresh.
How do you write a compelling story in Phase 7 of design thinking?
Structure your story around three elements: the challenge (what problem did you set out to solve and why does it matter?), the insights (what surprising truths did you uncover about the people you're designing for?), and the impact (how does your solution change someone's experience?). Make it personal — anchor the narrative in one specific person's journey. Use emotional language that makes the need vivid. End with a clear call to action. If stakeholders feel the human need, they'll support the solution.
// Troubleshooting
Can I use design thinking as a solo practitioner without a team?
You can apply the phases individually, but you'll miss a core advantage: diverse perspectives during brainstorming. IDEO's principle of creative collaboration means wild ideas from unexpected contributors often unlock the most innovative solutions. If working solo, compensate by interviewing diverse stakeholders, sharing prototypes widely for feedback, and inviting others into brainstorm sessions even informally. The empathy and prototyping phases work well solo; ideation benefits most from collaboration.
What if my stakeholders don't believe in design thinking?
Start small with a low-stakes pilot rather than proposing a full transformation. Run a condensed design thinking sprint on one well-defined problem and document the results with the storytelling phase. Skeptical stakeholders respond to demonstrated outcomes, not methodology pitches. Show them a specific user whose experience changed. Use the four innovation lenses to speak their language — Viability addresses business concerns, Feasibility addresses technical concerns, and Responsibility addresses risk.
What happens if testing reveals my prototype completely fails?
That's a success, not a failure. The testing phase exists to discover what doesn't work so you can improve. A failed prototype means you learned something important before investing heavily. Loop back to synthesis or ideation — your test likely revealed a new insight or an unexamined assumption. Ask what specifically failed: Was the concept wrong (loop to ideation), or was the underlying need misunderstood (loop to empathy)? IDEO's mantra 'spend a little to learn a lot' assumes some prototypes will fail.
// Comparisons
How is design thinking different from lean startup methodology?
Design thinking focuses on deeply understanding human needs before generating solutions, using empathy, insight synthesis, and structured brainstorming. Lean startup focuses on building minimum viable products quickly and measuring market response through build-measure-learn cycles. Design thinking goes deeper on the 'why' before building; lean startup emphasizes speed to market. They complement each other — use design thinking to discover the right problem and solution direction, then lean startup to scale and iterate on the business model.
What makes IDEO's design thinking different from generic problem-solving frameworks?
Three key differentiators: First, empathy is foundational — you immerse yourself in users' lives before defining the problem, rather than starting with data analysis. Second, the diverge-then-converge structure with explicit brainstorm rules prevents premature convergence, which is the most common failure in generic brainstorming. Third, the four innovation lenses (Desirability, Feasibility, Viability, Responsibility) evaluate solutions holistically rather than defaulting to business metrics alone. Generic frameworks often skip empathy, lack structured ideation rules, and evaluate primarily on ROI.
How does IDEO's process compare to Double Diamond design?
Both share the diverge-then-converge structure, but at different scales. The Double Diamond has two phases — Discover/Define and Develop/Deliver — each with a divergent and convergent mode. IDEO's 7-phase process is more granular: it breaks the first diamond into Frame, Gather Inspiration, and Synthesize, and the second into Generate Ideas, Prototype, and Test, then adds Storytelling as a seventh phase. IDEO also explicitly applies the four innovation lenses during testing, while Double Diamond is more framework-agnostic on evaluation criteria.
// Advanced
What are analogous industries and how do you use them in design thinking?
Analogous industries are unrelated fields studied during the Gather Inspiration phase to surface fresh perspectives on structurally similar human problems. For example, a hospital studying patient anxiety might examine how theme parks manage crowd flow to keep guests calm, or how airlines handle boarding to reduce stress. The technique breaks teams out of industry tunnel vision. Look for contexts where the emotional dynamic is similar — managing uncertainty, building trust, guiding transitions — even if the surface domain is completely different.
How do you handle conflicting insights during the synthesis phase?
Conflicting insights are normal and valuable — they often reveal different user segments or context-dependent needs. Don't resolve them by choosing one over the other. Instead, convert each into separate How Might We questions and explore both directions during ideation. Sometimes the conflict itself becomes the most powerful insight: 'Users simultaneously want simplicity and control' might lead to adaptive interfaces. Group your research by user type if conflicts map to distinct personas.
Can design thinking work for technical or engineering problems?
Yes, but the framing matters. Design thinking excels when the problem involves human interaction, experience, or behavior — even in technical contexts. For a backend infrastructure problem with no human-facing component, traditional engineering methods may be more efficient. But for technical challenges like developer tools, API design, or internal tooling, design thinking reveals usability needs that purely technical analysis misses. Frame the HMW around the human using the technical system, not the system itself.
Is design thinking only for innovation teams or can operations teams use it too?
Operations teams benefit significantly from design thinking, especially for process improvement, internal service design, and change management. The empathy phase helps operations leaders understand frontline workers' real pain points — not just reported metrics. For example, an operations team redesigning a warehouse workflow could observe workers, synthesize insights about cognitive load and fatigue patterns, and prototype new process flows. The framework works wherever people interact with a system that can be redesigned.