cognitive psychology
Empathy gap
What is the empathy gap?
The empathy gap is how badly we predict behaviour - our own and others' - across different emotional or physical states. Calm, we can't really feel how we'll act when stressed, rushed, hungry or angry, so a "cold" version of us consistently underestimates how much a "hot" state changes what we do.
Also known as: empathy gap, hot-cold empathy gap
Prefer to watch?
Watch the recap 0:58
The demo
Right now, relaxed: how many seconds would you happily wait for a slow page to load before giving up? Set it. Then we'll change one thing about your situation and ask again.
What this demo shows (text version)
While calm, you set how many seconds you'd patiently wait for a slow page before giving up. Then the demo puts you in a "hot" state - you're already late for a payment deadline and the page is crawling - and asks again. For most people the tolerated wait collapses, because the relaxed version of you genuinely couldn't feel how little patience the stressed, hurried version would have.
That gap between your cold prediction and your hot behaviour is the empathy gap. It's why interfaces that test fine in a calm studio fail for rushed, stressed, distracted real users - the unhurried team can't simulate the user's state. Close it by testing under realistic pressure and designing for the worst moment, not the calm demo.
We can't feel a state we're not currently in, so we mispredict behaviour across states. Calm and unhurried, you genuinely cannot simulate how impatient, anxious or distracted you'll be in the moment - which is exactly the problem for designers, who build in a quiet, focused state for users who are often rushed, stressed, multitasking or upset. The unhurried team underestimates the rushed user. Close the gap deliberately: test under realistic pressure and context, design for the worst moment not the calm demo, and don't assume people in a hot state will behave like you do reviewing the screen in a cold one.
Calm, you said you'd happily wait - but picture yourself already late and that patience evaporates, doesn't it? That's the empathy gap: your cold, unhurried self can't feel your hot, hurried one. It's why designs that test fine in a quiet room fall apart for stressed, rushed, real-world users - the team simply couldn't feel the state their users are in.
The classic form is the hot-cold empathy gap: in a cold state (calm, satisfied) we underestimate the influence of hot states (hunger, fear, urgency, anger, pain) on our choices, and vice versa. We can't vividly simulate a visceral state we're not in, so predictions made in one state about another are systematically off - which is why "I'd never do that" often loses to the moment.
For design this is a core reason usability problems get missed. Teams build and review interfaces in a calm, expert, focused state, while real users arrive rushed, distracted, anxious, on a small screen in bright sun, or already frustrated by an earlier failure. The unhurried maker underestimates how much those conditions degrade attention and patience, so flows that feel fine in the studio fail in the wild.
Close it by getting into - or simulating - the user's actual state: test under time pressure, interruption and realistic context; recruit participants who are genuinely in the situation; and design for the stressed, hurried, worst-case moment rather than the calm happy path. Empathy gaps also matter in research itself, since people asked to predict their future feelings (in a survey, say) are often wrong about them.