Why Change Fails at the Story Level

Here is something I have come to believe after fifteen years working at the intersection of executive learning and organizational change: the most powerful force in any transformation is not the strategy, the sponsor, or the communication plan. It is the set of stories people already carry about who they are, what is possible here, and what happens to those who try to change things.

These stories are rarely written down. They circulate in anecdotes traded over coffee, in the way newcomers are cautioned, in what gets laughter during meetings and what produces silence. American psychologist Jerome Bruner described narrative as a fundamental mode of thought through which humans construct reality, not merely communicate it. In organizations, that construction is constant and largely invisible.

Over years of designing learning and transformation programs for executive teams across industries and continents, I began to notice a pattern. Even carefully designed change efforts were influenced by forces that remained largely unspoken.

The question was not new to me. I had encountered it earlier in my research on collaboration and technology. But it was practice that made its implications impossible to ignore.

The Limits of Storytelling

Organizations have embraced narrative in the past decade, and rightly so. Purpose statements, culture stories, transformation narratives represent genuine progress in how leaders think about meaning. Change management has followed this shift, emphasizing the importance of crafting a compelling story and cascading it throughout the organization.

But the limitation is directional. Storytelling moves outward. We craft a message and deliver it. But the stories that actually block change move in the opposite direction. They are already present, deeply rooted, shaping what feels legitimate or possible well before any change initiative begins. When leaders introduce a new story without reading the existing ones, they often create dissonance rather than alignment.

Karl Weick’s research on sensemaking showed that people do not first experience events and then interpret them; they perceive through the stories they already hold. David Boje took this further, arguing that organizations are not single-story systems but “polyphonic” environments where competing narratives coexist, often in contradiction (Boje, 2001).

When a team quietly believes that ambition leads to punishment because a previous leader was publicly removed or an early risk-taker was made an example of, no inspirational communication will override that belief. Or consider a merger where two organizations appear complementary on paper but inhabit different narrative worlds. One carries stories of speed and entrepreneurship; the other stories of rigor and reliability. In integration meetings, people use the same words yet mean different things. These are not simply cultural differences. They are different stories about what good work looks like and what kind of organization deserves loyalty. In both cases, the story has to be surfaced and understood on its own terms before anything can shift.

Narrative Intelligence: Working With Stories as Infrastructure

This realization led me to the concept of narrative intelligence and eventually to founding Alif, a studio dedicated to narrative intelligence in organizations.

Narrative intelligence is the capacity to perceive, interpret, and work with the stories that shape how an organization understands itself. It differs from storytelling in the way a structural audit differs from interior decoration. Storytelling asks: what story should we tell? Narrative intelligence asks: what stories are already here, and what are they doing?

At Alif, we have developed a working framework around four moves that we return to in every engagement. I want to share them here because I believe they offer change practitioners a layer of perception that is largely absent from our field — and that can make the difference between change that takes hold and change that slides off.

Seeing is the first move: learning to notice the dominant stories (the ones repeated and rewarded), the marginal stories (held by those with less voice), and the missing stories (the experiences nobody names).

Think of a technology firm that celebrates innovation publicly, but among its engineers, the real operating narrative may be quite different: don’t be the one who breaks production. The gap between the official narrative and the lived one often matters more than either alone.

Understanding goes deeper. It means decoding why a narrative persists and what function it serves even when it appears dysfunctional. A healthcare organization may uphold the narrative of always putting patients first. On the surface, it expresses care. In practice, it can become untouchable. It justifies unsustainable work hours and makes raising concerns about staff wellbeing feel morally suspect. In narrative therapy, Michael White and David Epston describe “problem-saturated stories,” narratives so dominant they foreclose alternatives. In organizations, this often appears as a virtue pushed so far it becomes unquestionable.

Reworking is not about replacing one story with another, which rarely holds, but expanding the narrative space. A financial services firm might pride itself on the idea that “we eat our own,” a marker of resilience and independence. Reworking would not mean rejecting it, but naming both what it has given (resilience, fierce independence) and what it costs.  If earlier stories of mentorship can be recovered from the organization’s own history, new ground opens. Over time, a richer narrative might take hold: we are tough and we take care of each other. The old story was not erased but woven into something with more room in it.

Translating is where narrative insight meets organizational reality. Awareness alone changes little. An engineering team might adopt the language of psychological safety, but the words remain aspirational until they are translated into practice: redesigned code reviews, a shift in vocabulary from “failures” to “learning moments,” shared documentation of things that went wrong, and a commitment to never terminate someone for a first honest mistake. Narratives become real when decisions, rituals, and artifacts carry them forward.

A Different Starting Point

None of this replaces what change management already knows. Stakeholder mapping, sponsor alignment, and communication planning remain essential. What narrative intelligence offers is an additional layer of perception.

The practical shift is in the questions we learn to ask. Before designing the change story, we might first explore: what stories already circulate here? What do they protect, and what do they foreclose? Where do official narratives and lived experience diverge? Whose stories have been carrying the organization, and whose have been left out?

Organizations are not machines to be reprogrammed. They are communities held together by shared meaning, as Bruner reminded us, lives in narrative. Change management, at its deepest, may be the art of working with those narratives. Not writing over them, but learning to read them first.

References

Boje, D. (2001). Narrative Methods for Organizational and Communication Research. Sage.

Bruner, J. (1991). The Narrative Construction of Reality. Critical Inquiry, 18(1).

Weick, K. (1995). Sensemaking in Organizations. Sage.

White, M. & Epston, D. (1990). Narrative Means to Therapeutic Ends. Norton.