Telling Your Team Bad News Without Panicking Them or Hiding It
How to deliver bad news to a team plainly and with a next step, drawing on documented practice from Ernest Shackleton, Gene Kranz, and Kim Scott's Radical Candor.
You have known for two days. The deal fell through, or the funding did, or the plan the team has been working toward since spring is being cancelled. You have rehearsed three openings, none of them quite right, and the all-hands is at ten.
What does a team actually need to hear first?
Not your preamble. People who sense bad news are waiting for it, and every sentence before the news is a sentence they spend bracing. The first thing they need is the fact itself.
The second is what it means for them. The third is what happens next. Most delivery problems come from reversing the order: context, reassurance, a hint, and finally the news in a subordinate clause.
Ask an assistant to "help me announce bad news to my team" and you get balanced language with a lot of cushioning. That cushioning is what makes the message unclear. The documented approaches differ on style but agree on this: say the thing, then lead.
How did Shackleton tell men their ship was lost?
The Endurance was crushed by pack ice in the Weddell Sea in 1915. Accounts of the expedition, including Shackleton's own South (1919) and Alfred Lansing's Endurance (1959), describe him telling the crew plainly that the ship was lost and that the party would have to travel across the ice. He did not pretend otherwise, and he did not leave the men with nothing to do. Routines, tasks, and a defined next objective followed quickly.
Applied: After stating the news, give people something concrete: a task, a date, a meeting. Hope based on a plan is more durable than reassurance based on tone. If the situation is truly severe, say so, then say what you are doing about it.
"The news I need to tell my team is: [news]. Draft a 90-second spoken opening that states the news in the first two sentences, says what it means for the team in plain terms, says what is known and unknown, and ends with the next step and the time of the next update. No cushioning phrases, no corporate euphemisms."
Why it works: forcing the fact into the first two sentences removes the buildup that makes people anxious.
What do you do when facts are unclear?
Gene Kranz's Failure Is Not an Option (2000) describes flight controllers in a crisis as separating two jobs: first establish what is actually true, then decide what to do. In his account, speculation was discouraged until the data was solid, and each specialist reported what they knew and what they did not.
Applied: Tell the team the same way. "Here is what we know. Here is what we do not yet know. Here is when I will update you." That structure lets you be honest about uncertainty without looking evasive, and it stops you from announcing conclusions you will have to retract.
"Here is everything I know about the situation: [list]. Sort it into three lists: confirmed facts, things I believe but have not confirmed, and open questions. Then draft a short update that shares only the first list and clearly names the third, with a time for the next update."
Why it works: sorting before speaking keeps guesses from being presented as facts.
What if the kind thing is the unclear thing?
Kim Scott's Radical Candor (2017) describes four quadrants built on two dimensions: care personally and challenge directly. Ruinous empathy, high on care and low on directness, is the instinct to soften until the message disappears. Obnoxious aggression is the opposite, direct but without care.
Bad news tempts managers toward ruinous empathy. "There may be some changes to the roadmap" sounds gentle. It also leaves people unsure whether their project exists.
Applied: Check your draft for hedges. Replace "may" and "potentially" with the real statement. Then add the care: acknowledge the effort, say what you are sorry about, and be present for questions.
"Here is my draft announcement: [paste]. Highlight every hedging phrase, euphemism, or vague word. For each, suggest a plain replacement that states what is true. Then identify where the draft shows care for the people affected and where it could do so more specifically."
Why it works: a hedging audit finds the sentences that make a message kind in tone and unclear in content.
Which approach fits the news you have?
| Approach | From | When it fits | Watch out for |
|---|---|---|---|
| Truth, then a task | Ernest Shackleton, South and accounts such as Lansing's Endurance | The situation is serious and people need direction | Forced cheerfulness that contradicts what people can see |
| Facts before decisions | Gene Kranz, Failure Is Not an Option | The situation is still developing and you lack answers | Using uncertainty as cover for not saying anything |
| Caring and direct | Kim Scott, Radical Candor | The news is clear but you are tempted to soften it | Directness without care, which lands as coldness |
What won't any of this do?
It will not make the news good, and it will not prevent people from being upset. It also cannot tell you whether to announce at all, or what the legal position is when the news involves redundancies, pay, or regulated matters. Employment rules vary by country, so check with HR or counsel first. What these approaches do is make the telling honest, clear, and followed by something to do.
Ernest Shackleton and Gene Kranz are in the Explorer & Adventurer category, and Kim Scott is in People & Culture. For the originals, see South, Failure Is Not an Option, and Radical Candor. To structure a hard conversation you have been putting off, Difficult Feedback is a $49 tool built for it.
All the copy-paste prompts from this guide, and the rest of the Situations series, live at /prompts too, free to copy without reading the guide first.
Frequently asked questions
Should I wait until I have all the answers before telling the team?
Usually not. Waiting lets rumors fill the gap, and people tend to assume the worst. Say what you know, what you do not know, and when you will update them. A team can handle uncertainty that is acknowledged more easily than silence that feels like concealment. Even a short holding message, such as what you know, what you are checking, and when you will update, is better than silence.
How much of my own worry should I show?
Enough to be believable, not enough to hand the team your anxiety. Shackleton's documented leadership shows steadiness as a deliberate choice rather than an absence of fear. Being honest that this is hard, then moving to what happens next, tends to read as strength. Prepare a plain statement of what you feel and what you intend to do, then keep the focus on the team's questions rather than on yourself.
What if the bad news involves layoffs or something with legal implications?
Talk to HR or counsel before you speak, because what you can say and when may be constrained by employment law, contracts, and confidentiality. The principles here still apply to tone and clarity, but they do not replace advice about your obligations, which differ by country. If you are bound by confidentiality, say so honestly rather than inventing reasons, and offer what you can share and when.
What does Kim Scott mean by ruinous empathy in this context?
In Radical Candor, ruinous empathy is caring about people without challenging directly. For bad news it looks like softening the message until nobody quite understands what has happened or what it means for them. The kind-sounding version is often the more harmful one, because people make plans on a picture that is too rosy. Check each sentence by asking what a worried person would take from it, and whether they would know what to do next.
Should I deliver bad news in writing or in person?
For anything that affects people's jobs, pay, or sense of security, in person or live video first, then follow with a written summary. Writing is good for facts and details people will want to reread. It is poor at conveying that you are present and accountable. Allow time for questions in the meeting itself, and offer a way to ask privately for anyone who prefers it.
How do I handle the questions I cannot answer?
Say so, and say when you will have an answer. Kranz's crisis practice separates establishing facts from deciding what to do, which means admitting what is not yet known is part of the process. A dated commitment to come back is worth more than a confident guess you later have to retract. Write down what you promised to find out and who owns each question, so the follow-up happens even if the day gets away from you.
Written by Gareth Hoyle. Last updated 8 October 2026. Part of the authority.md guides library.
More guides.
Apologizing to a Customer When You Got It Wrong
How to write an apology a customer believes, using the Trust Triangle from Frances Frei and Anne Morriss, the Trust Equation from Maister, Green and Galford, and Robert Cialdini's commitment principle used ethically.
Asking for a Raise Without Turning It Into a Standoff
How to run a pay conversation as a problem you and your manager solve together, using three documented negotiation approaches from Fisher and Ury, Chris Voss, and Deepak Malhotra.
Running a Post-Mortem Without Blame That Still Changes Something
How to run a review after a failure that finds real causes without scapegoating anyone or letting accountability disappear, using Amy Edmondson, W. Edwards Deming, and Gene Kranz.