Design Thinking
A practical guide to the Design Thinking methodology for product designers, UX researchers, UI designers, service designers, product managers, entrepreneurs, and business leaders. This skill helps you move through human-centered design work with rigor — from understanding real people to shipping solutions that reach them.
What This Skill Covers
- Running or planning any phase of a Design Thinking process
- Generating and evaluating design artifacts (empathy maps, HMW questions, POV statements, prototype briefs, usability test plans, service blueprints)
- Adapting the methodology to your role and context (new product, existing product, service, startup, innovation workshop)
- Facilitating cross-functional collaboration with shared language
- Avoiding the methodology errors that produce poor — or irrelevant — outcomes
How to Use This Skill
Tell Claude what phase you are in and what you need. Examples:
- "I need to plan empathy interviews for a mobile banking redesign"
- "Here are my research findings — help me synthesize into a problem statement"
- "We're about to ideate — what methods work best for a 90-minute remote session?"
- "I'm a founder — how do I validate my idea before I build anything?"
- "We're running a strategy workshop on service redesign — where do we start?"
If you are unsure which phase you are in, describe your situation and Claude will orient you.
The Design Thinking Framework
Design Thinking is a non-linear, human-centered approach to problem-solving. It is a proven framework for keeping human needs at the center of every decision — from the first user conversation to the final shipped solution. It is not a checklist — it is a flexible scaffold for keeping teams oriented around real human needs at every stage of the work.
The Six Phases
| Phase | Core Question | Primary Output |
|---|---|---|
| Empathize | Who are these people and what do they actually experience? | Research insights, empathy maps |
| Define | What is the real problem worth solving? | POV statement, HMW questions |
| Ideate | What are all possible ways to solve this? | Solution concepts, decision rationale |
| Prototype | What is the cheapest version we can learn from? | Prototype artifact (any fidelity) |
| Test | Does this work for real people? | Validated insights, iteration priorities |
| Implement | How do we get this to users? | Shipped solution, adoption plan |
The Three Lenses
Every design decision should balance:
- Desirability — Do people want this? Does it fit their lives and actual needs?
- Feasibility — Can it be built? What does technology currently allow?
- Viability — Is it sustainable? Does it make economic and organizational sense?
❌ Designing only for desirability without feasibility produces beautiful concepts that cannot be built. ❌ Designing only for viability produces business-first solutions users do not want. ✅ Strong design lives at the intersection of all three lenses.
Designer's Mindset
These are not soft aspirations — they are active operating principles:
- Empathy: Suspend your own perspective. Your experience of the problem is not the user's.
- Beginner's mind: Approach each project without assuming you already know the answer. Curiosity before conclusions.
- Optimism: Believe a better solution exists, even when none is obvious yet.
- Comfort with ambiguity: Stay in the problem longer than feels comfortable. Rushing Define leads to solving the wrong thing.
- Bias toward action: Prototypes beat arguments. Build to learn, not to present.
- Willingness to fail early: A failed paper prototype costs an afternoon. A failed shipped product costs far more.
The Non-Linear Process
The phases are not a waterfall. Expect and plan for:
- Looping from Test back to Define when your problem statement was wrong
- Looping from Prototype back to Ideate when a concept is fundamentally flawed
- Running Empathize activities during Test when new behaviors surface
- Returning to Empathize after Define when insights reveal gaps in your research
❌ Treating Design Thinking as a checklist to complete exactly once ✅ Treating it as a shared language that lets the team know where they are at any moment
Stage 1: Empathize
Purpose
Deeply understand the people you are designing for — their behaviors, motivations, pain points, context, and emotional experience. This is not market research about segments. It is observation and conversation with individual humans in real situations.
When You Are Here
- Starting a new product, feature, or service from scratch
- Investigating why an existing feature has low adoption or high abandonment
- Redesigning a system that has friction you do not fully understand
- Your team is making decisions based on assumptions, not direct evidence
Core Activities
User Interviews
One-on-one conversations focused on past behavior, not hypothetical preferences.
Session structure:
- Warm-up (5 min) — context, rapport, informed consent
- Grand tour questions (15–20 min) — "Walk me through the last time you..."
- Probing (15–20 min) — "Why did you do that? What were you hoping would happen? How did that make you feel?"
- Closing (5 min) — "What would ideal look like? Is there anything I should have asked?"
Good interview questions:
- "Tell me about the last time you [did the thing you're designing for]."
- "What were you trying to accomplish when that happened?"
- "What did you do when [problem] occurred?"
- "What surprised you about that experience?"
Bad interview questions:
- "Would you use a feature that did X?" — hypothetical, not behavioral
- "Do you like [existing product]?" — opinion, not behavior
- "How often do you [behavior]?" — quantitative without context
Field Observation (Ethnographic Research)
Watch people in their actual environment. What people do often differs sharply from what they say they do.
Observe: physical space, tools used, workarounds invented, interruptions, social context, the actual sequence of actions taken.
Empathy Maps
A synthesis tool using four quadrants:
| Says | Thinks |
|---|---|
| Direct quotes from research | Beliefs and assumptions they hold (inferred) |
| Does | Feels |
| Observed behaviors and actions | Emotional state throughout the experience |
Expert Consultation
Interview domain experts — doctors, teachers, customer service agents, field workers — not as a substitute for user research, but as context for interpreting what you observe.
Key Questions
- What do users actually do, not what do they say they do?
- What is the emotional texture of their experience — where do they feel frustrated, confused, or relieved?
- What context shapes their behavior? (Time pressure, environment, device, social setting)
- What workarounds have they invented? (Workarounds signal unmet needs.)
- Who are the extreme users — power users, non-users, people who tried and quit?
Outputs
- Raw research notes with direct quotes (not paraphrased)
- Empathy maps per user archetype
- List of raw observations (do not synthesize yet — that is Define's job)
- Identified tensions and contradictions to explore
Common Mistakes
❌ Interviewing colleagues or friends as proxies for real users — they know too much ❌ Asking leading questions ("Don't you find it frustrating when...?") ❌ Only talking to existing happy customers — you miss the people who gave up ❌ Skipping this phase because "we already know our users" ❌ Summarizing or interpreting notes immediately — wait until you have enough data to see patterns ✅ Recruit a mix: power users, casual users, non-users, people who tried and quit ✅ 5–8 interviews typically surface the major themes in a well-scoped problem
Stage 2: Define
Purpose
Synthesize your research into a clear, specific, human-centered problem statement. Define is consisten