How to give a team bad news
Echipa HR 365 · reviewed 2026-09-08 · 5 min read
The rule that matters most is not what you say but the order in which people find out. Whoever is directly affected finds out first and individually; the team hears it from you, not in the corridor; the rest of the company hears it after the team. Any reversal of that order does more damage than the content of the news.
The order, and why it is the first decision
News travels faster than you plan. If five people hear it in a meeting and the sixth, who is directly affected, hears it from one of them, you have lost something that a single conversation will not recover.
Who hears it and when
- Those directly affected — individually, before any general announcement — even if that means five conversations in one morning
- The team — the same day, from you, in a short meeting, not by email
- The rest of the organisation — after the team, in the form agreed with them
- Externally, if applicable — last, and never before your own people
The structure of the announcement to the team
| Part | What it contains | How long |
|---|---|---|
| The news | Straight out, in the first sentence. No preamble and no context first | 15 seconds |
| What it concretely means for them | Who is affected, how, from when. This is where their attention is | 2-3 minutes |
| Why | The real reason, as much as you can say; “I cannot say everything” is acceptable, a false explanation is not | 1-2 minutes |
| What does not change | The part almost always missing, and the one that settles people most | 1 minute |
| What comes next and when | Concrete steps, with dates. If you do not know, say when you will | 2 minutes |
| Questions | No time limit; what you do not know, you note and come back with a date | as long as needed |
The fourth part is the one that gets left out and the one that most changes the reaction. In bad news, people extrapolate: if a project is cancelled, they wonder whether redundancies follow. One sentence explicitly stating what does not change stops half the speculation.
What you do not say
- “It was not my decision.” Even if true, it removes you from the position of being able to do anything.
- “It will be fine.” You do not know, and if it is not, you have spent all your credit.
- “Do not worry.” Worry is the rational response to bad news; denying it amplifies it.
- An explanation you do not believe yourself. It shows, and then the rest of the announcement becomes suspect too.
- Details about individuals, if the news concerns a particular person.
The hardest to observe is the second. The instinct is to reassure, and “it will be fine” is the most available form. The honest alternative — “I do not yet know what this looks like in three months, but I know what we are doing in the next two weeks” — reassures less in the moment and far more over time.
What you do in the following days
The announcement is the beginning, not the end. In the first days afterwards, people process individually and have questions they did not ask in the group. A manager who disappears into meetings straight after the announcement confirms exactly the fears they were trying to calm.
- Be physically available the next day. Presence matters more than what you say.
- Talk individually with those you see as most affected, without making an event of it.
- Come back with the promised answers, on the promised date — even if the answer is “I still do not know”.
- Do not stack another change on top in the first two weeks.
Can I announce by email, if the team is distributed?
A short meeting, even online, is better — because you can answer. Email is for the summary afterwards, with what was said and what comes next.
What if I am not allowed to give the real reason?
Say that you cannot say everything, and why. People accept a declared limit far more easily than an explanation they do not believe — and the second costs you credibility in future too.
What if somebody reacts very badly in the group?
Do not contradict them there. Acknowledge the reaction, say you want to talk separately, and do it the same day. Continuing in the group loses both the conversation and the rest of the team.
Where to start
Before the announcement, write the list of those directly affected and the order in which you will speak to them. It takes five minutes and prevents the one mistake that cannot be repaired.
Then write the sentence about what does not change. If you cannot write one, it is a sign that you do not yet know the limits of the news either — and they are worth clarifying before you speak.
What you prepare beforehand
An hour of preparation is the difference between an announcement that settles people and one that amplifies. Three things, written down rather than merely thought through:
- The sentence with the news, exactly as you will say it. Read aloud once — if it sounds evasive, it is not ready.
- The list of questions they will ask, with an answer for each, including “I do not know, I will find out by Friday”.
- What does not change, in one or two sentences. It is the part nobody prepares and everybody waits for.
The second list proves the most useful. In a difficult announcement, the questions are eighty per cent predictable — and a prepared answer sounds like clarity, an improvised one like hesitation, even when they say the same thing.
When nobody asks anything
Silence after an announcement does not mean acceptance, it means nobody wants to be first. What works: you ask the first question on their behalf — “you are probably wondering whether this means X” — and answer it. From there, the discussion starts.
Team announcements, with read confirmation
The summary reaches everyone, including those who were absent, and you can see who opened it — so nobody hears it in the corridor because they were on leave.
You can create an account in a few minutes and use every module for 7 days, no card required.