How to deliver bad news at work without burying it

Bad news goes in the first sentence: the thing that happened, and what happens next. Everything you put in front of it reads as stalling, because it is.

Nobody needs this advice for good news. You have never opened a message with four lines of context before announcing that the demo went well. The padding shows up only when the news is bad, and it is there for the writer, not the reader.

Lead with the thing itself

Start with the fact, written the way you would want to receive it. "The launch is moving to March 12. Here is why, and here is what changes" tells the reader in one breath how bad it is and that somebody has hold of it.

The reader's first question is always the same: how bad? Answer it immediately or they will answer it themselves. The silence between "do you have a minute" and the actual news is where people build a worse version than anything you were going to say.

Burying the lede spares nobody. A reader who finds a slipped date halfway down the message goes straight back to the top and rereads everything above it, hunting for what else got softened.

In email, the subject line is part of the first sentence. "Update on the launch" hiding a slip is a bury. "Launch moving to March 12" has done its job before the message is even opened.

Put the size in dates and numbers

Write the size of the problem as a date or a number, never as an adjective. Adjectives ask the reader to guess how bad it is, and readers guess big.

"Slipping" can mean two days or two months. "March 12 instead of February 26" can be planned around. The vague version feels safer because it commits you to nothing, but the follow-up question will demand the number anyway, and by then you have spent two messages looking evasive instead of one looking honest.

When you do not have the number, give the time you will have it. "About forty accounts hit the bug, exact count by Thursday" is a fine sentence even though half of it is an admission. I have made this case for status updates, and it goes double when the news is bad: a problem described in adjectives gives nobody anything to act on.

You only owe them the next step

Bad news can be sent before the fix exists, as long as it carries the next step and a time. "I am reproducing it now and will have a cause by tomorrow" is enough.

"Don't bring me problems, bring me solutions" is advice that sounds like leadership and works like a gag order. People who take it seriously sit on bad news for days while they quietly assemble a fix, and the sitting costs more than the problem. Waiting until you have a solution is the most expensive way to be helpful.

A workable next-step line has the same parts every time:

• What is already moving, even if that is only "I am looking at it now."
• When the reader will hear from you next.
• What you need from them, which can be a decision or nothing at all.

And if the bad news is really a no you have already decided on, write the no plainly and skip the suspense.

Cut the cushions

Cut every line whose only job is to soften what follows. Cushions delay the news and charge it interest.

Each of the usual ones backfires in its own way:

• "Quick heads up" promises something small, so the real size lands as a second surprise.
• "Small issue" is a measurement you have not made yet.
• "Not a big deal, but" argues with the fact that you are writing at all.
• "We need to talk" hands the reader an open evening to fill with guesses, all worse than the truth.

The compliment sandwich belongs in this pile too. Wrapping a miss in two slices of praise mostly damages the praise: from then on, every nice sentence you write gets scanned for the "but", and the reader stops trusting your good news, which is a strange price to pay for one soft landing.

Apologies are their own trap. If the thing is your fault, apologize once, properly, then move to the fix. An apology in every paragraph turns a status update into a request for comfort, and now the person absorbing your bad news is also managing your feelings about it.

Send it the day you know

The right time to send bad news is the day you learn it. Every delay feels like kindness and is actually inventory: waiting until after their big meeting, or until you have "more clarity", quietly converts a thing that happened into a thing you knew and sat on. Only the second one damages you.

Most of the time it should arrive in writing. The facts land exact, and the reader can read the date twice before anyone expects a reaction from them. Calls invert that: the other person hears a number they have never seen and has to react to it on the spot. Offer the call for after they have read it.

For news about a person and their work, the order flips, and the conversation comes first. If the reply comes back hot, that is a different message with its own rules.

Decide the format in advance

If you cannot stop yourself cushioning, stop relying on willpower: decide before you type that the first sentence is the news, the second is the size, and the third is the next step.

I need the rule myself. Partway through building Unvent I redesigned the landing page and threw the whole thing out the next morning, because it was worse than the page it replaced. Even the log entry I wrote about it pauses to note what the redesign fixed before it gets to what was wrong. I was cushioning bad news for an audience of me. The instinct does not care that nobody else will ever read the message, so I stopped asking it for permission and let the format decide.

The dread, for what it is worth, is a bad forecaster. No message I have honestly dreaded sending has landed as badly as the dread promised, and the fear runs ahead of the facts every time. Send it today. Bad news is the one thing in your drafts that does not improve with age.