You've made the decision. Maybe it's a new scheduling system, a reshuffle of who reports to whom, or a move to a different shop. Now you have to tell the team.
You've already run the meeting in your head. You know the reactions you're bracing for: the crossed arms, the long silence, the question you can't answer yet, the good employee who quietly starts looking elsewhere.
So you prepare for pushback. You build the case. You line up the reasons this is the right call.
That preparation is aimed at the wrong problem.
People Don't Resist Change. They Resist Not Knowing.
Most of what looks like resistance in that room isn't opposition to the change itself. It's a reaction to uncertainty.
When you announce a change, every person listening is quietly running the same calculation: What does this mean for me? If the announcement doesn't answer that, they answer it themselves. And people filling in blanks under pressure rarely assume the best. They assume their hours are getting cut, their role is shrinking, or the thing they're good at won't matter anymore.
That's why a well-argued announcement can still go badly. You won the argument for the change. You just didn't remove the guesswork, and the guesswork is what people walk out of the room with.
The announcement isn't the moment to persuade your team. It's the moment to make the change concrete enough that nobody has to guess.
This is the first of the five gaps that stall change: the clarity gap. Most owners think of clarity as something to fix after a change starts slipping. In practice, the announcement is where it's either built or lost.
The Five Questions Everyone in the Room Is Asking
Your team won't ask most of these out loud. They're asking them anyway.
1. What, specifically, is changing? Not "we're improving how we schedule." What will someone actually do differently on Monday? Which form, which system, which step goes away? Vague descriptions sound like you're hiding something, even when you're not.
2. Why now? People can accept a hard change when they understand the problem it solves. What they struggle with is a change that seems to come from nowhere. Name the problem first, in plain terms, before you name the solution.
3. What stays the same? This is the question owners most often skip, and the one that does the most to lower the temperature. When everything feels up for grabs, people assume the worst about all of it. Telling them what isn't changing (their pay, their crew, their customers, their schedule) gives them solid ground while the rest moves.
4. What does this mean for me? The general answer isn't enough. A shop lead and an office manager experience the same change very differently. If you can't answer this for each role, you're not ready to announce, or at least your managers need to be ready to answer it in the conversations that follow.
5. What's still up to us? If the whole change arrives fully built, the team has two options: comply or resist. Some decisions are yours to make, and that's fine. But you can own the what and the why while leaving real room in the how: the rollout order, the workflow details, what gets tested first. People defend what they helped shape. (How to decide how much to involve your team.)
Where Announcements Usually Go Wrong
Even with good answers to those questions, two habits undo a lot of announcements:
Leading with the solution. Opening with the new system instead of the problem it solves makes the change feel like a preference, not a necessity. Problem first, every time.
Treating it as one meeting. The announcement plants the idea. The real questions come two days later, one on one, after people have had time to think. If nobody is ready for those conversations, the break room answers them.
A Quick Check Before You Announce
Before you call the meeting, see if you can do all five of these:
Explain what's changing and why in two sentences, without jargon.
Name at least three things that are not changing.
Answer "what does this mean for me?" for every role affected.
Name the one person people should go to with questions. (Here's what happens when that ownership is in name only.)
Say when you'll check back in, and how people can tell you if something isn't working. (Here's why that matters more than it seems.)
If any of those are hard to answer, that's useful information. It doesn't mean the change is wrong. It means the clarity work isn't done yet, and an announcement made now will create the uncertainty you were trying to avoid.
Get the Message Right Before You Deliver It
A big change announcement is one of the few moments when everyone is paying full attention. It's worth getting right.
If you've got a change coming, bring it to Office Hours. We'll work through the message against the questions your team will actually be asking, so you walk in with answers instead of hoping nobody asks.
Not sure whether your team has room for another change right now? The Change Readiness Assessment takes a few minutes and shows where things stand.