Tactical empathy at work: mirroring and labeling scripts for product managers

Tactical empathy is the name Chris Voss popularised for making the other side feel heard on purpose, as a negotiating move rather than a courtesy. Voss spent a 24-year tenure with the FBI, where he became its lead international kidnapping negotiator, according to his Black Swan Group biography. In How to Use the Key to Tactical Empathy, he describes the target outcome: "That's right is what your counterpart says when they feel completely understood."

Why does tactical empathy matter at work, not just in hostage talks?

Most of a PM's negotiations are with people who have more authority than you and who will still be your colleagues next quarter. You cannot out-rank a CEO or order an engineering lead to change an estimate. What you can do is find out what is actually driving their position, and that information rarely comes out while they are defending it.

Tactical empathy works because it lowers the defence. Voss draws a sharp line between two responses in the same piece: "Get a that's right and you're in a good place. Get a you're right and you're in a bad place." "You're right" is what people say to end a conversation. "That's right" is what they say when you have described their view better than they had, and it is usually followed by the detail you needed.

What are mirroring and labeling?

The two core moves are small enough to use in any meeting.

A mirror repeats the last few words the other person said, with a slight upward tone, and then waits. Isaac R. Betancourt of The Black Swan Group sums up the instruction as "Repeat the last few words they say back to them." in his piece on labeling. A mirror costs nothing, sounds like interest, and almost always gets the person to expand.

A label names the emotion or dynamic behind what they said. Betancourt defines labeling as "a technique that allows us to attach a tentative identifier to the dynamics, emotions, or circumstances implied by your counterpart's words and actions." The word tentative matters. A label is a hypothesis you offer, not a diagnosis you deliver, and a wrong one still earns a correction that tells you more.

Move	What you say	What it gets you
Mirror	Their last few words, as a soft question	More facts about their position
Label	"It sounds like..." or "It seems like..."	The feeling or pressure behind the position
Summary	Their view and their feelings, played back in full	The "that's right" that means they feel understood
Silence	Nothing, for a few seconds after a mirror or label	Room for them to fill with detail

How do you use tactical empathy when the CEO objects to your roadmap?

Situation: you present a quarter focused on retention, and the CEO says, "I don't think retention work is going to move anything the board cares about."

• Mirror: "Anything the board cares about?"
• Label: "It sounds like you're under pressure to show new revenue this quarter, and retention feels like it won't show up in time."

The mirror usually gets you the specific metric the board is watching. The label names the pressure without accusing the CEO of short-termism. If the label is right, you can reframe the roadmap around that metric (retention as protected revenue). If it is wrong, the correction tells you the real objection, which might be about credibility, timing or a competitor.

How do you use it when an engineering lead pushes back on scope?

Situation: you ask for a feature by the end of the quarter, and the engineering lead says, "That's not happening without cutting corners on the migration."

• Mirror: "Cutting corners on the migration?"
• Label: "It seems like you've been burned before by dates that got set before anyone looked at the migration."

Engineering pushback is often about history, not the current request. The label invites the lead to tell you what went wrong last time, and that story usually contains the constraint you need to plan around. From there, the conversation becomes a trade of scope and dates, which is covered in detail in how to negotiate deadlines with stakeholders.

How do you use it when sales escalates a customer request?

Situation: a sales director messages you: "If we don't have SSO by the 30th, we lose the account. I've told them it's coming."

• Mirror (on a call, not in chat): "You've told them it's coming?"
• Label: "It sounds like you're in a tough spot, because you've made a commitment to a customer you really want to keep, and now it depends on us."

The label acknowledges the sales director's exposure without agreeing to the date. It also surfaces what was actually promised, which is often narrower than "SSO by the 30th." Once you know what the customer was told, you can negotiate what to deliver, or decline cleanly, as described in how to say no to stakeholders.

How do you label the thing everyone is avoiding?

Name the negative before the other person does. If you are about to ask for more time on a project that already slipped once, open with the label: "You're probably thinking this team always asks for more time." It feels risky, but it takes the accusation out of their mouth and makes it discussable. Voss's reasoning, in the same Black Swan piece: "no elephant in the room ever went away because everyone denied it was there in the first place."

Two cautions apply to all of this at work. Delivery matters more than wording: Jorge Gayle of The Black Swan Group writes in Managing Up with Tactical Empathy that "Delivery is just as important as the skills themselves." And sincerity is not optional. A colleague who spots a technique being run on them stops trusting everything else you say, so use labels only when you actually believe them.

What is the strongest argument against tactical empathy at work?

The fair objection is that it can slide into performance: a PM who labels every feeling in every standup sounds scripted, and a technique built for high-stakes crises can feel out of proportion in a sprint review. That objection is right about overuse. Keep mirrors and labels for the conversations where someone is defending a position you need to understand, and talk normally the rest of the time.

If you want to build these moves into your preparation, AI for negotiation prep shows how to rehearse a difficult conversation with a model playing the other side, and the best negotiation resources for product managers collect the books and talks worth reading next.

Where does Builders Camp cover stakeholder negotiation?

Negotiation for Product Managers is a 1 week Builders Camp bootcamp with 2 live sessions, directed by Andre Albuquerque, in the Product Management Starter Track and the Product Leadership Track. Its published topics include conflict and difficult conversations (de-escalating, keeping trust and resolving disagreements without avoidance), framing to shift conversations from positions to outcomes, and negotiation across product, design, engineering, sales and leadership. See the Negotiation for Product Managers bootcamp for dates and format.