Design Thinking Research: The Complete Guide to the Empathize Phase

Why the Best Products Start With Empathy — Not Ideas

The most expensive mistake in product development isn't bad execution. It's building the right solution to the wrong problem.

Design thinking exists to prevent exactly that. It's a human-centered framework that starts not with ideas, not with technology, but with deep understanding of the people you're designing for. And its first and most critical phase — Empathize — is fundamentally a research discipline.

The numbers behind design thinking are striking:

• Design-led companies outperformed the S&P 500 by 211% over 10 years (Design Management Institute)
• Organizations with mature design thinking practices deliver a median per-project ROI of 229% (Forrester Research)
• IBM clients implementing design thinking saw $48.4M in benefits over three years against $12M in costs — a 301% ROI (Forrester)
• 71% of companies report that design thinking improved their working culture; 69% say it made innovation processes more efficient (IxDF)

None of these outcomes happen without rigorous empathy research at the front end.

---

What Is Design Thinking?

Design thinking is a problem-solving methodology that prioritizes deep human understanding before any solution is considered. Stanford's d.school, IDEO, and IBM have each developed influential versions, but the core structure is consistent across interpretations.

"Design thinking is a human-centered approach to innovation that draws from the designer's toolkit to integrate the needs of people, the possibilities of technology, and the requirements for business success." — Tim Brown, CEO of IDEO

The classic framework has five stages:

1. Empathize — Understand the people you're designing for through research
2. Define — Synthesize research into a clear problem statement
3. Ideate — Generate a wide range of possible solutions
4. Prototype — Build quick, low-cost representations of ideas
5. Test — Gather feedback on prototypes with real users

A critical misconception: these are not sequential steps. Design thinking is explicitly iterative. Teams regularly loop back — new findings in the Test phase often return them to Empathize, or new prototypes reveal the need to Redefine the problem. The diagram of a linear process understates the framework's organic, recursive nature.

---

The Empathize Phase: Why It's the Foundation

The Empathize phase is where all subsequent design decisions are grounded. Skip it or shortchange it, and every downstream step is built on assumption rather than evidence.

"Build bridges of insight through empathy — see the world through the eyes of others, understand the world through their experiences, and feel the world through their emotions." — Tim Brown, IDEO

Empathy in design thinking is not sympathy (feeling for someone) — it's a rigorous effort to understand a person's experience, motivations, and the meaning they make of their world. The Empathize phase is what separates design thinking from traditional product development, which often begins with a solution looking for validation.

The phase has four research stages:

1. Discovery — Broad exploration to understand the problem space and user context
2. Immersion — Deeper engagement to experience the problem firsthand
3. Connection — Identifying patterns and emotional resonance across research data
4. Detachment — Stepping back to synthesize insights objectively

---

Core Empathy Research Methods

1. In-Depth User Interviews

User interviews are the cornerstone of the Empathize phase. Unlike surveys or analytics, they surface the "why" behind behavior — motivations, frustrations, mental models, and unarticulated needs that no other method can reach.

Effective empathy interviews:

• Ask about behavior and experience, not opinions: "Tell me about the last time you tried to do this..." not "Do you think this is important?"
• Use open-ended questions that invite narrative: "Walk me through a typical day when this comes up"
• Probe for emotional context: "How did that make you feel?" "What was frustrating about that?"
• Listen more than you talk — the 80/20 rule applies
• Follow surprising threads rather than sticking rigidly to a script

For the Empathize phase specifically, exploratory and generative interview approaches work better than structured validation interviews. You're not testing a hypothesis — you're understanding a human experience.

2. Observation and Contextual Inquiry

People don't always do what they say, and they don't always know what they actually do. Direct observation in context captures behavior that interviews cannot.

Observation techniques:

• Naturalistic observation: Watch users in their natural environment without interference
• Contextual inquiry: Combine observation with concurrent interviewing — "I notice you just paused there. What were you thinking?"
• Shadowing: Follow a user through their entire workflow for hours or days
• Fly-on-the-wall: Observe without interacting; capture behavioral patterns over time

Contextual inquiry is particularly valuable for identifying the gap between stated preference and actual behavior — one of the most productive tensions in user research.

3. Immersion Studies

Immersion means putting yourself in the user's position as directly as possible. A healthcare team designing patient room layouts might spend 24 hours as a patient. A team redesigning a banking interface might attempt to open an account themselves using only the current system.

Immersion produces visceral empathy that interviews alone cannot generate. It also surfaces operational details and edge cases that users have normalized to the point of forgetting to mention.

4. Surveys and Diary Studies

For broader reach or longitudinal insights, surveys and diary studies complement the depth of individual interviews.

Diary studies ask participants to log their experiences over days or weeks — capturing moments as they happen rather than relying on recall. They're especially valuable when the experience you're researching is intermittent or happens in contexts you can't observe directly.

Empathy surveys are best used to quantify patterns discovered in qualitative work — how common is this frustration? How many people experience this workflow? Koji's structured questions enable this quantification within conversational AI interviews, combining the depth of open-ended dialogue with the measurability of scale, ranking, and choice questions.

5. Listening Sessions and Workshops

Group listening sessions (not focus groups, which introduce social dynamics that distort individual perspectives) bring 3–5 users together to surface collective patterns in experience. Facilitated workshops where participants map their own journeys, draw their mental models, or role-play scenarios often yield insights that one-on-one interviews miss.

---

Empathy Mapping: Synthesizing What You Learn

The empathy map is the primary synthesis tool of the Empathize phase. It organizes research findings around four quadrants:

Below the quadrants, add:

• Pains: Frustrations, obstacles, and fears
• Gains: Goals, desires, and measures of success

How to build an empathy map:

1. Gather your research team and all research artifacts (transcripts, observation notes, photos)
2. On sticky notes, capture every observation that fits a quadrant
3. Cluster similar observations within each quadrant
4. Identify tensions and contradictions (e.g., Says one thing, Does another)
5. Synthesize into 3–5 core insight statements that capture the user's experience

The tensions are often the most generative insights. A user who says they want more control over the interface but does use only default settings is telling you something important about the gap between desire and behavior.

---

From Empathy to Define: "How Might We" Statements

The Define phase begins where the Empathize phase ends. The primary tool for transitioning between them is the "How Might We" (HMW) statement — a reframing technique that transforms research observations into actionable design opportunities.

HMW was originated by Procter & Gamble in the 1970s and later popularized by IDEO and the Stanford d.school. The format is deliberately constrained:

Structure: "How might we [verb] [object] so that [outcome]?"

The three-word opener does specific work:

• "How" acknowledges that a solution exists, projecting optimism
• "Might" creates permission to explore — it's not "how will we" (too committing) or "how should we" (too prescriptive)
• "We" establishes collective ownership of the problem

Examples of HMW statements derived from empathy research:

Research finding: Users feel overwhelmed when they first open the dashboard and don't know where to start. → HMW make first-time users feel confident immediately upon login?

Research finding: Users abandon checkout when they realize they can't go back to change an earlier step. → HMW give users a sense of control and safety throughout the purchase flow?

Research finding: Users feel embarrassed asking for help because it signals to colleagues that they don't understand the product. → HMW enable users to get help discreetly without social exposure?

Well-formed HMW statements are broad enough to invite multiple solutions but specific enough to exclude irrelevant ones. They embed the empathy insight directly into the design challenge.

---

Common Empathy Research Mistakes

"We already know our users"

The most dangerous assumption in product development. Familiarity with your users is not the same as empathy. Teams who skip the Empathize phase consistently build solutions to the problems they imagine users have — not the problems users actually experience. Industry data suggests most companies that skip systematic empathy research are building on assumptions that are 40–60% wrong.

Confusing empathy with sympathy

Sympathy is feeling for someone. Empathy is understanding from their perspective. A researcher who feels sorry for a user struggling with an interface is being sympathetic. A researcher who understands why the interface feels confusing from that user's mental model is practicing empathy. The distinction matters for what you do with the insight.

Asking about opinions instead of behavior

The most common interview mistake in the Empathize phase: asking "What do you think of [feature]?" instead of "Tell me about the last time you tried to [accomplish goal]." Opinions are unstable and context-dependent. Behavioral narratives reveal durable patterns.

Following a rigid script

Empathy research rewards curiosity. When a participant says something unexpected, that's signal — follow it. A strict adherence to a pre-written question list produces surface-level data and misses the surprising insights that drive breakthrough solutions.

Insufficient sample diversity

Researching only your most vocal or most satisfied users creates a false picture of the experience. The most actionable insights often come from edge cases, frustrated users, or people who have churned — people who feel the problem most acutely.

Skipping secondary research

Primary empathy research should be informed by existing data: analytics, support tickets, NPS verbatims, social media. Secondary research identifies where the friction is before you talk to users, making primary research more targeted and productive.

---

How AI Is Transforming the Empathize Phase

Traditional empathy research has a fundamental scaling problem. In-depth interviews are expensive, scheduling is painful, and geographic constraints limit who you can talk to. A typical empathy research sprint — 12–15 interviews — takes 4–6 weeks and costs $15,000–$30,000 in researcher time.

AI-moderated interview platforms are changing this economics fundamentally:

Scale: Where a team could run 15 interviews in a month, AI platforms can conduct 200–500 interviews in 72 hours — across time zones, languages, and user segments simultaneously.

Consistency: AI interviewers never get tired, never ask leading questions, and never skip follow-up probes. They apply the same empathy interview protocol to every participant with perfect consistency.

Depth: Voice-based AI interviews produce conversational richness comparable to human moderation. When participants hint at something emotionally significant, the AI probes deeper — the same way a skilled human interviewer would, but at scale.

Synthesis: Automatic thematic analysis across all conversations surfaces the patterns that define the Define phase without weeks of manual coding. Platforms like Koji identify emerging themes across hundreds of transcripts and surface the most cited insights with direct quotes.

"Leveraging AI in developing empathy maps can reduce research time by up to 44%, while machine learning algorithms identify patterns that human researchers might miss." — AI Research Acceleration Report, 2024

Importantly, this does not replace the human-centered ethos of design thinking. AI handles the operational overhead — scheduling, transcription, initial theme extraction — so researchers can focus on the interpretive work that requires human judgment: synthesizing empathy maps, forming HMW statements, and building the understanding that drives design.

Koji's platform supports the full Empathize workflow:

• Open-ended questions for narrative, exploratory conversation
• Structured questions (scale, single_choice, ranking) to quantify the prevalence and intensity of specific findings
• Automatic transcript analysis to extract themes without manual coding
• Research reports that organize findings in the format needed for the Define phase

---

Designing Your Empathy Research Study

How Many Participants?

The Empathize phase is not about statistical significance — it's about insight depth. For early-stage design thinking, 8–15 participants typically produces sufficient richness for meaningful pattern identification. If you're working with multiple distinct user segments, plan 5–8 participants per segment.

Signs you've reached sufficient insight depth:

• New interviews are confirming patterns already identified rather than surfacing new ones
• Your empathy map clusters are well-populated with diverse examples
• You can write 5–7 HMW statements with confidence

Who to Research

For maximum insight, prioritize:

• Extreme users: People who use the product or face the problem at the extremes — the most intensive users and those who barely use it at all. Edge cases illuminate the design space more sharply than average users.
• Lead users: Early adopters and heavy users who have developed sophisticated workarounds and adaptations.
• Non-users and churned users: People who tried and stopped using your product (or a competitor's) often have the most diagnostic perspective on what doesn't work.

Choosing the Right Research Mode

---

Design Thinking vs. Traditional Product Development

"Design thinking has a bias toward action and empathy toward who you are designing for — to not have a fear of failure." — Bernie Roth, Director, Hasso Plattner Institute of Design, Stanford

---

Getting Started With Empathy Research

Step 1: Define your research question. What aspect of your users' experience needs to be understood? Be specific enough to guide research but broad enough to allow surprising discoveries.

Step 2: Map your assumptions. Before talking to users, list everything your team believes about them. These are your hypotheses. Empathy research will confirm, refute, or complicate each one.

Step 3: Recruit diverse participants. Prioritize range over representativeness at this stage. Include extreme users, edge cases, and people your team doesn't typically talk to.

Step 4: Run exploratory interviews. Aim for 45–60 minute sessions. Lead with open-ended narrative questions. Follow the energy — when something interesting surfaces, go deeper.

Step 5: Build empathy maps. For each participant and then collectively across all participants. Look for tensions between what users say, think, do, and feel.

Step 6: Generate HMW statements. Transform the 3–5 most significant insights into design challenges using the "How Might We" format. These feed directly into Ideation.

Step 7: Validate at scale. Use AI-moderated interviews to test whether patterns identified in qualitative research hold across a larger, more diverse sample before committing to a design direction.

---

Related Resources

• Structured Questions in AI Interviews — add scale, ranking, and choice questions to empathy interviews to quantify insights
• Empathy Map Guide — deep dive on building and facilitating empathy mapping workshops
• Generative Research Guide — the research methods that surface unknown user needs
• How to Write User Interview Questions That Surface Real Insights — question design for deep empathy work
• Qualitative Research Software — tools to support the design thinking research stack
• Prototype Testing and Concept Validation — how the Test phase feeds back into the Empathize phase