Empathy is the foundation of design thinking. Before you define a problem, generate ideas, or build anything, you need to deeply understand the people you are designing for. Not what you think they need. What they actually need.

This distinction is more important than it sounds. Most product failures can be traced back to a team that built what they assumed users wanted rather than what users actually needed. The Empathize stage exists to close that gap.

Combine multiple empathy research methods to build a complete picture of user experience

The Goal of Empathy Research

You are trying to understand three things:

What people do when they encounter the problem you defined during initialization. Their actual behaviors, not their stated preferences.
What people feel about the experience. Frustration, confusion, resignation, workarounds they have normalized.
What people need but cannot articulate. The latent needs that only emerge when you observe closely enough.

That third category is where the most valuable insights live. People are generally bad at predicting what they want. Henry Ford's apocryphal quote about faster horses captures this well. Your job as a design thinker is to watch, listen, and read between the lines.

Research Methods

1. User Interviews

Interviews are the workhorse of empathy research. A well-conducted interview reveals motivations, frustrations, and mental models that no amount of analytics data can provide.

Practical guidelines for effective interviews:

Talk to 8 to 15 people. Fewer than 8 and you will not see patterns. More than 15 and you hit diminishing returns (unless your user base is highly segmented).
Ask about specific past experiences, not hypotheticals. "Tell me about the last time you tried to..." is 10x more useful than "Would you use a product that..."
Follow the emotion. When someone's tone changes, when they laugh nervously, when they say "it's fine, I guess" in a way that clearly means it is not fine, follow that thread. Ask "tell me more about that."
Shut up and listen. New interviewers talk too much. Your job is to create space for the other person to share. Silence is a tool. Let it work.
Do not pitch your idea. The moment you start describing your solution, you have stopped doing research and started doing sales. Keep the conversation about their experience, not your product.

2. Contextual Observation

Watching people in their natural environment reveals things interviews cannot. People often do not mention their workarounds because they have normalized them. They do not think to tell you about the spreadsheet taped to their monitor or the three browser tabs they keep open as a memory aid.

If possible, observe your target users in the context where they encounter the problem. A 30-minute observation session often surfaces more insights than an hour-long interview because you see reality rather than a curated narrative.

Take notes on:

Physical environment and tools
Workarounds and unofficial processes
Moments of hesitation, confusion, or frustration
How they communicate with others about the task
What they do immediately before and after the core activity

3. Survey and Diary Studies

Surveys are useful for validating patterns you have already identified through interviews, not for discovering new ones. Use them after qualitative research to check whether the themes you found in 10 interviews hold true across a larger group.

Diary studies ask participants to record their experiences over time (typically one to two weeks). They are especially useful for problems that unfold over days rather than in a single session. For example, if you are studying how people manage their finances, a diary study captures the real rhythm of spending, checking balances, and worrying about bills in a way that a single interview cannot.

Synthesizing Your Research

Raw research data is useless until you synthesize it. This is where many teams get stuck. They have pages of interview notes and hours of observations, but they do not know what to do with it all.

Empathy Maps

An empathy map is the simplest and most effective synthesis tool. For each user archetype, create a four-quadrant map capturing what they Say, Think, Do, and Feel.

The magic of empathy maps is in the contradictions. When what someone says ("I don't care about price") contradicts what they do (spending 20 minutes comparing prices), you have found a genuine insight. Those contradictions are the raw material for the Define stage.

Affinity Clustering

Take all your observations, quotes, and insights from every interview and observation. Write each one on a separate note. Then group them into clusters based on themes that emerge naturally.

Do not start with predetermined categories. Let the patterns emerge from the data. You might expect to find three themes and discover seven. Or you might find that the theme you expected to dominate barely shows up at all. Both are valuable discoveries.

Name each cluster with a descriptive label that captures the insight, not just the topic. "Scheduling is hard" is a topic. "Parents sacrifice their own health appointments to accommodate their children's schedules" is an insight.

Journey Maps

A journey map traces the full experience of a user trying to accomplish a goal. It maps their actions, thoughts, emotions, and pain points at each step. The emotional curve is the most revealing element. Look for the lowest points; those are your design opportunities.

Map the current experience first (what happens today), not your aspirational version of it. You need to understand reality before you can improve it.

How Many People Should You Talk To?

The academic answer is "until you reach saturation," meaning until new interviews stop revealing new information. In practice, here are some guidelines:

Small focused project: 5 to 8 interviews, ideally with observation sessions
Medium project with multiple user types: 8 to 12 per user type
Complex multi-stakeholder project: 15 to 20 across all stakeholder groups

If you are a startup founder validating a problem, aim for at least 15 conversations. Fewer than that and you risk building on a sample that is too small to trust. See our guide for startups for more on research-driven validation.

Common Mistakes

Asking leading questions. "Don't you think it would be better if..." is not research. It is confirmation bias in question form. Ask open-ended questions and let the participant lead.

Interviewing only fans or power users. Your most enthusiastic users will tell you everything is great. Your churned users and non-users will tell you what is actually broken. Seek out the uncomfortable conversations.

Stopping at surface-level answers. When someone says "it's pretty easy to use," do not take that at face value. Ask them to show you. Ask about the last time they got stuck. Ask what they would change. Surface-level answers produce surface-level insights.

Skipping synthesis. Doing 12 interviews and then moving straight to ideation without synthesizing is a waste of those 12 interviews. Take time to process what you learned before moving to the Define stage.

What Comes Next

With your empathy research synthesized into maps, clusters, and journey diagrams, you are ready to move into the Define stage. That is where you will convert your understanding of users into clear, actionable problem statements that guide the rest of the project.