Empathize — understand the user first

Observe and interview the people you are designing for before forming any solution.

Why it works

Designers default to building for themselves, projecting their own needs onto users. Direct observation and open interviews replace that projection with evidence, surfacing the latent needs people cannot articulate in a survey. The mechanism is reducing the false-consensus bias — you stop assuming others are like you.

How to do it

1. Interview real users with open "why" and "tell me about a time" questions, not yes/no ones.
2. Watch them do the actual task in their real context; note workarounds and frustrations.
3. Record what they do, not just what they say — the two often diverge.

Evidence

Design thinking is a process framework rather than a tested intervention, so this is mechanistic. The empathize stage draws on established ethnographic and user-research methods that reliably surface needs self-report misses. The false-consensus effect is directly documented — people systematically overestimate how much others share their own views — and LaPiere's classic field study shows how sharply what people say diverges from what they actually do, which is why watching behavior beats asking. (mechanistic)

There is no RCT showing "empathize" as a discrete stage improves outcomes; its value is in counteracting the well-documented tendency to design for oneself.

Sources

• Ross, L., Greene, D., & House, P. (1977). The "False Consensus Effect": An Egocentric Bias in Social Perception and Attribution Processes. Journal of Experimental Social Psychology, 13(3), 279-301.
• LaPiere, R. T. (1934). Attitudes vs. Actions. Social Forces, 13(2), 230-237.

Common mistake

Running a "user interview" that is really a pitch — asking leading questions that confirm the solution you already want to build, so you hear agreement instead of needs.