How to Tell an Executive Bad News in 90 Seconds

"So are we still good for the 30th?"

"Well, it depends a bit what we mean by good. There's a few moving parts."

I was sitting next to the engineer who said that. He had ninety seconds of an executive's attention and he spent the first twenty of them building a runway. By second forty the executive had stopped listening and started deciding, and what she decided was that this project needed closer supervision.

Here's what you think the preamble does. You think it softens the blow, sets context, and stops the reaction being disproportionate. You're managing the temperature of the room.

Here's what it actually does. Senior people sit through bad news for a living. They have a highly tuned sense for someone circling a thing they don't want to say, because they've watched a hundred people do it, and the pattern reads as one of two things: either you don't know what's going on, or you do and you're hoping not to have to tell them. Both answers make them want more control over your project, not less.

The counterintuitive bit, and the thing nobody tells you before your first steering committee, is that the fastest way to keep your autonomy is to deliver bad news faster and flatter than feels comfortable. A leader who opens with "we're going to miss the 30th by three weeks, here's what I want to do about it" is a leader who is clearly still driving. The dread you feel in the half second before that sentence is the entire price. It's cheaper than the alternative, which is six months of being asked for line by line reviews every week by someone who no longer trusts your version of green.

Four parts, in this sequence, and the sequence is the whole technique.

The headline, in one sentence, with a number and a date. "We're going to miss the 30 October go-live. My best estimate is 20 November." No wind-up. Say it before anything else, because until you've said it your listener is doing nothing except waiting to find out how bad it is, and they cannot process anything you say in the meantime.

The impact in their currency, not yours. Not "the vendor's lead time has extended". They don't own lead times. They own the number that they promised somebody else. So: "That pushes us past the change freeze, so we lose the November window and the next slot is 8 January." Now it's a thing they recognise from their own world. Nine times out of ten this is the sentence that determines how the rest of the conversation goes, and nine times out of ten it's the sentence technical leaders skip.

What you've already done. Two lines, maximum. Not a defence, and not a list of how hard everyone worked. Just enough to show the obvious options have been closed off before they suggest them. "We've asked for expedited freight, it saves four days and costs about the same as one site. We've checked whether we can run a partial go-live and we can't, because the payment routing switches over in one hit."

The ask, with a name and a date. You are not there to report weather. You are there because there is a decision, and it usually belongs to them. "I need a call from you by Friday on whether we take the January slot or we spend on contractors to hold November. My recommendation is January, and I'll tell you why in one sentence if you want it."

Ninety seconds. Often less. Then stop talking and let them ask. The silence after the ask is the part everyone fills with nervous elaboration, and elaboration is where credibility goes to die.

Real shape, generic company. A network refresh across 34 hospitals and day clinics for a private hospital group. In week 11 the supplier confirms the second tranche of hardware has slipped from 30 September to 21 October, which lands after eight of the hospitals are booked for cutover.

The version I've heard a hundred times:

"So we've had some news from the supplier, and it's related to the global component situation which is affecting everyone at the moment. The team have done a huge amount of work chasing this. We're exploring a number of options including expedited freight and we're also looking at whether we can re-sequence, although that has knock-on effects for the engineering resource which we'd need to work through. It's probably amber at this stage."

Ninety seconds spent, nothing decided, and the listener now has to interrogate you to find out what actually happened.

The version that keeps you in charge of your project:

"Tranche 2 hardware slipped to 21 October. The eight hospitals booked for that window move to November, and the overall completion date holds either way.

The reason that matters to you is the winter freeze: if any of those eight slide past 28 November, they land in the March window and we'd be carrying two sets of kit through the whole of winter.

We've priced expedited freight, it recovers four days and costs about one hospital's worth of install, so it doesn't solve it. Re-sequencing does, and the engineers are available in November.

What I need from you: sign-off on re-sequencing by Friday, and one call to the group operations director so the hospital site directors hear the new dates from their own chain of command rather than from my project team. I'll send you two lines you can forward."

That's under ninety seconds read aloud. Time it if you don't believe me. It contains worse news than the first version and it makes you sound like someone who should be left alone to get on with it.

Surprise. If this is the first they've heard that the supplier was ever a risk, the conversation isn't about the slip, it's about why they're only hearing now. The fix is upstream: flag things as watch items while they're still cheap, in one line, so the bad day is a continuation rather than a reveal.

Spin. "Challenging" instead of "late". "Opportunity to re-baseline" instead of "we're three weeks over". Executives translate this vocabulary in real time and it costs you more than the plain word ever would.

Arriving with a problem and no recommendation. If you genuinely cannot recommend, say what you'd need in order to, and when you'll have it. "I'll have a recommendation Thursday once the engineer availability is confirmed" is a perfectly respectable answer. "What do you want to do?" is not.

Waiting for the steering committee. The committee is a cadence, not a queue. If it's material and the meeting is eleven days away, you send two lines today and you brief the committee on Wednesday. Nobody has ever been criticised for telling someone too early.

Take the worst item on your plate right now, the one you've been half hoping resolves itself, and write its headline sentence. One line, a number, a date.

Read it out loud. If it doesn't make you slightly uncomfortable, it's still hedged, so rewrite it until it does. Then find ten minutes in your sponsor's diary this week and say it first, before anything else, and let them ask the second question.