The announcement came on a Tuesday morning, delivered in a carefully crafted email from the Chief People Officer.
It had all the right language. The word “transformation” appeared four times. The phrase “organizational excellence” appeared twice. There was a reference to “our shared values” and a statement about how “every voice matters in this journey.” The email included a timeline, a steering committee roster, and a QR code linking to the new change management portal.
By noon, the replies from the executive team had been uniformly enthusiastic.
By lunch, the hallways told a different story.
“Here we go again.”
“They announced something like this eighteen months ago. Nothing changed.”
“I wonder how long before they bring in the consultants.”
“I’ll believe it when I see it.”
No one said these things in writing. No one said them to leadership. But they were said — consistently, across departments, across tenure levels, across job titles. And they were not cynicism for its own sake. They were evidence-based assessments, grounded in the organization’s own history.
The change initiative was eighteen hours old, and it had already failed.
The Architecture of Organizational Skepticism
When change initiatives fail, leaders tend to look for answers in the usual places: inadequate resources, unclear strategy, insufficient change management training, misalignment at the middle-manager level.
These diagnoses are not wrong. They describe real obstacles that derail real change efforts, and addressing them matters.
But they miss the deeper issue — the one that operates beneath strategy and structure, the one that shapes how any new initiative is received before a single workshop is facilitated or a single behavior change is asked for.
They miss the organizational narrative.
Every organization carries what I think of as a transformation narrative — the accumulated story, held collectively and rarely spoken aloud, about what happens when this organization says it is going to change. This narrative is assembled from history: the initiatives that were announced with fanfare and abandoned without acknowledgment, the culture work that was launched and then quietly deprioritized when the quarter tightened, the leadership commitment that held firm until it became inconvenient.
The transformation narrative is not a policy. It is not in any document. But it is more powerful than any document, because it operates as the interpretive frame through which every new change effort is received.
When a new initiative is announced, people do not evaluate it in a vacuum. They filter it through the transformation narrative. And if that narrative says change doesn’t really happen here, then the most thoughtfully designed initiative in the world will land in a field of quiet resistance before anyone has been asked to change a single behavior.
The Three Sources of Organizational Skepticism
The transformation narrative is built from evidence. Specifically, three kinds.
The first is the fate of previous initiatives. People remember. They remember the customer experience transformation of four years ago, which generated extensive process documentation and then dissipated when the sponsoring executive departed. They remember the DEI initiative from two years back, which produced a task force, a statement, and then a prolonged silence. They remember the last leadership development program, which generated real engagement among the cohort who participated and zero visible change from the executives who approved it from a distance.
Each unfinished initiative is a data point. The accumulation of data points becomes a story: change is announced here, but not sustained. Leadership commitment is performative, not structural. It is safer to wait and see than to invest.
The second source is leadership behavior during change. People watch what leaders do, not what they say. They notice whether the executive sponsor of the new initiative mentions it in the next all-hands meeting, or whether other priorities have crowded it out. They notice whether managers are given real time and reduced workload to implement changes, or whether the new initiative is added on top of existing demands. They notice whether the senior team changes their own behavior first, or whether transformation is positioned as something the organization needs, not something leadership is actively modeling.
The third source is what happens to people who engage authentically. Change initiatives invite people to take risks: to surface problems, to challenge existing processes, to try new behaviors that may not yet feel natural. What happens to the people who take those risks tells a story about whether honest engagement is actually safe. If the person who named the real obstacle in the kickoff workshop was quietly sidelined in the months that followed, everyone else in that room learned something that no communications strategy will overcome.
What Narrative-Informed Change Management Actually Looks Like
I want to be clear about what I am not arguing. I am not arguing that strategy doesn’t matter, that leadership alignment is unimportant, or that change management infrastructure should be deprioritized. These things matter enormously.
What I am arguing is that these elements will not succeed if the organizational narrative is not addressed directly. You cannot out-structure a story. You cannot out-communicate a belief system that has been built from years of evidence.
What you can do is change the evidence.
In practice, this means the work of narrative-informed change starts before the initiative launches. It starts with what I would describe as an organizational narrative audit — an assessment of the stories currently circulating about what this organization does when it says it is going to change.
That audit is not a survey. It is a qualitative process, often facilitated in small groups and individual conversations, designed to surface the real narrative infrastructure: the specific past initiatives that inform current skepticism, the leadership behaviors that have shaped beliefs about commitment, the trust injuries that need to be directly acknowledged before new trust can be built.
From that audit, change-ready communication looks different. Not the QR code and the steering committee roster. Instead: We have launched change initiatives before that did not succeed. We know what the hallway conversation sounds like. We are asking you to give us the chance to write a different chapter — and we are committing to specific, measurable behaviors that will show you whether we mean it.
That kind of communication does not guarantee success. But it does something the standard launch communication does not: it acknowledges the story already being told. And acknowledging the current story is the only way to begin changing it.
The Accountability Structure That Actually Works
Once the narrative audit has surfaced the current transformation story, the design of accountability takes on new importance. Organizations frequently rely on what I call declarative accountability — the public statement of intention, the values commitment, the steering committee charter. These are useful signals. But they do not hold the transformation narrative accountable because they are too easy to produce and too easy to forget.
What shifts the narrative is behavioral accountability — the specific, visible, recurring evidence that leadership is doing what it said it would do. This means: the executive sponsor mentions the initiative in the next all-hands, and the one after that, and the one after that. The senior team adjusts its own meeting norms before asking middle managers to adjust theirs. The leader who encounters a difficult truth from the change process thanks the person who surfaced it, publicly and specifically. The initiative is given real resources and real protection — not the best language and the tightest timeline.
None of this is complicated. All of it is uncomfortable, because it requires sustained commitment under competing pressures rather than the burst of energy that characterizes a launch.
But the transformation narrative does not update from a launch. It updates from what happens after the launch, and after that, and after that. Every instance of sustained commitment adds evidence to the story. Every dropped commitment adds evidence to a different one.
The teams watching are patient, meticulous accountants.
The Question Worth Asking Before You Launch
There is a question I now ask every organizational leader before a major change initiative goes public.
What is the story your people are currently carrying about how change works here?
Not what you hope they carry. Not what the engagement survey suggested. What does the median member of your organization, thinking honestly, believe about whether this place actually changes?
If the answer is: they believe we mean it, that change takes hold here, that leadership follows through — then your initiative has a foundation to build on. The work is still hard. But the narrative is on your side.
If the answer is: they’ve seen this before, they’re waiting to see if this is real, they’re cautiously going through the motions — then the most important work is not designing the initiative. It is rewriting the transformation narrative first.
That work is slower. It requires leaders to acknowledge what has not worked, to own the pattern without defensiveness, to make promises that are specific and observable enough to be held accountable. It requires something that most organizations, in their urgency to move forward, are reluctant to do: pause, name the history, and ask for the chance to write a different story before asking for investment in a new one.
It is also, in my experience, the only thing that works.
