Most designers believe they understand their users. The problem is that understanding and empathy are not the same thing. Understanding processes what users say. Empathy registers why they say it, what they leave out, and what they do when no one is asking questions.
User-centric design depends on that distinction. Without genuine empathy, design research becomes a collection of data points that confirm what the team already suspected. With it, research reveals the contradictions, habits, and unspoken frustrations that produce real design breakthroughs. This article covers the core methods that move design practice from surface-level insight to the kind of empathy that changes outcomes.
What You’ll Learn
- Why open-ended interviews generate richer empathy than structured question sets
- How observation uncovers what users can’t or won’t articulate directly
- How empathy mapping and journey mapping convert raw research into actionable design direction
- Why co-creation transforms users from research subjects into design partners
- The two most significant barriers to empathy in design practice, and how to address them
- What empathy research produces beyond the product itself, and why the choice of method decides what you can see
How Do User Interviews Build Genuine Empathy?
User interviews build genuine empathy when they are structured as conversations rather than questionnaires. The shift from closed to open-ended questions—”Tell me about a time when…” instead of “How often do you…”—gives users room to surface narratives designers wouldn’t have thought to ask about. Those narratives contain the emotional context that drives real design decisions.
In 2009 Airbnb was taking in about $200 a week in New York and the number would not move. Instead of running a survey, the founders flew out, knocked on their hosts’ doors, and spent time inside the apartments people were actually listing. Paul Graham built his essay on doing things that don’t scale around that trip; weekly revenue there roughly doubled after it. The harder finding took longer to name—what the company was designing for was trust between strangers, which co-founder Joe Gebbia laid out in a 2016 TED talk. Neither one was sitting in the booking data. A structured questionnaire would have buried both.
We run interviews in our own work, though not with the users of a product. Brand work starts with the people inside an organization: founders, staff, whoever has been there long enough to have opinions about what the place actually is. The mechanics are the same as design research, and so is the failure mode. Ask someone directly what their company stands for and you get the rehearsed answer, the one assembled for investors and polished by repetition. Ask them to describe a decision they lost, or a client they turned down, and you get the real position. What people say about themselves is a claim. What they can describe in detail is evidence.
The most reliable approach is to ask open questions, then hold silence after the answer. Most interviewees will fill that silence with elaboration that reveals more than their initial response. Reflecting back what you’ve heard—”It sounds like that part is the frustrating one”—invites users to clarify, correct, and go deeper.
Key takeaways:
- Open-ended questions create space for narratives; closed questions confirm what you already believe
- Silence after an answer is a research technique, not a gap to fill
- Reflection and paraphrasing surface the emotional layer beneath stated preferences
What Can Observation Reveal That Interviews Cannot?
Observation surfaces friction that users have normalized. When an experience becomes routine, people stop perceiving it as a problem—and stop reporting it as one. Direct observation captures those invisible pain points by watching what users actually do, not just what they say they do.
IDEO’s shopping cart redesign is the most cited demonstration of this principle, and it was filmed: ABC’s Nightline gave the firm five days to rebuild the cart from scratch and aired the result as “The Deep Dive” on February 9, 1999. Rather than start with surveys, the team watched shoppers navigate real store environments. They saw people struggle with unwieldy carts, maneuver through crowded aisles, and worry about their children’s safety. The child seating change—one of the project’s most consequential—came from watching behavior shoppers had long since stopped noticing.
The most common mistake in user research is over-indexing on interview data and skipping observation entirely. Immersion closes that gap. For a team designing an app for older adults, a single session navigating a phone through glasses that simulate vision impairment can generate more actionable empathy than hours of interviews. The experience of encountering a problem directly changes what a designer looks for and what they build.
Key takeaways:
- Normalized friction rarely surfaces in interviews—observation is required to find it
- Shadowing users without intervening produces richer behavioral data than guided sessions
- Direct immersion in the user’s environment builds the kind of empathy that interview transcripts describe but cannot create
How Do Empathy Maps and Journey Maps Translate Research Into Design Direction?
Empathy maps and journey maps translate qualitative research into structured frameworks that surface contradictions and reveal overlooked pain points. An empathy map organizes what users say, think, feel, and do into a visual framework that makes underlying motivations and inconsistencies visible. A journey map traces the emotional arc of a user’s experience across every interaction with a product or service.
The value of an empathy map is in the contradictions it reveals. Users who say they prioritize speed often behave cautiously and deliberately when observed—taking careful steps to avoid making errors. Without the map, that gap between stated preference and actual behavior stays invisible. With it, designers can build for what users do rather than what they claim to want.
Journey mapping extends this to the full scope of an experience. A team at Amsterdam UMC mapped the journeys of 13 patients aged 70 and over who had returned to the emergency department within 30 days of an earlier visit, and published what they found in European Geriatric Medicine in 2022. The friction was not in the clinical care. It was in the waiting, and in discharge communication that left patients unsure what happened next—both of them on the outer edges of the visit, where nobody had been looking.
As a general rule, the most significant friction in a user experience is rarely where the team expects to find it. Mapping the full arc of an interaction, not just the product moments, is what makes that friction visible.
Key takeaways:
- Empathy maps surface the gap between what users say and what they do—that gap is where real design insight lives
- Journey maps reveal pain points outside the product itself, including interactions the team may not have considered
- Visual mapping exercises turn raw research into a shared reference the entire team can act on
What Does Participatory Design Add That Research Alone Cannot?
Participatory design adds the dimension that research describes but cannot produce: users as active contributors to the solution. Co-creation invites users into workshops and prototyping sessions where they ideate, critique, and build alongside the design team. The result is a design shaped by the people who will use it, not just informed by their responses to questions about it.
For a 2017 study in the ACM Designing Interactive Systems proceedings, Gillian McCarthy, Edgar Rodriguez Ramírez, and Brian Robinson put five young people with type 1 diabetes in a room with five designers and had them prototype blood glucose monitors together. The session produced five rough prototypes and six distinct strategies for handling the stigma of a visible medical device—among them disguising it as an ordinary object, making it customizable, and pushing the other way entirely to strengthen its identity as medical equipment. That last one is not a direction a design team arrives at by asking a teenager which features they want. It came from users given the tools and the context to contribute directly to the design.
If the goal is to understand unspoken needs and generate design directions that didn’t exist before, participatory design is the right method. If the goal is to validate a concept the team has already developed, usability testing is more appropriate. Both are valuable, but they answer fundamentally different questions.
Key takeaways:
- Participatory design generates ideas that research alone cannot surface
- Users contribute differently when given agency in the process, not just asked to evaluate what already exists
- Co-creation demonstrates empathy in action—it builds trust between a design team and its audience by showing that input shapes outcomes
What Are the Most Common Barriers to Empathy in Design Practice?
The two most significant barriers to empathy in design practice are resource constraints and confirmation bias. Resource constraints are real but frequently overstated—brief, focused empathy sessions generate more insight per hour than extended research cycles that lack clear objectives. Confirmation bias is more insidious: it operates invisibly, shaping which questions get asked, which responses get weighted, and which findings get acted on.
The practical fix for resource constraints is a focused empathy sprint: a short research session built around a single, well-defined question. A two-hour observation session or five targeted interviews can produce more actionable insight than a week-long research cycle without a clear problem statement. Small-scale empathy exercises also build internal credibility for deeper research investment over time.
Confirmation bias requires a different intervention. Recording all sessions and reviewing them with team members who weren’t present reduces the influence of any single observer’s interpretation. Bringing in colleagues from backgrounds different from the design team’s introduces perspectives that challenge embedded assumptions. The most reliable approach is to ask before each session: “What am I already assuming about what I’ll find?” That question doesn’t eliminate bias, but it makes assumptions visible and therefore addressable.
Key takeaways:
- Resource constraints are a real barrier, but focused short-cycle empathy work produces strong returns relative to time invested
- Confirmation bias shapes research design before a single interview begins—naming it is the first step to managing it
- Diverse perspectives in the research process reduce the influence of any single team member’s assumptions
What Does Empathy Research Produce Beyond a Better Product?
Empathy research produces a defensible account of what an audience actually needs, and that account is the raw material for more than an interface. At Subverse this is where brand work begins. Narrative Branding, our methodology, builds a brand’s meaning as a coherent system, so that everything an organization says, shows, and does reinforces the same understanding. That system cannot be assembled out of assumptions about the audience. It has to be built from evidence about them.
The connection runs through resonance. A brand resonates when what it offers aligns with what the people it serves are facing, and that alignment cannot be engineered from a conference room. It is earned by knowing in specific terms what the audience is dealing with, which is what interviews, observation, and mapping produce. Design teams use that material to build products. We use it to decide what a brand should mean and which signals belong.
Which is why the choice of method carries more weight than it appears to. Each one returns a different kind of evidence: interviews return narrative and stated intent, observation returns behavior, mapping returns the contradictions between the two, co-creation returns direction the team did not already have. Run one of them and you have a partial account of the person you are designing for. Treating them as interchangeable is how a team ends up confident about an audience it has only heard from in one register.
Key takeaways:
- Research that stops at the product wastes most of what it surfaced — the same evidence defines what a brand should mean
- Resonance is earned by knowing specifically what an audience faces, which is what empathy methods exist to establish
- Each method returns a different class of evidence, so the method you choose determines what you are able to see
Conclusion
Empathy in design is not a disposition. It’s a discipline with specific methods, each suited to a different kind of insight. User interviews surface narrative and context. Observation reveals what users have normalized and stopped reporting. Empathy maps and journey maps translate raw research into usable structure. Participatory design gives users a role in shaping outcomes, not just evaluating them.
The most common failure is treating these methods as interchangeable—selecting one and skipping the others. Each addresses a blind spot the others cannot. Using at least two methods, one that produces narrative and one that produces behavioral data, then mapping what they reveal against each other, is where the most useful contradictions surface. Those contradictions are almost always where the real design work begins.
Start with a single method on your next project. Make it deliberate, bounded, and reflective. Then do it again.
