How to Escalate Without Making an Enemy

"He went over my head."

Five words, said in a kitchen, to two people who weren't in the meeting. That's the version of your escalation that travels. Not the carefully worded email, not the options table you spent an hour on. Just those five words, and the fact that you'll be working with that person for another two years.

Almost nobody objects to a problem being raised. What people object to is finding out about it from their own boss.

Think about how that lands. Your director forwards them a thread at half eight in the morning with "can you look at this". They've had no chance to prepare, no chance to give their side, no chance to say "yes, we know, here's what we're doing about it". They look, to their boss, like someone who didn't spot their own problem. You did that to them. Not the escalation. The order in which they found out.

So the rule is simple and it has no exceptions worth taking. Nobody learns about an escalation involving them from a third party. You tell them first, in their own words, before you send anything.

It does not have to be a long conversation. "I'm going to raise the test environment delay with Priya on Thursday, because it's now pushing the cutover date and I don't think either of us can fix it at our level. I wanted you to hear it from me. Is there anything in my summary you'd want said differently?"

That's it. Ninety seconds. And notice what it does: it invites them to correct your facts, which they will, and that makes your escalation better. Half the time they'll tell you something you didn't know that changes the whole picture. Occasionally they'll say "give me until Tuesday and I'll have it sorted", and if the date works, you give them Tuesday and you say so in writing.

There's a tell in badly written escalations, and once you see it you can't unsee it. The subject of the sentence is a person or a team.

"The network team hasn't delivered the firewall rules." "Vendor X keeps missing their dates." "The QA lead isn't prioritising our regression pack."

Every one of those is technically true and every one of them starts a fight. You've handed the reader a culprit, and the culprit's manager is now defending a person rather than solving a problem. The conversation becomes about whether the accusation is fair. Nobody talks about the cutover date again for a fortnight.

Write the same facts with the situation as the subject:

"The firewall rules for the cutover are not yet in place, and the window closes on the 14th. The network team has a queue of 40 changes against the same freeze, which I think is the real constraint."

Same information. No culprit. And you've just done something that will be remembered: you named their constraint out loud, on their behalf, in front of their boss. People remember who did that for them.

This is not politeness for its own sake, and it is not softening. You still say the date is at risk. You still say the impact. What you drop is the causal finger-pointing, which was never load-bearing anyway. If somebody genuinely is not doing their job, that is a line-management conversation with their manager, held separately and privately. It does not belong in a delivery escalation, and mixing the two is how you get a reputation you'll spend years correcting.

A 28-person infrastructure function at a food producer is 10 days from an order intake cutover. They need six firewall changes through a security team that has a three-week standard lead time and a hard freeze starting on the 14th. The security team has said no to an expedite twice.

The first draft of the escalation, written on a Tuesday afternoon while annoyed, said: "The security team is refusing to expedite our changes despite knowing the cutover date, which will now slip."

Read that as the head of security reading it. You're being told your team is being unreasonable, by someone two levels below you, in front of your peer. Your first instinct is not to help.

The version that actually went, after a phone call to the security lead first:

"Six firewall changes for the order intake cutover are queued behind roughly 40 others ahead of the 14th freeze. At standard lead time they land on the 21st, which is seven days after the freeze and pushes the cutover to February. I've spoken to Dan and the queue is genuinely full, this isn't a prioritisation oversight at his end. Three options: expedite our six and slip something else with a named owner deciding what, run the cutover with the existing rules and accept a documented workaround for three weeks, or move the cutover to February and tell the production planning team now while they can still replan. I recommend the first, and I think the trade is ours to justify rather than the security team's. I need a decision by Thursday the 8th."

Dan was copied. Dan had already heard it from the writer. Dan then did the single most useful thing in the whole story, which was to reply with "agreed, and if the trade-off is approved I can have all six done in four days." He became an ally in the escalation rather than its target, because nothing in it made him the problem.

The expedite was approved on the Wednesday. And the next time that team needed something from security, they got a phone call back in an hour.

An escalation that gets a decision and then no acknowledgement leaves a bad taste even when it went your way. Close the loop deliberately: reply to the same thread, same recipients, say what was decided, what happened, and name the people who made it happen. Especially the person you escalated about.

"Decision taken on the 8th to expedite. All six rules in place by the 12th, cutover holds. Thanks to Dan's team for turning them round in four days against a full queue."

That costs you nothing. It buys you the thing that makes the next twelve escalations easy, which is a person who knows that being involved in one of your escalations is survivable.

Take whatever you're currently planning to escalate and find the name in it. If a person or a team is the subject of any sentence, rewrite that sentence so the situation is.

Then pick up the phone to that person before you send it. Not an email, a call. Tell them what you're raising, when, and to whom, and ask them to correct anything you've got wrong. If they ask for a few days and the date still works, give it to them in writing with the date in it.

If they ask for a few days and the date doesn't work, say so, and send it anyway. Warm is not the same as soft.