Empathy Gap.

01Overview

The empathy gap — also called the hot-cold empathy gap — is the systematic failure to predict how visceral states (hunger, pain, anger, fear, fatigue, stress) affect our own and others' behaviour and preferences. When we are in a "cold" state — calm, rational, comfortable — we consistently underestimate how profoundly "hot" states change what we want, what we decide, and how we behave.

For designers, this is a foundational research methodology problem. Products are almost always designed in cold states — comfortable offices, controlled lab conditions, well-rested and well-fed designers — but experienced in hot states: users who are stressed, rushing, frustrated by a previous error, or under genuine time pressure. The gap between those states produces systematic blind spots in design.

02Detailed explanation

Loewenstein's 1996 research established the theoretical framework. Experiments show that people in a cold state underestimate how hunger affects food choices, how pain affects willingness to pay for relief, how sexual arousal affects risk-taking, and how anger affects punishment decisions — even when they are explicitly asked to account for the state change.

• The gap operates in both directions: when in a hot state, we underestimate how differently we will behave in the corresponding cold state (and vice versa). Cold people think they won't give in to temptation; hot people think they'll still feel the craving tomorrow.
• The gap also operates interpersonally — we cannot accurately empathise with others in states we are not currently in. A designer who has never experienced severe chronic pain cannot accurately imagine what a healthcare interface feels like to use during an acute episode.
• The gap is not resolved by instructions to "imagine" the other state — simply thinking about being hungry doesn't produce the same predictive accuracy as actually being hungry. Imagination is a cold-state cognitive operation.

03Why it exists

Visceral states are processed by separate neural systems from our deliberative, reasoning mind. When we are in a cold state, our predictive models of our own behaviour are built by the cold system — which cannot accurately simulate the influence of the hot system on future behaviour. The brain simply doesn't have access to what it feels like to be hungry, aroused, or afraid when it isn't those things.

04Effects on users

• Users signing up for a service in a relaxed, exploratory state make different decisions than users who return under time pressure to complete a specific task — the same interface feels different in each state, and the design typically only accounts for one.
• Error flows designed by calm engineers feel brutally cold to users who are already frustrated by the error that triggered them — the empathy gap produced a mismatch between the emotional register of the message and the emotional state of the user receiving it.
• Healthcare, financial emergency, and crisis support products are almost always designed in cold states but used in hot ones. The gap between the design context and the use context is most severe — and most consequential — in these domains.
• Users who say in research "I would just re-enter my card details" are in a cold state. Users who are actually re-entering card details for the fourth time, having missed a step they were never told about, are in a qualitatively different state that their cold-state predictions don't capture.

05Effects on designers & teams

• Research design: interviews conducted in a studio or Zoom call are almost never in the same emotional state as the real-world use context — designers interpret findings through the cold state, missing the hot-state dynamics that drive real behaviour.
• Error state design: error messages written by engineers who are not in an error state are calibrated for cold, rational reading — not for the frustrated, confused, or urgent state of the user who will actually encounter them.
• Content tone: UX writers composing in a calm working session can't fully simulate the emotional register of a user who is about to lose their work, has just received bad medical news via the product, or is trying to complete a transaction in two minutes before a deadline.
• Deadline and urgency design: teams that have never experienced their own product under genuine time pressure design urgency states — loading indicators, timeout warnings, step-progress messages — that feel insufficient or dismissive to users who are actually under pressure.

6Introspective view

Look inward. In a calm studio, teams cannot accurately predict how stressed, rushed or emotional users will feel in the moment.

From an introspective perspective, ask how Empathy Gap may already be shaping your research, critique, planning, and interpretation — not only what users encounter in the finished interface.

7Extrospective view

Look outward. Designs made in a cool state under-serve users in hot states (stress at checkout, anger in support).

From an extrospective perspective, Empathy Gap is a property of the product experience itself — visible in pricing, copy, defaults, layout, and the moments where users decide whether to continue, convert, or leave.

08Practical takeaways

• Conduct contextual research in the use environment: observe users in the real context — at their actual workstation, in their actual process, at the time they actually use the product. Emotional state is contextual; lab conditions strip it.
• Map emotional states onto the user journey: explicitly identify which journey stages are likely "hot" states (time pressure, frustration, confusion, urgency) and design specifically for those emotional contexts — not just the calm, exploratory states.
• Test error states with users who are already frustrated: the most honest evaluation of an error message is reading it when you've just been through the experience that triggered it, not when a researcher reads it to you in a calm interview.
• Hire for diverse lived experience: team members who have personal experience of the difficult states your users face — chronic illness, financial precarity, caregiving stress — have smaller empathy gaps in those contexts. This is a genuine design capability.
• Read support tickets as hot-state evidence: customer support contacts are the hot-state record — the messages users write when they are frustrated, confused, or urgently stuck. They contain emotional signal that cold-state research misses entirely.

09Design examples

10Ethical risks

The empathy gap is exploited when products deliberately place high-stakes decisions or consent flows at hot-state moments — when users are excited, frustrated, or time-pressured — knowing that the hot state impairs deliberation in predictable ways. Urgency design, scarcity messaging, and "you're almost there" prompts at decision points all leverage hot-state impairment to reduce scrutiny.

Designing for hot states means designing for the full human — not the calm, rational, well-rested person who doesn't exist at the moment of use. It is both the hardest and most important empathy work in the discipline.

11Related biases