The all-hands is over, the slides are sent, the reorg email has landed. The leader feels they have communicated the change. The people on the receiving end feel they have been told something once, in a rush, and are now left to fill the silence with their own worst guesses. That gap, between "I said it" and "they heard, believed, and can act on it", is where most change communication fails, and it is almost always wider than the leader thinks.
The quick version
- You will under-communicate. Kotter's rule of thumb is that leaders under-communicate the change vision by a factor of 10, when you feel you've said it enough, you're at roughly 10% of what people need.
- People process change emotionally first, rationally second. During upheaval they are making sense of a disrupted world, so "what does this mean for me?" outranks the strategy slide every time.
- Deeds out-shout words. Nothing kills a change message faster than a leader whose behaviour contradicts it. Consistency between what you say and what you do is the message.
- Communicate in an order: why now, then what's changing, then what it means for you, then what we need from you, and repeat it through many channels over time, not once.
The idea in depth
Start with the failure that gives the whole topic its urgency. John Kotter's "Leading Change: Why Transformation Efforts Fail" (Harvard Business Review, 1995), later expanded into the book Leading Change, distilled years of watching transformations stall into eight common errors. The fourth is "under-communicating the vision," and his line about it has outlived almost everything else he wrote: leaders under-communicate by a factor of 10. A team crafts a genuinely good change story, holds a single meeting or sends one memo, and considers the message delivered, having used, by Kotter's estimate, a fraction of one percent of the company's annual communication bandwidth on the most important message of the year.
What follows from that is a different default: plan for repetition, not a single announcement. Assume your first telling reaches almost no one in the way you intended. Build the message into every recurring channel you already have, team meetings, one-to-ones, performance reviews, the casual corridor conversation, and keep it there for the life of the change, not the week of the launch. If saying it again feels excessive to you, you are probably approaching the level where it first registers for everyone else.
A fair limitation: the "factor of 10" is a memorable heuristic, not a measured constant, and Kotter's eight-error framework is practitioner wisdom drawn from observation rather than a controlled study. The widely repeated claim that 70% of change efforts fail is similarly contested, it is cited everywhere and traced to firm evidence almost nowhere. Treat both as directional truths that have survived because they match what leaders see, not as laws you can put a decimal point on.
Why people don't hear the strategy: change is a sense-making crisis
The reason one announcement doesn't land isn't that employees are slow. It's that change disrupts the story people use to understand their world. The organisational theorist Karl Weick spent a career on this in Sensemaking in Organizations (1995): people act as if events cohere in an orderly way, and when that order is severely disrupted, Weick's term is a "cosmology episode", they can feel, suddenly, that the universe is no longer rational. In that state, what people need first is not your strategic rationale; it is help rebuilding a coherent story they can stand in.
The practical consequence: lead with meaning before logic. Before the metrics and the operating model, answer the questions people are actually asking themselves, why is this happening now, is the thing I valued still valued, and where do I fit? A change message that opens with synergy targets and skips the human disruption is technically informative and practically inaudible. The listener is too busy steadying their own footing to take in the spreadsheet.
flowchart TD
A(["Change is announced"]) --> B{"Does the person have
a coherent story yet?"}
B -->|"No, disruption,
uncertainty, fear"| C(["They fill the silence
with worst-case guesses"])
C --> D(["Strategy slide
can't be heard"])
B -->|"Yes, meaning first:
why, and what it means for me"| E(["Footing restored"])
E --> F(["Now the plan
can land + stick"])
This is where Chip and Dan Heath's Switch framing earns its place. They argue change has to reach both the rational mind ("the Rider") and the emotional one ("the Elephant"), and that the Elephant is the one that actually moves. Two of their moves translate straight into change communication: shrink the change, make the first step small enough that a frightened team can take it, and find the bright spots, point to where the new way is already working, so the story is "we've started" rather than "brace for impact." The honest caveat: these are accessible distillations of behavioural research, not the primary studies themselves, so use them as a vocabulary for the move, not as the evidence.
The message has an order, and a lot of it is behaviour
Once you accept you'll repeat the message many times, the question becomes what to repeat and in what sequence. A reliable order, drawn straight from the questions a disrupted person is asking: why now (the honest case for change, not a manufactured crisis), what is changing (concretely, including what is not changing, often the most reassuring line you can offer), what it means for you (roles, security, day-to-day), and what we need from you (the small first step). Skip "what it means for you" and people will assume the worst and act on the assumption.
When you feel you've communicated the change enough, you're at about 10% of what people need.
The harder discipline is that much of your communication isn't verbal at all. Kotter's own point, easy to nod at and hard to live, is that deeds are the most powerful form of communication, and nothing undermines change faster than important people behaving inconsistently with the words. If you announce "we're flattening the hierarchy" and then route every decision through the old approval chain, the corridor has already decided the words were noise. So audit your own behaviour as a message. Before you ask the organisation to change, find the one or two visible actions that prove you mean it, and do them where people can see.
A worked example
Take a 200-person services firm, call it Meridian, merging two departments into one. (Illustrative throughout; this is a teaching example, not a real company.) The leadership team does what most do: a town hall, a tidy slide deck titled "One Team, One Future," and a follow-up email. Three weeks later, the new department is quietly seizing up. People have heard the announcement and concluded, in the absence of anything else, that the merger means redundancies and that their own manager is on the way out.
Run it through the lens above and the failure is obvious. The leaders communicated once, started with the strategic logic ("operational efficiencies"), never answered "what does this mean for me?", and, worst of all, the two department heads were visibly still running their old turf separately, so the deeds contradicted the words. The fix isn't a better deck. It's a campaign: the same four-part message (why now / what's changing, including what stays the same / what it means for you / what we need from you) repeated across town halls, team meetings and one-to-ones for the duration; an explicit, early answer on roles and job security; and one unmissable proof of behaviour, the two heads jointly chairing the first combined meeting and publicly making a decision they'd previously have made alone.
flowchart LR A(["Why now
honest case for change"]) --> B(["What's changing
+ what's NOT changing"]) B --> C(["What it means
for YOU: role, security"]) C --> D(["What we need
from you: the small step"]) D -.->|"repeat across many
channels, over time"| A E(["Deeds that match
the words"]) === B
The thing that unblocks Meridian isn't eloquence; it's repetition plus consistency. The message reaches people at the tenth telling, in the channel they trust, backed by leaders whose actions stopped contradicting their slides. That is what "over-communicating" actually buys you, not noise, but a story people can finally stand inside.
Frequently asked questions
What should I say when I don't have the answers yet?
Say that. "Here's what we know, here's what we don't yet, and here's when you'll hear more" is far stronger than silence, because silence is the one thing people reliably fill with their fears. Commit to a cadence, a weekly update even when the update is "no change", so the absence of news stops reading as bad news. Honesty about uncertainty builds more trust than false confidence that later collapses.
Isn't repeating the same message just going to annoy people?
It annoys you long before it reaches them. The leader has lived with the change for weeks or months; the audience is hearing it cold, while distracted, through the filter of their own anxiety. By the time the message feels worn out to the person saying it, it is usually arriving fresh for most of the people who need it. Vary the channel and the framing, not the core message.
How do I handle the resistance and tough questions in the room?
Treat them as information, not insubordination. A sharp question often signals someone engaged enough to challenge the plan, and the way you respond is itself a message everyone is watching. Answer the question you were actually asked, admit the trade-offs the change involves, and never punish the asking, the moment dissent goes underground, you lose your best early-warning system. (For the deeper playbook, see managing resistance & driving adoption.)
Top-down email or face-to-face, which matters more?
Email scales and creates a record; it does not build belief. The meaning-making that change demands happens in conversation, where people can react, ask, and read your tone and body language. Use written channels to inform and to leave a reference, and reserve your scarce face-to-face time for the emotional core of the message and the questions that follow. The most credible channel is usually a person's own manager, so equip managers to carry the message, don't route around them.
How do I know if my communication is actually working?
Stop measuring outputs (emails sent, town halls held) and listen for inputs you didn't author: what are people saying in the corridor, in skip-levels, in the questions they ask? If the rumour you hear back bears no resemblance to the message you sent, the message hasn't landed regardless of how many times you delivered it. Pulse checks and honest manager feedback beat a read-receipt every time.
Related in the Toolkit
Communication is the connective tissue of every change effort, it's how the model in your head (change models like Kotter, ADKAR, Lewin) becomes a story people can act on, and it's the channel through which you turn doubters into participants (managing resistance & driving adoption).
- Change models (Kotter, ADKAR, Lewin), the frameworks that tell you what to communicate at each phase of a change.
- Leading transformation at scale, communication discipline gets exponentially harder across thousands of people and many sites.
- Managing resistance & driving adoption, what to do when clear communication still meets a wall of "no."
- Mobilising stakeholders & coalitions, the people who must carry and echo your message for it to be believed.
- Digital & business transformation, where new tools and ways of working make the "what it means for you" question especially loud.
- Leadership styles & models (situational, servant, transformational, adaptive), your default style shapes how your change messages are received.
- Onboarding & ramp, the same meaning-first communication that helps a new hire orient helps a whole team through change.
- Centralisation vs decentralisation, a structural change that lives or dies on how honestly the "what's changing" is communicated.
Where to go next
- "Leading Change: Why Transformation Efforts Fail", John Kotter, HBR (1995), the source of the eight errors and the "factor of 10" line; the foundational essay on change communication.
- Sensemaking in Organizations, Karl Weick (1995), why people need to rebuild meaning before they can absorb a plan; the theory underneath "lead with the human story."
- "Find the 'Bright Spots' to Generate Change", Dan Heath, SHRM, a practitioner walk-through of the Switch moves (Rider/Elephant, shrink the change, bright spots) you can apply to a change message.
- "John Kotter, The Heart of Change" (YouTube), Kotter on winning hearts as well as minds, the emotional half of change communication most plans neglect.