
Why do People Stop Believing Announcements?
Many organizations improvise change communication. They know something needs to happen, so they announce it. They know people have questions, so they answer them. They know there's resistance, so they respond to it.
It feels responsive. It feels adaptive. It feels human.
And it costs more than you realize.
The real cost is institutional trust
Every time you improvise change communication, you're making small withdrawals from your organization's trust account.
You announce something before the details are final. People hear one version, then hear corrections later. That feels like backpedaling.
You answer the same question three different ways depending on who asks. People compare notes. That feels like inconsistency.
You provide information when someone escalates, but not proactively. People realize they only get clarity if they push. That feels like information is being withheld.
None of these moments feel catastrophic in isolation. But they compound.
Trust debt accumulates invisibly
The first time you wing a change announcement, people might shrug it off. The second time, they notice a pattern. By the fifth time, they've adjusted their expectations.
They stop believing initial announcements contain complete information. They wait for the "real" story to emerge through informal channels. They assume leadership doesn't have their act together.
This isn't cynicism. It's pattern recognition. Your team is learning what to expect based on what you've delivered historically.
And once that learning is embedded, it's expensive to reverse.
Improvisation creates invisible work
When you don't have a structured approach to change communication, you create work you don't see.
Managers spend hours answering questions that could have been addressed proactively. Teams hold sidebar meetings to decode what leadership "really meant." People escalate issues that should have been clarified upfront.
The coordination tax compounds at scale
Small organizations can sometimes get away with winging it.
But as you scale, improvisation breaks down hard.
Different departments hear different versions. Middle managers fill gaps with their own interpretations. Frontline staff operate on assumptions that leadership doesn't even know exist.
You can't fix this retroactively
Once trust is damaged, you can't just decide to "communicate better" on the next change and expect people to forget the pattern.
They'll wait to see if this time is different and hedge their bets.
That's not unfair. That's rational.
If you want to rebuild institutional trust, you need a system that prevents the breakdowns people have learned to expect. Not just better intentions. A repeatable structure that produces different results.
What a system prevents
A systematic approach to change communication doesn't eliminate uncertainty. It eliminates the patterns that erode trust.
It prevents:
you from announcing before decisions are final
managers from improvising conflicting explanations.
people from feeling blindsided by information gaps you didn't realize existed.
The hidden cost is cumulative
Winging change communication feels low-cost in the moment. No prep work. No planning overhead. Just handle it as it comes.
But you're deferring costs and they accrue interest.
Every improvised announcement makes the next change harder. Every inconsistent answer makes people trust you less.
This is solvable.
You need a system that accounts for how trust erodes and prevents the patterns that cause it.
References & Related Reading:
1) Detert and Burris, "Leadership Behavior and Employee Voice: Is the Door Really Open?" (Academy of Management Journal, 2007): https://journals.aom.org/doi/10.5465/amj.2007.26279183
2) DiFonzo and Bordia, "Rumor, Gossip and Urban Legends" (Diogenes, 2007): https://journals.sagepub.com/doi/10.1177/0392192107073433
If you're running a rollout and want a plan for each stage, The DANCE System gives you 29 tools across five phases, from defining the change to keeping it in place after launch.
Related Blog Posts:
Why does improvising change communication stop working?
Why does the reason for the change keep changing?
