Leading With Storytelling
Storytelling Isn’t the Problem. What It Hides and What It Bends Is.
Storytelling has become the leadership skill of the moment. Every keynote celebrates it, every platform rewards it, and every manager is encouraged to become a narrative architect. The enthusiasm is understandable – a good story travels, sticks, and moves people in a way a framework rarely does.
But there’s a quiet failure inside the trend, and it’s worth naming precisely, because the usual critique gets it wrong. The problem isn’t storytelling.
Narrative is one of the most powerful instruments a leader has for carrying a complex understanding into other people’s heads. Used well, a story is how a sophisticated model becomes shared.
The problem is two things narrative does when it’s left to do the work alone: it can hide the absence of a real model, and, more insidiously, it can quietly bend an accurate model into a false shape. The first is a failure of honesty. The second is a failure built into the form itself, and it’s the one almost nobody names.
The first failure: the story with nothing behind it
Picture two leaders giving the same compelling talk. The first has a genuine grasp of the system: The interdependencies, the constraints, the trade-offs, and is using a story to make that grasp transmissible, because a room can’t absorb a systems diagram, but it can absorb a narrative that carries the same logic.
The second has no underlying model at all and is using the story to manufacture the feeling of understanding in its absence.
From the audience, these are indistinguishable. Both are clear, both land, both get applause. That’s the problem: the organisation has no way to tell the leader who understands the system from the leader who has merely learned to sound as though they do.
And when the two look identical from the outside, the system stops rewarding the harder of them, because why pay the cost of building a real model when a well-told story produces the same applause for a fraction of the effort?
This isn’t a moral failing in a generation of leaders. They drift toward narrative-as-substitute because the architecture rewards it: visibility and promotion go to the compelling communicator, and the organisation rarely has any mechanism that distinguishes a story backed by a model from a story covering for the lack of one.
The incentive points one way.
Fix the leaders, and nothing changes; the next cohort reads the same incentives and makes the same trade.
The second failure: the form itself bends the truth
The deeper problem survives even when the leader is completely honest, when there is a real model behind the story. Because narrative is not a neutral container. It has a fixed shape, and it forces whatever you pour into it to take that shape.
A story needs a protagonist. It needs causes that lead to effects in sequence. It needs a beginning, a tension, and a resolution.
Real systems have none of these. They have feedback loops with no starting point, outcomes produced by structural forces rather than by any single actor, contradictory truths that hold at once, and situations that never resolve so much as shift into the next configuration.
The moment you narrate a system, you have deformed it: you’ve imposed linear causality on something nonlinear, and, this is the dangerous part, you’ve assigned agency where there were only forces.
This is why the character explanation is the default in almost every organisation, and why the architectural one is so hard to hold. Narrative can only see heroes and villains. Tell the story of a turnaround, and it comes out as “Sarah drove the change” because a story structurally requires a Sarah, someone who did it. But the honest systemic account is that the architecture shifted: the incentives changed, the decision rights moved, the constraints relaxed, and the behaviour followed.
There was no protagonist; there was a field of forces. The story didn’t just simplify that truth. It relocated the cause, from the system to a person, which is the precise error that misleads organisations into trying to fix performance by changing people instead of changing the structure.
So the danger isn’t only the empty story. It’s that the story-form, even in honest hands, quietly converts an architectural model into a character one, on the way out of the leader’s mouth. The leader may understand that the result was structural. The narrative will still hand the audience a hero, and the audience will remember the hero.
And the next time the organisation faces the problem, it will go looking for another Sarah instead of asking what the architecture is producing.
Why this matters more than it seems
Stack the two failures, and the cost is steep.
Decisions are being made on the most compelling account rather than the most accurate one.
Dissent gets harder because contradicting a clean narrative feels like spoiling it.
And underneath both, the organisation slowly loses the ability to think in anything but stories, which means it loses the ability to see structure at all, because structure is exactly the part of reality that narrative can’t represent.
A company that understands itself only through stories will reliably misdiagnose itself, because every story it tells will point at a person where it should point at a system.
None of this means strip narrative out and lecture in systems diagrams.
That misreads the problem as badly as the storytelling cult does, and it’s self-defeating, because a leader who can’t make a systemic model transmissible can’t lead with it.
The answer is structural, and it has to address both failures: build a system that can see the model behind the story, and keep narrative in its proper place: As the vehicle that delivers a model already built, never the tool you think with while building it.
The fix: make the model accountable, and build it before you narrate it
If the first failure is that the architecture rewards a story regardless of the model behind it, the fix is to make the model itself accountable.
Decision processes should require the reasoning, not just the recommendation, the trade-offs weighed, the things that would change the leader’s mind, so that a story with nothing behind it has nowhere to hide.
Reward the people whose accounts survive being questioned to the studs, not the ones who simply present well. Build genuine challenge into how decisions get made, so the test of an idea is whether it holds when someone pulls on it, not how it lands in the room.
And if the second failure is that narrative bends a true model toward agency and sequence, the discipline is to build the architectural model first, in its own non-narrative terms – what forces, what incentives, what decision rights, what constraints – and only then wrap it in a story for transmission.
The order is everything. A story told after the systemic analysis is a delivery vehicle.
A story told instead of it pre-loads the character bias before any analysis happens, and the leader ends up believing their own hero.
When the model is built first and explicitly, the story can be checked against it: does this narrative still point at the structure, or has it quietly handed us a protagonist?
That question, asked routinely, is what keeps the telling honest.
The point
Leaders don’t need fewer stories, and they certainly don’t need to be told to “think harder.” That instruction has never once produced a better thinker. They need to work inside a structure that can tell a model-backed story from an empty one, and they need the discipline to build their understanding in architectural terms before they convert it into narrative, because the conversion always tries to smuggle a hero in.
Storytelling is fashionable, and complexity is permanent, but the two were never the real opposition.
The real tension is between narrative and structure, between a form that can only see protagonists and a reality that mostly runs on forces with no face.
A good story and a real systemic model can coexist, but only in that order, and only under a structure that can tell them apart.
Told alone, the story doesn’t just simplify the system.
It hands the system a hero, and the hero is almost always the architecture, wearing a person’s face.