Working with others
Share news your team won't like
A simple way to deliver unwelcome news plainly, with the reasons, and with room for questions
Tell your team the news plainly and early, explain why as far as you can, and leave real time for questions.
- 20 minutes
- You and your team
- Whenever it comes up
- Conversation
Why this can work
Many people find not knowing harder than the news itself. Saying it plainly, with the reasons, treats your team like the capable adults they are.
Read moreHow to deliver bad news to your team
You’ll come away with the news delivered once and clearly, and your team's real questions out in the open.
- Find out the why.
Before you tell anyone, ask whoever decided why, and what's still open. If you can't explain the reason, your team will invent one, and theirs will usually be worse.
You“Before I tell the team, can you help me understand why this was decided, and what's still open to change?” - Write your first two sentences.
The news, and the one-line reason, said in the first minute before any background. People can't take in context while they're waiting to hear what happened. For example: the Denver project is paused from next month, because the company is putting its budget behind the two launches closest to revenue.
- Tell them together, and soon.
In one room or one call, before it leaks, and not late on a Friday if you can help it. Say what it means for them, what you don't know yet, and when you'll know more.
Tip: If it affects one person much more than the rest, tell them privately first.
- Stay for the questions.
Leave at least as much time for questions as for the news. Answer what you can, say plainly when you can't, and write down what you've promised to come back on.
You“I know that's not what you hoped to hear. What questions do you have? I'll answer what I can, and tell you when I can't.” - Follow up in writing the same day.
The news, the reason, and a date for the answers you promised. People who were too surprised to ask anything in the room will read it later.
To: your teamAs we discussed today: the news, in one sentence.
The reason, as I understand it: the why. What it means for us: what changes for the team.
A few questions I promised to come back on: open questions. I'll have answers by date, and my door's open in the meantime.
Swap the highlighted parts for your thing. Works on Slack, in email, or said out loud.
Good times to repeat it: whenever a decision affects your teambefore news would reach them another waywhen a plan they cared about changes
Making it work for you
Every workplace is different. Here’s what to think about before you start, and what might get in the way.
Things to think about
People often go quiet in the room and have their real questions a day or two after. Check in one-to-one over the following week, especially with whoever is most affected.
What might make this harder
You can say you had a different view and that you're committed to making it work, if that's true. Don't pretend to love it; people can tell.
Questions people ask
How do you deliver bad news to your team?
Say the news plainly in the first minute, give the reason as far as you can, say what it means for them, and leave real time for questions. Then put it in writing for anyone who wants to reread it.
Should a manager explain a decision they disagree with?
Yes, as fairly as you can. Give the real reasoning, and if you had a different view, you can say so without undermining the decision.
How early should I tell my team about a change?
As early as you're allowed to and know enough to explain it. Hearing news secondhand tends to do more damage than the news itself.
What if I can't answer my team's questions?
Say so plainly, write the question down, and give a date you'll come back by. Then come back, even if the answer is that you still don't know.
Why this works, and where it comes from
The instinct, when you have news your team won't like, is to soften it: more context, more cushioning, a gentler moment next week. It comes from a good place. What hurts trust is rarely the news itself; it's the gap around it. A rumor heard first, a long preamble, a meeting that ends with nobody sure what actually changed.
The reason matters as much as the news. When you ask why before you announce, you can give your team a real answer, and a real answer, even an unwelcome one, is easier to accept than a decision that seems to come from nowhere. People don't have to agree with a decision to respect it, but they do have to understand it. If you can't get the why, saying so plainly keeps your credibility intact.
There's a pull, especially when you disagree, to side with your team against whoever decided. It feels loyal, and it tends to backfire. It turns the next decision into a fight before it starts, and it quietly tells your team how you'll talk about them. Explaining the other side fairly, even when you'd have chosen differently, is part of leading well.
News that's really about one person, like a role change or a layoff, doesn't belong in a team meeting. That conversation happens privately, usually with HR involved and clear guidance on what you can say. Tell them first, and only then tell the team.
Other simple things to consider
What to do next
More in Working with others
A few minutes that compound
Do it with Truest and it goes on your permanent record, in a Career Vault your employer doesn’t own.
See how Truest worksAlready a member? Log in- A reminder beforePut it on your calendar and Truest reminds you before it starts.
- It comes back if it slipsA missed one comes back around instead of disappearing.
- On your recordWhen it's done, it goes on your record with your priorities and progress.
Read this alongside your role page
Tell Truest what you’re dealing with
We read every one, and we write guides for the things that come up most. Leave your email if you’d like to hear when we do.
An exercise written by Truest, based on our experience. Last updated September 25, 2026. We sell a career membership; where that’s relevant above, we say so.