The Story the Structure Is Already Teaching

On the difference between the story we tell and the one our structure is already teaching.

I’m sitting in the boardroom. A colleague says, “we care about everyone’s well-being.” The deadline in question remains unmanageable. Another person raises the same concern in the next two meetings and then, quietly, stops a month later. My team is told to slow down, yet performance continues to be rewarded by urgency.

No one is lying. The values are sincere. The language may even be heartfelt and beautiful. Still, people are learning something from these interactions. It’s not from the words spoken or even written, but from what happens next.

Most people think narrative means the story an organization tells about itself. A brand story. A campaign. The language on a website or in a strategy deck. Narrative, in this sense, lives at the level of words and images. It’s something we craft, polish, and send outward.

For the kind of work this essay series is concerned with, that definition is too small.

The narratives that hold or hinder an organization do not live only in what it says about itself. They live in the underlying logic that connects beliefs to behaviour, behaviour to consequence, and consequence to what people gradually learn to expect. They live in the pattern that keeps happening, even when no one is writing copy.

Narrative, in this sense, is not decorative. It is structural. It can be observed, named, and, with care, changed.

This essay is an attempt to say, more precisely, what we mean by narrative in this work and why it matters to distinguish it from messaging, brand, or content, especially for those responsible for setting direction and making trade-offs at scale.

The story we tell and the one people learn

Imagine an organization that has just come through a strategic refresh. The language is sharper. The visual identity feels more alive. The website finally sounds like the people who work there.

On the surface, the story works. It speaks of care, equity and courage in the face of complexity. It promises transparency, learning, and partnership at a sustainable pace.

A few layers down, something else is still happening. Deadlines remain impossible. Decisions are made in the same rooms. The people closest to the work are still the last to hear about shifts in direction. Teams are encouraged to “push back on urgency” while their performance continues rewarding speed.

No one is lying. The new story is aspirational in the best sense. People mean it when they say it out loud. Aspirational language is not the problem; leaders have to speak into futures that are not fully here yet. The trouble begins when people are asked to inhabit a story the structure cannot yet support, without being honest about the gap or intentional about closing it.

In that gap, something else is taught.

You will be rewarded if you overextend.

Some voices still matter more than others.

Urgency quietly outranks care.

This is narrative in its structural sense. Not the official story. The lived logic that connects belief, behaviour, and consequence. The pattern that, over time, tells people what is actually true here.

And this matters because people feel the mismatch before they can explain it.

When the gap between the story and the structure grows wide, the cost shows up in things leaders already track: disengagement, attrition, reputational drift, and strategies that look good on paper but never fully take in practice.

The language changes.

The pattern continues.

Meaning lives in use

Wittgenstein wrote that the meaning lives in use. Words do not live in a definition on a page. They live in how a word is used, in what follows when we use it. Meaning emerges from the form of life around those words.

Organizations behave the same way.

The meaning of care is not decided by a values statement. Watch what happens when someone says, “I need more time.”

The meaning of equity is not held in a strategy deck. It lives in how opportunity is distributed, how risk is shared, and whose labour is absorbed by the impact of change.

The meaning of “innovation” emerges from where the budget goes, who is promoted, and what is allowed to fail without penalty.

Narrative, in this deeper sense, is the underlying logic that makes these meanings cohere. It is the chain of because and therefore that lives beneath the surface:

We believe this.

Therefore, we prioritize this kind of work.

Therefore, we make these trade-offs under pressure.

Therefore, people experience us this way.

Therefore, they come to believe this about us.

Most organizations never say this chain out loud. Still, people learn it. In habits. In assumptions. In what gets repeated often enough to feel inevitable.

Over time, organizations teach us the distance between what they are willing to promise and what they are willing to build. Narrative shapes structure, and structure shapes narrative. The real question is what the gap is teaching people to believe.

What narrative is not

To make this clearer, it helps to distinguish narrative from its close neighbours.

Messaging is what you say in a particular moment. A campaign. A speech. A website. Messaging can be thoughtful and sincere while still clashing with the deeper logic people experience every day. The right words in the wrong structure produce a particular kind of dissonance, one most people feel before they can name.

Brand is the long arc of associations people carry about you. Trust, tone, aesthetic, reputation. The emotional residue of repeated encounters.

Content is the visible expression: articles, speeches, posts, documents, videos, and decks. It is the visible trace of how you have chosen to express yourself.

Narrative sits beneath all three. It is the logic that makes certain messages believable, and others ring hollow.

If messaging is what you say in a moment, narrative is why it makes sense to say it and whether people can feel that it is true.

Narrative is carried by structure

Because narrative is often mistaken for storytelling, organizations frequently treat it like a surface layer. Something we refine once strategy is set and real decisions have already been made.

But narrative is not laid down on top of structure. It is carried by structure.

It lives in who has the standing to call something off when it’s not ready.

Who is allowed to say, “this doesn’t fit us anymore.”

What gets time on the calendar and what never quite finds a slot.

Which risks are tolerated, and which feel impossible.

What gets escalated, and what is silently absorbed.

Who is believed the first time they say, “this is not working.”

These are structural questions. They are questions of power, incentives, and design.

Change the structure, and the narrative people learn from experience will change, even if the words take time to catch up. Leave the structure untouched, and even the most beautiful language will eventually thin.

This is why the narrative work cannot rest only with communications teams. They can adjust messaging. They can tend the brand. They can steward content. They cannot, on their own, alter the lived logic people encounter every day.

And here is the uncomfortable truth: sometimes the contradiction is not accidental. Organizations occasionally preserve ambiguity because it is useful.

A company may speak sincerely about collaboration while maintaining tightly concentrated decision-making because distributed power is slower. A workplace may celebrate wellbeing while quietly rewarding overextension because exhaustion sustains performance targets.

No villain is required. Only incentives. This is working the system to survive.

Two organizations, one word

Consider two organizations using identical language about partnership.

In the first, partnership means co-design, shared risk, and decisions made with, not for, the people most affected. Budgets allow flexibility. Timelines leave room for listening. Staff are evaluated on how they engage, not only what they deliver.

In the second, partnership mostly means buy-in. Stakeholders are consulted after key decisions are already made. Communication is polished but one-directional. When the pressure rises and time is tight, consultation quietly walks out the door.

Both organizations may sound almost identical in public. The messaging may be equally compelling. The brand appears equally strong.

But the narratives people learn are profoundly different.

In the first, people gradually learn: we move more slowly because we refuse to move without you and are willing to share control.

In the second, they learn: we value partnership provided it does not meaningfully disrupt control.

The difference is not language. It is structure. And over time, structure becomes believable.

Narrative infrastructure

In the last essay, we explored structure as pattern. Here, we can name a more specific shape that the pattern takes:

Narrative infrastructure: the web of structures, habits, routines, incentives, and rituals that make one story easy to live and another hard to sustain.

Executives touch narrative infrastructure every day. It lives in governance (who is in the room for which decisions), in incentives and targets (what gets rewarded or quietly penalized), in resource allocation (what always finds budget and what never quite does), in people systems (who is promoted, protected, or let go), and in rituals (how meetings are run, how bad news is handled, what gets celebrated, what quietly disappears).

Individually, these choices look operational. Together, they teach people what is possible here.

Narrative infrastructure behaves less like policy and more like a riverbed. Water can move differently. But the easiest path is already shaped. Over time, people learn which concerns are worth raising, which ambitions feel welcome, and which stories are likely to be believed.

Narrative infrastructure is not something applied from outside. It is already there, in how you are built. The first move is simply a way of seeing: in our current design, what makes this story believable, and what quietly makes it impossible?

For leaders, this moves narrative out of the realm of “nice to have” and into the realm of governance and risk. It becomes a question about whether the infrastructure you steward can carry the strategy you are asking people to execute.

Narrative can be observed

If narrative is structural, it is not mysterious. It leaves traces.

The person who used to speak in meetings now hangs back. The team delivering heroic work under impossible conditions, jokes quietly about the official story as though it belongs to a separate reality. The leader who truly believes in a new direction finds that every attempt to articulate it gets quietly translated back into old terms.

These are narrative signals. They tell us something about the underlying logic between the official story and lived experience.

Working with narrative rarely starts by rewriting taglines. It starts with listening for the pattern underneath:

When we say this, what happens next?

When someone behaves as if this were true, what do they encounter?

What do people learn to stop asking for?

Which words feel dangerous? Which feel hollow? Which still feel alive?

Over time, answers to these questions reveal the narrative already in effect. Not the one written in strategy documents, but the one people are actually living inside.

For leaders, this kind of listening is not cosmetic. It is one of the few ways to see, with any clarity, how the organization you believe you are leading differs from the organization people experience every day.

What this opens up

To say that narrative is structural is not to say it is fixed. Narratives are continually made and remade through decisions, rituals, incentives, silences, and repeated acts of attention.

The work is not, finally, about telling a better story. It is about whether the structure beneath the story can hold what the story is asking people to believe.

That is a harder question. But also a more useful one.

Because once we understand narrative as carried by structure, we are no longer limited to asking, “how do we write a stronger sentence?” We can begin asking, what would have to become true for this sentence to feel honest?

For leaders, the practical question shifts from “what do we want to say?” to “what are we building that will make this sentence feel true in the day-to-day lives of our people and partners?”

And if the story around you feels strangely detached from lived reality, it may be worth asking:

What narrative is this structure quietly teaching me to believe?

And what would have to change, not in the words but in the way we are built, for a different narrative to be possible?