Escalating a blocker
Escalate a blocked issue to another team without blame, or receive one and own it.
Case study: The ticket that waited 19 days
Aakash, a developer in Pune, needed the platform team in Tokyo to open a firewall rule for a client go live. He raised a ticket, then pinged three times on Slack. Nineteen days passed. Finally, in a client call, his delivery head blurted, "The Tokyo team has been sitting on it." The platform manager heard about it secondhand and was furious. Two weeks later, Aakash's colleague Megha hit a similar block. On day four she messaged the platform manager directly: what she needed, why it mattered, the date at risk, and what she'd already tried. It was done in two days.
Takeaway: Escalate early, privately and with facts. An escalation is a request for help, not an accusation.
Many of us wait too long to escalate because it feels like complaining, then it explodes in a big meeting. Global teams expect an early, calm escalation with facts, and they treat it as normal project hygiene.
Escalating the issue
Goal: Get the blocker unblocked with a clear owner and date, while keeping a good relationship with Hiroshi's team.
Step by step
- Escalate early. After one or two follow ups, not after three weeks.
- State the facts. What you need, the ticket, what you tried, and the dates.
- Show the impact. What date or customer is at risk if it slips.
- Ask for help, not blame. Frame it as "help me get this unblocked", never "your team is slow".
- Agree an owner and date. Close with who will do it and by when.
Say this, not that
| Hi Hiroshi, I'd like your help with a blocker. I don't think it's anyone's fault, but it's now putting a date at risk. | Your team is not responding at all. | Blame makes people defend. A request for help makes them act. |
| We raised ticket NET 482 on the third for a firewall rule. We've followed up twice, and it's still unassigned. | Facts and dates let him check quickly. | |
| If it isn't done by Friday, the client go live on the twentieth will slip. | It is very very urgent. | Impact is more convincing than urgency words. |
| Is there anything I can do on our side to make it easier, like a call with your engineer? | ||
| Could we agree who will pick it up and a date I can share with the client? |
Model conversation
- You
- Hi Hiroshi, thanks for taking my call. I'd like your help with a blocker that's now putting a client date at risk.
- Hiroshi
- Of course. What's happening?
- You
- We raised ticket NET 482 on the third for a firewall rule. We've followed up twice in the channel, and it's still unassigned.
- Hiroshi
- I see. We've had two people on leave this month. I'm sorry it's been slow.
- You
- Totally understand. The impact is that if it isn't done by Friday, the client go live on the twentieth slips.
- Hiroshi
- That's important. Let me look at the queue.
- You
- Thank you. Is there anything I can do on our side to make it easier, like a quick call with your engineer?
- Hiroshi
- That would help. I'll assign Kenji today, and he'll aim for Thursday.
Receiving the escalation
Goal: Calm the situation, own your team's part, and give Neha a credible timeline without throwing anyone under the bus.
Step by step
- Acknowledge. Thank them for raising it. Don't argue with their frustration.
- Get the facts. Ask for the ticket and the date at risk before promising anything.
- Own it. Take responsibility for your team, even if the cause is complex.
- Give a timeline. A specific next update and a realistic date.
Say this, not that
| Thanks for raising this with me directly, Neha. I'm sorry it's taken this long. | We are also very busy, you know. | Defending first makes the other person escalate higher. |
| Could you send me the ticket number and the date that's at risk? | ||
| That's on us. We should have flagged the delay earlier. | Actually, the junior on my team missed it. | Own it as a manager. Fix it inside your team, privately. |
| I'll have someone on it today, and I'll update you by four o'clock with a firm date. | A near term update rebuilds trust quickly. | |
| Going forward, let's set up a shared channel so this doesn't get lost again. |
Model conversation
- Neha
- Hi, I need to escalate something. Our database migration request has been waiting on your team for twelve days.
- You
- Thanks for raising this with me directly, Neha. I'm sorry it's taken this long. Could you share the ticket and the date at risk?
- Neha
- It's DBA 219. Our release is on the fifteenth, and the client is already asking.
- You
- Got it. That's on us. We should have told you about the delay earlier.
- Neha
- Okay. So when can you do it?
- You
- I'll get someone on it today, and I'll message you by four with a firm date.
- Neha
- That would help a lot.
- You
- And going forward, let's set up a shared channel for your releases so nothing gets lost.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.