How to Escalate an Issue Without Burning Bridges
Need to escalate at work? Here's how to do it professionally — try direct resolution first, document, frame around impact, and keep people in the loop.
Escalate by framing it around impact, not blame — and looping in the person you're escalating about, not going behind them. Done right, escalation looks like you protecting the work; done wrong, it looks like a complaint. The difference is transparency and tone.
Try the direct route first
Before escalating, attempt to resolve it with the person directly. Skipping that step is what burns bridges. If it's already been tried, note that.
How to escalate cleanly
- Lead with impact: "This is putting the launch date at risk."
- Be factual: dates, blockers, what's been tried — no editorializing.
- Propose a resolution: don't just dump a problem; suggest a path.
- Loop people in: CC or mention the person involved where appropriate — no ambushes.
Example
"Flagging a risk on the launch: we've been blocked on X for a week. [Colleague] and I have tried A and B; we now need a decision on C. Could we get 15 minutes to align? I've included [colleague] here."
What burns bridges
- Going over someone's head silently.
- Framing it as a personal complaint.
- Exaggerating or being vague.
- Surprising the person in front of leadership.
A quick read
What's happening: a blocker needs a manager's involvement to resolve. Best move: impact-framed, factual, with the person looped in. Avoid: a behind-the-back complaint.
Where Ulet fits
Ulet's Work mode helps you escalate around impact, not blame — professional and transparent, in your own voice. Screenshots are never stored.