Companies in transformation spend enormous amounts of energy on the “what” of change, such as new structures, processes, technologies, and operating models. The consultants who designed it are usually good. The logic is usually sound. The business case is usually solid.
What they almost universally underinvest in is the story of the change.
It is not the announcements or the communications plan with its emails, town halls, and intranet updates. The story, the narrative that helps people understand not just what is changing and why, but where they are in this transition, what’s being asked of them, what they’re being invited toward, and whether it’s worth the difficulty they’re about to experience.
That story is the difference between change that happens and change that sticks.
Why employees resist change (it’s not what you think)
The default explanation for resistance to organizational change is that people dislike change, fear the unknown, or are committed to the status quo.
I think this is mostly wrong. Or at least, it’s too simple.
People resist change when the change narrative doesn’t give them enough to work with. When the story being told about the change doesn’t include them or their concerns, their history, or their specific experience of the current state. When the official story feels disconnected from the reality they’re living. When leadership appears to be asking for trust without offering honesty in return.
Resistance is often a rational response to a story that doesn’t add up. Before you try to overcome resistance with more communication, more data, or more town halls, it’s worth asking: what story are the resisters telling themselves, and is it more honest than the official one?
Often it is. Or at least, it’s filling in gaps that the official story left empty.
What a change narrative needs to do
Communicating change to employees is not fundamentally a messaging challenge. It’s a narrative challenge. The difference is that messaging is about what you say, whereas narrative is about the story you invite people into.
A change narrative, one that actually works, does five things.
It honors the past.
Whatever is changing replaced something that once worked for some people. Treating the old way as simply wrong or outdated alienates everyone who built their identity around it. The change narrative has to acknowledge what was good and explain why the world has changed in ways that now require something different.
It names the real difficulty.
Change is hard. People know this. If your communication consistently underplays the difficulty, if every town hall makes it seem like the transition will be manageable and exciting, people stop trusting it. They know the hard parts exist. If you don’t name them, they assume you’re hiding more.
It explains the why at the level of belief, not logic.
We’re doing this because the market is moving toward X, and if we don’t respond, we’ll lose Y, is logic.
Logic informs. It rarely moves people.
The belief version is: We’ve built something real here, and I’m not willing to watch it become irrelevant because we were too slow to change. That’s why I’m asking you to do something difficult.
Belief moves people. It’s the difference between understanding and commitment.
It gives people a role in the story.
People in a story behave differently from those being acted upon by it. A change narrative that positions employees as active participants, “here’s what we need from you, here’s why your part matters,” creates a different quality of engagement than one that positions them as recipients of a transition. This is not manipulation. It’s respect.
It stays alive over time.
This is the one that most organizations get badly wrong. The change is announced. The narrative is delivered. And then the narrative goes quiet, just as the hard part of the implementation begins. Change narratives need to be sustained; they need to be updated, revisited, and reconnected to daily reality for as long as the change is in progress. This is usually longer than anyone originally projected.
The internal communication strategy that works for change
I’ve seen two broad approaches to internal communication during change, and they produce very different results.
The first is broadcast communication. The leadership team creates the message. It’s refined by HR and communications. It’s delivered through a series of managed channels, such as email, all-hands, and manager cascade. The message is consistent, controlled, and largely one-directional. People receive it. They may or may not believe it.
The second is narrative communication. The leadership team creates the core story and the framework. But then they actively listen to what people are worried about, to what questions aren’t being answered, to which parts of the official story are landing and which parts aren’t. And they adjust. They bring in real stories from people inside the organization who are experiencing the change. They create spaces for honest conversation, not just managed messaging. They let the story be complicated because complicated stories are the ones people trust.
The second approach is harder. It requires leaders to be comfortable with uncertainty and questions they can’t fully answer. But it produces something the first approach rarely does: genuine engagement rather than quiet compliance.
What I tell leaders about change communication
There’s one piece of advice I give to almost every leader navigating a major organizational change: tell the harder version of the story sooner.
Whatever you’re worried about saying because it might create anxiety, say it early, say it with context, say it with your own honest perspective on how you’re thinking about it. People can handle honest complexity. What they can’t handle, and don’t forgive easily, is finding out later that the story was incomplete.
Trust in leadership is built during change. But it’s built through what leaders show people, not just what they tell them. When a leader acknowledges publicly that this is harder than they expected, that’s trust being built. When a leader responds to a question they can’t answer with “I don’t know yet, and here’s what I’m doing to find out,” that’s trust being built.
A change that changes an organization is always a story. The question is whether it’s a story your people will want to be part of, or one they’ll spend the next two years quietly editing themselves out of.
Story It works with HR and leadership teams on the change narrative, such as building the internal communication strategy and the storytelling framework that help organizations navigate transition in ways that build trust rather than erode it. If you’re in the middle of a change and the story isn’t landing, let’s talk.
Discover more from Storyit
Subscribe to get the latest posts sent to your email.
