FM-14: Narrative Collapse
A pattern. Everyone still executes. No one can say why it matters anymore.
Justin R. Greenbaum · The Lexicon · July 2026
A division head can recite this year’s strategy, but when a new hire asks why the company chose this path over the alternative, the answer is a slide instead of a reason, because the logic that produced the plan was never written down and the people who held it have moved on. A team lead sees two directives that contradict each other but raises neither, because no shared story is left to say which one wins, so both get worked in parallel until one quietly starves. A finance manager approves a spend the same way it was approved last year, but no one in the room can name the goal it now serves, because the decision runs on precedent and the intent behind it has gone missing. A senior engineer nods through the alignment meeting, agreeing with everything, but walks out unable to tell her own team what changed or why, because the meeting produced consensus without conviction.
None of these people are failing. Each one is executing inside a story that no longer explains itself.
This has a name. It is Narrative Collapse.
Here’s the pattern. The system loses a shared explanatory story for why decisions are made and how actions connect to outcomes. The narrative was treated as an artifact, a deck to be refreshed, rather than infrastructure to be maintained, so as decisions piled up, the causal logic linking intent, tradeoffs, and outcomes stopped being kept current. Work continues, but meaning fragments. People still know what to do; they can no longer say why. Alignment becomes performative, agreement in the room and confusion outside it, and execution persists without conviction. When this shows up, it looks like people not getting the message, so the reflex is to send the message again, louder.
Re-alignment masquerades as diligence. The team that meets weekly to re-sync on priorities is called communicative. The executive who re-launches the strategy with a fresh framework is called a strong communicator. The organization that agrees quickly in every review is called aligned. The signal the system reads is engagement. The condition underneath is a shared story that has come apart, papered over by the motion of restating it.
What Narrative Collapse gets mistaken for is what keeps it alive. This is a communication problem. People just need more clarity. It is change fatigue. The strategy is fine, execution is lagging. We need to re-launch the narrative. Each reading treats the loss of meaning as a messaging gap, so the repair is always more messaging, and more messaging adds noise to a system that already cannot tell signal from restatement. These misreadings are how Narrative Collapse survives contact with the all-hands, the one recurring event meant to restore the shared story and the one most easily spent restating the slide and mistaking agreement for belief.
The pattern recurs and changes costumes. In one company it is a strategy that exists in five versions, one per audience, none of which reconciles with the others. In another, a hospital where every unit executes its protocol and no one can explain how the protocols add up to care. In a third, an agency running so many transformation programs at once that the reason for any single one has dissolved into the noise of all of them.
The conditions are structural, not behavioral. A communications training does not interrupt it; a clearer deck does not restore a logic no one is maintaining. Hiring a stronger storyteller does not interrupt it; a better narrator of a broken story tells a broken story well. Replacing the executive does not interrupt it; the replacement inherits a system that treats the narrative as an artifact and lets the next one decay the same way.
What interrupts it is structural. Re-articulate the original intent, out loud, so the reason the path was chosen is back in the room and not buried in a deck. Name the tradeoffs the strategy actually makes, so people can see what was chosen against. Reduce the strategy to a small set of causal claims that a person can hold without slides. Make the plain-language case for why this and not that, until people can explain the system without the artifact. Where the story has already come apart, the fail-safe is to suspend the change initiatives until narrative coherence is restored, so nothing new is stacked on a foundation no one can explain.
When Narrative Collapse has a name, the options change.
The engineer who agreed without conviction stops calling it alignment and sees a room that produced consensus without meaning. The manager above stops scheduling another re-sync and asks why the story keeps needing to be restated. The executive stops reading fast agreement as alignment and asks whether anyone can explain the strategy without the deck. The board stops accepting a polished narrative as evidence of a shared one and asks whether the people executing it can say why.
Naming does not fix. Naming changes what can be seen. What can be seen is what can be acted on.
If any of this feels familiar, it has a name and a taxonomy.
The canonical definition of FM-14, including its early warning signals, common misdiagnoses, and recovery conditions, is at dripractice.com/fm/fm-14.
A role-specific view of how the same pattern looks from the executive’s seat is at dripractice.com/lens/the-executive.
A five-minute diagnostic that runs entirely on your device and never leaves it is at dripractice.com/diagnose.
Next in The Lexicon: FM-16, Process Inflation. When the shared story is gone, process rushes in to hold things together, and procedure starts standing in for the meaning it replaced. FM-16 is what happens when the workflow becomes the work.
Subscribe to The Lexicon.