The Recovery Conversation:
You’re two weeks from the deadline and you just realized you’re not going to make it. Every manager has been here. The temptation is to push harder.
The harder conversation is telling stakeholders the truth: “We’re not going to hit the date.”
Most managers wait too long to have this conversation. They keep hoping they’ll catch up. They don’t want to look bad. They think maybe, if they just push a little harder, they can close the gap. Here’s the thing: stakeholders can handle bad news. What they can’t handle is surprises. A slip announced two weeks before a deadline is manageable. A slip announced the day of the deadline is a career-damaging event.
You Should Have Seen This Coming
Before we talk about how to have the conversation, we need to talk about why you’re in this position in the first place.
If you’re on a 12-week schedule and the first time you’re raising a flag is week 10, something broke in your process. You should be reporting status every two weeks at a minimum, which gives you six touchpoints. At the very least, you should have had formal check-ins at 25%, 50%, and 75% complete. That’s three opportunities to catch a problem before it becomes a crisis.
Every manager must be a project manager. You need to know what your delivery looks like, and more importantly, whether you’re on schedule.
I know there’s a tendency in the industry to designate some managers as “people-only” managers with no delivery responsibility, just team health and development. I think that’s the wrong model. Very few managers are truly hired without a delivery expectation. Even if your title says “people manager,” there’s still an outcome your company expects: train a team, meet a client commitment, ship a product. The delivery component is always there. You’re just being told it isn’t.
This is where managers get in trouble. They think everything’s fine because the people side is going well. Morale is good, one-on-ones are happening, the team seems engaged. Meanwhile, the delivery is sliding, and nobody upstream knows it. Your stakeholders aren’t worried about whether you’re managing your people. They assume that’s handled. They’re worried about your delivery.
So you need stakeholder management, and more importantly, delivery management as it applies to schedule and percent complete. If you’re not tracking that, you’re setting yourself up to surprise your stakeholders.
The Recovery Conversation Structure
At this point, you’ve already made a mistake. The visibility and importance of the delivery will determine how big a mistake it is. But right now, you’re either trying to salvage your credibility or save your job. Here’s how to structure the conversation.
Lead with the Headline
Don’t bury it. “I need to tell you that we’re going to miss the March 15 deadline.”
The best thing you can do is be transparent about the current status. Don’t try to cover anything up. As soon as you start covering, you’re compounding a lie, and that makes it exponentially easier for someone to justify removing you from the position. If you give your stakeholders a clear picture of the situation, they have a chance to help. They can bring additional resources like more teams, more funding, or stakeholder management. Things you may not have access to or even be aware of. But they can’t do any of that if they don’t know what’s going on.
Own It
It may be that your team dropped the ball. Maybe you just found out. Maybe someone told you something was done and it wasn’t. But fundamentally, your job is to know. You can trust your team, but you have to verify. If you trusted them to get something done and they said it was done and it wasn’t, that’s on you too, because you didn’t verify.
This is the hard part of being a manager. You own all of the delivery. Which is why most managers are not pure people managers.
Explain the Impact
What does this mean for them? For the business? For downstream teams or commitments? Don’t just say “we’re going to be late.” Quantify it. Are you talking about a slip, a miss, or a complete failure? Your stakeholders need to understand the severity so they can calibrate their response.
Present the Plan
If you walk in and say “the whole thing is going to fail” with nothing else, you have two problems. One, you weren’t transparent earlier, so that’s already working against you. Two, you’ve shown up with a problem and no solutions.
You need to bring data about where you are, why you missed, and a plan (or a couple of scenarios) to get back on track. If you don’t have that, the conversation shifts from “how do we fix this” to “are you the right person to manage this.” You’re hired to provide an outcome. That means you need to show up with options for delivering that outcome, even if none of them are ideal.
Ask What You’re Missing
With everything you know, you think you’re going to miss. But maybe that changes with context you don’t have. Your boss or other stakeholders might know something that shifts the picture. Constraints that have changed, priorities that have moved, flexibility you didn’t know existed. Don’t count on it, but ask the question. If the constraints are different than you believe, you might be able to use that to close the gap.
Your fundamental goal is to find ways to win, or to minimize the loss.
The Lesson from Leading Up
I learned this firsthand on a software delivery where I was one of three managers working across the project. As we approached the deadline, I realized my team was going to be about two weeks late. The overall project was looking more like a month behind.
I didn’t wait for someone else to fix it. I gathered everybody, 20 to 40 people across all three teams, into one room, and we went through status every single day. We had a couple of groups that weren’t reporting status accurately, which made it impossible for the full team to coordinate. Statusing everyone together, in one room, at one time, meant nobody could maintain a different version of reality about what was due when.
I wasn’t in charge of the overall delivery. I was in charge of a sub-component. But it didn’t matter if my piece shipped on time and everything else didn’t. The whole delivery was going to fail for our company. So I went to the overall delivery lead, told him what I was doing, told him my projected date, explained why we needed the daily status cadence, and laid out the impact: we were going to be about a month late.
I went in expecting the worst. It turned out to be a manageable conversation. There was some flexibility on the delivery timeline that I didn’t know about. We weren’t in great shape, but it was an acceptable outcome. 30 days late instead of an uncontrolled miss.
Here’s the part that matters: sometimes you have to take the leadership for the entire team if nobody else is going to step up. If you don’t, you’re still going to be part of the failure. You might as well try to correct the delivery and worry about the political fallout later.
I was worried at the time about how the other managers would react. But in reality they didn’t push back. The overall contract lead approved what I was doing, and those teams started reporting in to me. I’m sure their managers didn’t love it, but they didn’t have much to stand on. They weren’t on schedule either, and more importantly, they hadn’t been transparent about it.
The manager who surfaces the problem and brings a plan gets to lead the recovery. The manager who hides the problem gets led.
The Earlier, the Better
The earlier you have this conversation, the more options you have. The longer you wait, the fewer choices remain. Two weeks before a deadline, you still have room to negotiate scope, add resources, or adjust timelines. Two days before? You’re just delivering bad news.
Build the habit of tracking your delivery, reporting status regularly, and flagging risks early. The recovery conversation is important to get right, but the best version of this story is the one where you never need to have it at all.
See you next week!
-Frank
