If the only way to know what’s happening is to ask five people, you don’t have alignment. You have oral tradition.
I mean that technically, not as an insult. Oral tradition is a real system — humanity ran on it for most of history. Knowledge held in specific heads, transmitted by proximity and conversation and apprenticeship, kept alive by retelling. It’s a genuine technology.
It’s also the primary knowledge infrastructure of most companies I walk into, and nobody has noticed, because it doesn’t look like a system. It looks like *asking Sarah.*
—
Inventory your own building. How much of your operation exists nowhere but in someone’s head?
The process works because Sarah knows it — Sarah’s been here seven years, and the process has never been written down because it’s never needed to be, because Sarah. The pricing exceptions live in one salesperson’s memory of which clients got which deals and why. The reason the invoice runs on the 12th instead of the 1st is a story only the controller knows. The client’s entire relationship history — the sensitivities, the promises, the near-cancellation two years ago that shapes every renewal conversation — lives in one account manager’s hippocampus, backed up nowhere.
None of this is on any dashboard. All of it is load-bearing. Your company doesn’t run on its documented processes. It runs on a distributed, undocumented, biological database — and the database goes home at five, takes vacations, gets sick, gets recruited.
You met this pattern in Chapter 3 as a person: the employee who became the process. This chapter is the same pattern as *infrastructure* — not one Susan, but the entire layer of your operation that exists only as memory.
—
Here’s what makes oral tradition dangerous, and it’s not that it fails. It’s *when* it fails.
Written systems degrade gradually — a doc goes stale, someone notices, someone patches it. Oral tradition fails catastrophically and all at once, on a schedule set by other people’s life decisions. Somebody resigns, and an entire functional area goes dark overnight. Somebody takes parental leave, and suddenly three people are asking questions nobody can answer. The founder is on a plane, and the company waits — we covered that.
And the two weeks’ notice is not a transition plan. You cannot download seven years of context in ten business days, and everybody knows it, so what actually happens is a frantic, partial oral transfer — folklore passed to an apprentice under deadline — and then the door closes, and the company spends the next year discovering, gap by gap, everything Sarah knew that nobody knew Sarah knew.
The exit interview asks why she’s leaving. Nobody asks what she’s *taking* — because nobody ever mapped what she was holding.
—
The cruelest part: the departure is when leadership finally sees the system. Same rule as everything in Part Three — the invisible thing becomes visible at the moment of maximum price. The absorber’s load appears when they collapse. The shadow system appears when it breaks. And the oral tradition appears in the silence after the goodbye party, when someone asks a routine question and the room realizes, slowly, that the answer just drove away.
Your knowledge infrastructure walks out the door every time anyone does.
The question the next section asks is harder than it sounds: should you even want to fix that — and what do you lose when you do?