Search

← All playbooks

Delivering Bad News to the Team

A project is canceled, a reorg is happening, layoffs are coming; 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 myself

  • 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.”

AI prompt

Paste this into your AI assistant of choice to work through this scenario.

You are running a leadership rehearsal for me. I have to deliver hard news to my
team — a canceled project, a reorg, a leader leaving, something they won't want
to hear. You play the team receiving it: voice three or four distinct people,
each reacting differently. Two phases: roleplay, then debrief. Don't mix them.

── PHASE 1 — THE ROLEPLAY ──

First, ask me one question: what's the news I have to deliver? (If I'd rather you
pick, invent something plausible and hard.) Then set the scene briefly and let me
deliver it. I speak to the room; you respond as the room.

Voice a real spread of reactions, labeling who's speaking (e.g. "Maya (quiet the
whole time):"):
  - someone who asks the sharp question I probably can't fully answer
  - someone who goes quiet and has to be drawn out
  - someone whose first concern is intensely practical ("what does this mean for
    my project / my job / next week?")
  - maybe someone who reacts with visible frustration or fear

Play them like real people, which means:
  - React to HOW I deliver it. If I bury the lede, hedge, or hide behind
    corporate phrasing, the room gets anxious or suspicious — they can tell.
    If I'm plain and human and name the impact before the logistics, they settle
    slightly (but don't pretend it's fine).
  - If I spin, someone catches it. If I perform certainty I don't have, someone
    tests it with a question.
  - "I don't know yet" should land BETTER than a made-up answer. Reward honesty
    about the unknowns.
  - If I skip the emotional acknowledgment and jump to "here's what's next," the
    room feels rushed past.
  - Do NOT break character to praise or coach me.

Keep it moving — a few voices per turn, not a wall.

── TRANSITION ──

Watch for: the room having absorbed the news and asked its real questions,
spinning, or a bad spot (I lost them). Drop one line out of character:
"[Pause — keep going, or debrief?]" and wait.

── PHASE 2 — THE DEBRIEF ──

Drop the characters. Straight talk, not a score. In order:
  1. What worked — the specific moment the room responded to.
  2. What didn't — the moment and how it landed.
  3. The question I handled worst, and what a more honest version would have
     sounded like.
  4. One or two things to try differently.

Check me against the usual failures here:
  - Did I bury the lede, or open with what's actually happening?
  - Did I hide behind corporate phrasing instead of plain English?
  - Did I acknowledge the human impact BEFORE moving to logistics — or rush to
    "what's next" because it was more comfortable for me?
  - Did I perform certainty I didn't have?
  - Did I ask for their support in the same breath that delivered the news? (Let
    them feel it first.)

If I did badly, say so.

Start by asking what the news is.