The missed deadline
Break bad news early with a recovery plan, or receive it as a lead without blame.
Case study: Green, green, green, red
For four weeks, Suresh in Chennai reported the reporting module as green in every standup. He knew the export feature was behind, but he was sure he'd catch up over the weekend. Two days before the UK client demo, he finally said it wouldn't be ready. The product owner in Manchester had already promised it to her VP. On another team, Lavanya saw the same kind of slip on a Tuesday, three weeks out. She told her product owner that day, with the reason, two options and a new date. The scope was trimmed, the demo went fine, and Lavanya was trusted more, not less.
Takeaway: Bad news gets worse with age. Share it early, with options, and you keep your credibility.
We often say "it will be done" and try to fix things quietly, because admitting a delay feels like failure. Global teams see an early warning as professional. The surprise, not the delay, is what damages trust.
Breaking the news
Goal: Tell Emma early and clearly, give the reason briefly, and leave her with options and a new date she can trust.
Step by step
- Tell early. The day you know, not the day before the deadline.
- Lead with the headline. What's late and by how much, in the first sentence.
- Explain in one line. The reason, without excuses or long stories.
- Bring options. Two choices: trim scope, add help, or move the date.
- Commit to a new date. A realistic date and when you'll update next.
Say this, not that
| Emma, I need to flag something early. The export feature won't be ready for the twelfth. | We are trying our level best, it will be done. | Hope is not a plan. A clear early warning is. |
| The main reason is that the payments API changed last week, and we have to rework the mapping. | One clear reason. No list of excuses. | |
| I see two options. We ship CSV export on the twelfth and PDF a week later, or we move the full feature to the nineteenth. | ||
| My recommendation is the first option, because the client mostly uses CSV. | Bring a recommendation. It shows ownership. | |
| I'll update you every Monday and Thursday until it's done. | I'll let you know if anything changes. | Regular updates rebuild trust. |
Model conversation
- You
- Hi Emma, I need to flag something early. The export feature won't be ready for the twelfth.
- Emma
- Oh no. How late are we talking?
- You
- About a week. The payments API changed last week, so we have to rework the mapping.
- Emma
- Okay. I've already told my VP about the demo, though.
- You
- I understand. I see two options. We demo CSV export on the twelfth and add PDF a week later, or we move the full feature to the nineteenth.
- Emma
- What do you recommend?
- You
- The first one. The client mostly uses CSV, so the demo still lands. I'll update you every Monday and Thursday.
- Emma
- Okay, that works. Thanks for telling me now and not on the eleventh.
Receiving bad news
Goal: Make it safe to bring bad news, focus on recovery, and agree a realistic plan.
Step by step
- Thank them. Reward the early warning, or you'll never get one again.
- Stay calm. Your face and tone in the first ten seconds set the culture.
- Understand. Ask what happened and what's left, without blame.
- Plan the recovery. Options, a decision and a new date together.
- Learn later. Save "why did this happen" for a calm retro.
Say this, not that
| Thanks for telling me early, Siddharth. That really helps. | Why are you telling me only now? | If you punish the messenger, the next message comes late. |
| Okay. Walk me through what's done and what's left. | ||
| Let's focus on recovery first. We can look at the why in the retro. | Who is responsible for this? | Blame now wastes time you need for recovery. |
| What would it take to deliver the core part by Friday? | ||
| Good. I'll tell the client today, and let's check in again on Thursday. |
Model conversation
- Siddharth
- Hi, I'm really sorry, but the notification service won't be ready for Friday.
- You
- Thanks for telling me early, Siddharth. That really helps. Walk me through what's done and what's left.
- Siddharth
- Email is done. Push notifications are stuck because the Firebase keys aren't approved yet.
- You
- Okay. Let's focus on recovery. What would it take to ship email on Friday and push next week?
- Siddharth
- That's doable. I just need the keys by Monday.
- You
- I'll chase the keys with the security team today. Can you write the new plan in the ticket?
- Siddharth
- Yes. And sorry again, I should have flagged the keys earlier.
- You
- No worries. Let's talk about that in the retro. Today, you did the right thing.
Practice it out loud
Reading is half of it. Fluent listens to you say it and scores your clarity, free, in your browser.