Delivering Bad News to the Team

A project is canceled. A reorg is happening. Layoffs are coming. A leader is leaving. Something the team will not want to hear.

In the moment

• Don’t sit on it once I’m allowed to share. Delay erodes trust more than the news itself.
• Tell them in person — or at least synchronously and live — if at all possible.
• Don’t bury the lede. Open with what’s happening, then context.
• Acknowledge the human impact before getting to logistics.
• Be honest about what I don’t know. “I don’t know yet” is a real answer.

In the following days

• Be present. Visible. Reachable. Disappearing after delivering bad news is the worst combination.
• Repeat the message. People will hear different parts of it on different days.
• Field questions individually. Some people will not raise theirs in the room.
• Don’t over-promise about what comes next.

What to watch for in yourself

• Hiding behind corporate phrasing because it feels safer. The team can tell. Say what’s happening in plain English.
• Performing certainty I don’t have.
• Skipping the emotional acknowledgment to get to “what’s next” — because what’s next is more comfortable for me to talk about.

Common traps

• Letting the news leak before I tell them.
• Spinning. The team will detect spin, and trust costs more to rebuild than it cost to maintain.
• Treating the moment as transactional. It isn’t.
• Asking for their support in the same conversation that delivers the news. Let them feel it first.

Sample language

“I want to share something difficult. [The news, plainly stated.] I know that lands hard. Here’s what I know. Here’s what I don’t know yet. Here’s what we’re going to do next.”

“I don’t have an answer to that yet. I’d rather tell you that than make one up.”