Every organization of any age carries perhaps six stories. The time the plant flooded. The year the founder refused the contract. What happened to the manager who went around the owner.
They are told to new people in the first month, repeated at intervals for decades, and they operate as the organization’s case law: the specific precedents from which everybody reasons about what this place does.
Why episodes carry more than rules
A rule states a general principle and requires the listener to work out how it applies. A story contains the application, which is what people actually need.
We do not compromise on safety is abstract enough to be reconciled with almost any behaviour. The account of the Friday afternoon when a job was stopped, with a client waiting and a crew already paid, resolves the ambiguity completely. It tells you what the rule costs and that the organization paid it.
Stories are also durable in a way policies are not. They survive rewrites, reorganisations, and the departure of everybody involved, because they are transmitted person to person rather than stored in a document nobody opens.
Selection is not neutral
Which episodes enter circulation is determined by whether they are worth repeating, and that criterion has nothing to do with whether they are representative.
Stories survive when they are dramatic, when they involve somebody senior behaving unusually, and when they resolve a question people actually have. Ordinary competence produces no stories at all. A supervisor who has handled two hundred situations well over eleven years generates nothing repeatable; the one occasion they lost their temper generates something that outlives their career.
This produces a systematic bias. The organization’s own account of itself is assembled from its extremes, and leaders are remembered for their worst two minutes considerably more reliably than for their best decade.
Leadership does not know which ones are circulating
The stories told in a leader’s presence are a curated subset, and they are curated toward the flattering.
The founding story, the recovery, the time the organization did something impressive: these get repeated at gatherings where leadership is present. The story about what happened to the person who raised a concern is told in vehicles and break rooms, and it is doing more work.
Which means a leader can hold a completely inaccurate picture of their organization’s own mythology while being told stories about it constantly. The version they hear is the version that is safe to tell them.
The only reliable way to find out is to ask somebody with several years of tenure a specific question: what story gets told to new people here that I have probably never heard? Asked once, in the right setting, it produces material a survey never will.
A story cannot be planted
Leaders who understand this occasionally attempt to manufacture the material, and the manufactured version is recognised immediately.
An episode that arrives through official channels, framed as an illustration of the organization’s values, has been marked as institutional messaging and is discounted accordingly. Stories acquire authority precisely from having been transmitted informally by people with nothing to gain.
What a leader can do is create the episodes. A story exists because something happened that was worth repeating, and the decision that generates one is nearly always a decision that cost the organization something visible.
Stop the job on the Friday afternoon and the story will circulate without any help. Announce a commitment to safety in a memo and nothing will.
The counter-story problem
Where an unflattering episode is in circulation and is accurate, there is no way to remove it and two ways to make it worse.
Denying it, which everybody who was present knows to be false. Or explaining it, which reads as management and confirms that the organization is more interested in the account than the conduct.
What works is slower and it is the only thing that does: generate a contrary episode. A single instance in which the organization visibly did the opposite, at cost, in circumstances people recognise as comparable.
The old story does not disappear. It acquires a qualifier — that was under the previous arrangement, or that was before the thing with the Nampa job — and the qualifier is what a leader is actually working toward, because it is achievable and outright erasure is not.
In institutions that outlast people
For an organization that intends to persist, stories are one of the few mechanisms that carry a standard across generations of staff, and they are usually left entirely to chance.
A district or a family firm at its third generation is operating on episodes involving people nobody currently employed has met. Those episodes are doing real work, and whether the right ones survived was determined by which of them happened to be repeatable.
Writing them down is the one intervention available. Not as promotional material, which fails, but as an accurate account with the difficulty included: what was actually at stake, what it cost, and who decided. An organization that records its own hard episodes honestly gives a successor something to reason from, which is considerably more than most institutions hand on.
Edited by Patrick J. Wolf, PhD