“We tell ourselves stories in order to live.”
— Joan Didion
In the first seconds after a signal claims the room’s attention, the leadership team faces an uncomfortable gap.
The metric has spiked, the complaint has landed, the headline is moving, and no one yet knows what is happening on the ground, yet the pressure to act as if they do is immediate. Calendars compress, Slack lights up, a senior figure walks in and asks what’s going on, and the question carries weight.
To resolve that tension, the group generates a story fast enough to restore causality and calm. Someone offers an explanation that makes sense, and within minutes the room has a narrative. The question no one asks, while it hardens, is whether the story took hold because it was right or because it arrived first.
Name it precisely: the first-story lock, the move by which the earliest plausible explanation for a triggering event becomes the scoring system the institution operates under.
The first story does not stay an explanation. It quietly decides what success will look like, who is blamed if things worsen, where resources flow, and which metrics go green to signal the problem is handled. It selects the questions worth asking and removes the rest, not by deliberate choice but by the gravity of being the first frame that makes sense.
Seal this off from a different and adjacent failure. A story winning because it is socially manageable and easy to brief upward, smoothness over jaggedness, is a separate phenomenon with its own discipline. This failure is purely temporal and political: the first plausible story wins because the room needed closure and could not wait, and once installed it is far harder to dislodge than it should be, regardless of its actual fit with reality.
The mechanism has two compounding forces, and each carries its own fatal pull.
The first is blame gravity. Under ambiguity, a causal story drifts toward the least powerful actor, because blaming them is cheaper than blaming the design, the leadership, or the structure. A warehouse where shipping errors spike lands on careless workers; management adds retraining and supervision; the training metric turns green; and the real cause, poor lighting and a lagging scanner, stays in place. The room won on the wrong scoreboard because blame fell where it cost least.
The second is narrative overfit. When a story matches the room’s existing fears with apparent precision, the fit itself becomes the evidence, and the room treats it as verified rather than tested. If a competitor launched a discount tier two days before churn spiked, the story writes itself, and pre-existing anxiety about pricing does the rest. It need not be true to lock in; it need only feel inevitable, which is what coherence produces under time pressure. Blame gravity selects who pays; overfit selects which story is told; both work fastest in the first hour, when the institution wants closure more than accuracy.
The cost is the frame tax: an organisation performing flawless execution against a distorted question.
When the first story is wrong, teams align, activity accelerates, dashboards improve, and the outcome stays untouched, because the system is executing efficiently in the wrong direction. The institution is not failing at execution; it is succeeding at the wrong thing.
Consider a B2B software company that watched churn spike the same week a major rival launched a discount tier. The room connected the dots in under an hour, slashed its own pricing, restructured the offer, and absorbed the margin hit. Three weeks later engineering found the real cause: a routine API update had broken the auto-renewal token for one card processor, and customers were not leaving, their payments were silently failing. The company had restructured its pricing for a problem that did not exist.
The objection is real and must be answered: if every first story must be downgraded to hypothesis and the room must hold open the possibility of revision before acting, the institution cannot move in the crucial early hours of a crisis, and the doctrine produces analysis paralysis when decisive action is needed.
It would, if the doctrine forbade acting on a first story. It does not; it forbids treating one as a verdict. Acting on a hypothesis is permitted and often required, the room must respond before clarity arrives. The failure is the moment the story stops being the working hypothesis and becomes ground truth, after which dissent reads as disloyalty and revision as embarrassment. The discipline is to act on a story you can still revise.
In practice, the move that prevents the lock is small and structural: force the room to state the first story aloud, then immediately downgrade it.
A story said out loud and labelled “this is our current hypothesis, and here is what would force us to revise it” cannot lock in the same way a story absorbed silently can. The labelling is the entire intervention. It changes the social cost of dissent, because dissent is now a structured response to a known claim rather than an attack on the room’s emerging consensus. It changes the burden of proof, because a hypothesis carries a falsifiability requirement that a “settled understanding” does not. And it changes what counts as new evidence: under hypothesis status, surprising data is signal; under settled status, the same data is noise that does not fit the story.
A story that cannot be falsified is no longer analysis; it is recruitment. Every first story should name what would defeat it before the institution commits resources to behaving as if it were true. Without that, the room is not deciding; it is voting on what feels coherent in the first hour.
So before you let the room scale the first plausible explanation into a scoring system, say it out loud, downgrade it, and name what would force you to abandon it.
Treat the first story as a question to be tested, never as a verdict to be defended, and the institution keeps the right to be surprised by reality.
The first story told about a problem quietly becomes the standard by which every later fact is judged; an unexamined opening narrative does not describe the decision, it scores it.
Decision Rule — The First-Story Audit
Before resources scale to fit any first story, force it to earn standing.
- State the story. Articulate the causal narrative aloud and on the record, so it can be tested rather than absorbed.
- Name the assumption. Identify the specific leap of faith the story rests on, the unverified link between the trigger and its proposed cause.
- Name the refutation. Specify one observation that would force the room to revise or abandon the story, and watch for it actively.
If you cannot name what would change your mind, the story is not safe to run as a frame; it is recruitment, and you are about to pay the frame tax.
Treat the first story as a hypothesis with a stated refutation, or you are not analysing, you are committing.

Leave a comment