HEARD, and why the sequence matters

An upset customer wants to feel heard before they want a fix.

Most of us reverse that. When something goes wrong, the first move is to explain: that the person we hired was new, that we were already on it, that no one meant it that way. All true, and none of it what the customer actually needs first. What they need first is to know I understood what happened, before I do anything about it.

Five verbs, in this order

The framework I use for this is HEARD, popularized by Disney.

• Hear is the opening. “Tell me what happened.” No interrupting, no “I understand, but.” Just what happened.
• Empathize is next. “That would upset me too.” Reflect the emotion back before you address the facts. It lands differently than “I see.”
• Apologize follows. “I’m sorry that happened.” Not “I’m sorry you feel that way.” That is not the same apology.
• Resolve is the fix. “Here is what I’m going to do about it, and by when.” But only now, not before.
• Diagnose is different. You change what let it happen. This is the only step the customer never sees. It happens after they hang up, and it is the easiest one to skip.

The sequence is doing all the work

The intuitive order is Resolve first (fix the immediate problem), then maybe Diagnose if there is time, with empathy showing up as an afterthought. HEARD flips that. People need to feel heard before they can hear you, so you cannot skip ahead of them.

In practice, HEARD separates the customer conversation from the operational fix. H, E, A, R is the conversation. Everything that follows (the person, the process, the training) is D. Different problems, different clocks. Most operators try to compress them into one conversation, which usually means the customer walks away feeling like they were the diagnostic, not the customer.

The step that compounds

The other lesson: D is the step that compounds. Every complaint has a system underneath it. Skip D, and next month you write the same email.