Building with Empathy

Empathy is not a workshop exercise

In most product organizations, empathy lives in the discovery phase. You run a user interview, fill in an empathy map, present the findings, and then build what was already planned. That is not empathy. That is documentation.

Real empathy in product means letting what you learn from users actually change what you build. It means the engineer hearing directly from a frustrated customer and redesigning the flow on the spot. It means the PM admitting their hypothesis was wrong because the data and user interviews confirm it. It means releasing a product that is smaller and more honest than the roadmap promised — because that smaller version solves the real problem.

The gap between functional and resonant

Functional products solve a problem. Resonant products make the user feel understood. Two products can have identical functionality and produce completely different emotional responses. The difference is in the intentionality of design choices — the micro-decisions about language, timing, friction, and flow that communicate whether the product was built by someone who thought carefully about the experience.

An example: onboarding. Most products treat it as a sequence of steps the user must complete before accessing the product. The experience communicates: "complete these tasks so we can activate you." A product built with empathy acknowledges the user arrived with a specific job to be done, surfaces the most direct path to that job, and removes everything that doesn't contribute to the first moment of value.

Empathy at scale is a systems problem

Individual PMs can be empathetic. Scaling empathy requires intentional systems. What works:

• 1
  Customer proximity as a standard: Every PM, designer, and engineer talks to a real user at least twice a month.
• 2
  Churn as a design input: Every churned user is a product failure containing a lesson, treated with the same rigor as growth.
• 3
  Language as a product decision: The words inside a product are not copy written after design is done. They are design. The label on a button, the error message, the empty state — these are the moments when the product speaks directly to the user.