The Right Order of Telling: How to Escalate a Problem Without Making It Personal

It's a Tuesday afternoon and the supplier who promised you stock by Friday has gone quiet. You're not the account lead. You're not the director. You're just the person who noticed. And now you're staring at an email chain wondering whether to reply, ring someone, or quietly hope it sorts itself out.

That bind is familiar to almost every young leader. The problem is real. The hierarchy is real. And the gap between the two is where careers get made or mildly dented. Escalation isn't a dirty word — it's how organisations find out what's actually happening. But the order in which you tell people matters, and so does the way you frame it.

First, work out what you're escalating

There's a difference between escalating a risk and escalating a person. A slipping supplier is a risk. A colleague who missed a deadline might be a risk, or might be a person having a rough month. A compliance worry is almost always a risk that needs a different route entirely.

Get this wrong and you turn a solvable operational issue into a relationship problem. Get it right and you look like someone who understands the difference between noise and signal. Before you speak to anyone, finish this sentence in your head: 'The thing I'm worried about is ______, and the impact if nothing changes is ______.' If you can't fill both gaps, you're not ready to escalate. You're ready to ask a question.

Rung one: the quiet word

Start with the person closest to the problem. Not a confrontation — a question. Something like: 'I noticed the purchase order hasn't moved since Thursday. Is there something I can help unblock, or should we flag it upwards together?'

That last clause is doing a lot of work. It signals you're not going behind anyone's back, and it gives them a chance to fix it before it becomes a Thing. In UK workplaces, where a raised eyebrow often carries more weight than a raised voice, this rung is criminally underused. Most problems die here, quietly and correctly. If the quiet word works, you've saved everyone a meeting.

Rung two: the short written note

If the quiet word doesn't shift anything, put it in writing — but write it like a summary, not a charge sheet. An email that says: 'Just to confirm where we got to — the supplier hasn't confirmed delivery, I've chased twice, and we need a decision by Wednesday to avoid affecting the launch. Happy to take the lead on chasing if that helps.'

Notice what's missing: blame, tone, and a cc to anyone senior. At this stage the note is for clarity, not evidence. It gives the other person a fair chance to respond and it gives you a record that reads like someone trying to solve a problem rather than build a case.

Rung three: the side-door check

Before you go up, go sideways. This is the rung people forget. Talk to someone who knows the policy or the politics — a trusted peer in another team, HR if it's a people issue, compliance if it's a regulatory one. Ask a simple question: 'If this were your problem, who would you tell first?'

For a supplier delay, the side-door might be procurement. For a missed deadline, it might be a peer who knows the colleague's workload. For a compliance worry, it's almost certainly a named contact in the policy — and you should use it early rather than late. A compliance issue is not a relationship puzzle. You don't sit on it to be polite.

Rung four: the manager conversation

When you do go to your manager, bring a decision, not a download. 'Here's what I know, here's what I've tried, here are two options, and here's what I'd recommend.' That structure does two things: it shows you've done the legwork, and it gives your manager something to say yes or no to rather than a vague worry to absorb.

This is also where you name the risk plainly, without dressing it up. 'If we don't decide by Wednesday, the launch slips by a week.' Senior people are not fragile. They're busy. Clarity is a kindness.

Rung five: the formal raise

Sometimes the polite route runs out. A grievance, a formal speak-up, a whistleblowing channel — these exist because earlier rungs sometimes fail. Using them is not a failure of relationship. It's a failure of the earlier rungs to produce a fix. And if you've kept a record, this rung is far less dramatic than it sounds: you're simply handing over a timeline that already exists.

When skipping a rung is genuinely right

If someone is at risk, the ladder becomes a fire escape. Safeguarding, safety, serious compliance breaches — you go straight out and you don't apologise for it. The same applies if you've already raised something twice and nothing has moved. At that point, going over a head is not overstepping. It's following through.

The judgement call is this: skip rungs for urgency, not for impatience. If you skip because you'd rather not have an awkward conversation, you'll pay for it later in trust.

Keep a record that helps, not harms

Notes aren't ammunition. They're memory. A short log — date, what you observed, who you told, what you asked for — is enough. Write it in plain language you'd be happy for anyone to read. The point isn't to catch someone out. It's to be able to explain your judgement if anyone ever asks why you did what you did, when you did it.

Escalation is a leadership skill, not a personality flaw. The goal isn't to reach the top rung. It's to solve the problem at the lowest rung that works — and to know, with a clear head, when it won't.