Before you race off to document everything, I need to defend oral tradition for a minute.
Because here’s what’s true about asking Sarah instead of reading a wiki: it’s *warm.* The answer comes with context, with judgment, with the backstory of why. It comes with a relationship — a little deposit in the trust account between two coworkers. The new hire who learns the process from a person absorbs a hundred things no document carries: the tone, the exceptions, the unwritten rules, the feeling of being welcomed into something. Oral tradition is how a company transmits not just its processes but its *culture*. It creates shared history. It makes a workplace feel like a place.
Companies that run on it aren’t stupid. They’re human. The warmth is real value, and any consultant who tells you to simply replace it with documentation is proposing to fix your fragility by amputating your culture.
So let’s be precise about the actual problem.
—
Warm systems have two properties that matter here: they are rich, and they are rivalrous. One Sarah can only be asked by one person at a time. The knowledge transfers at the speed of conversation, to whoever’s nearby, when she’s available, if she’s not on deadline. Warmth doesn’t scale — that’s not a flaw, it’s a definition. Intimacy is the thing that doesn’t mass-produce.
Which is fine at twelve people. At twelve people, everyone’s within asking distance of everyone, and the warm system *is* the infrastructure — proximity does the work. We covered this in Chapter 2: early companies survive on proximity, and proximity is a workaround that feels like a culture.
Then you grow, and the physics break. Forty people can’t all sit near Sarah. The askers queue. The answers fork — Sarah tells it slightly differently on Tuesday than she did in March, and now two teams run two versions of the truth, warmly delivered. New hires in the second office get the tradition thirdhand, which is to say wrong. The warmth that once covered the whole company now covers a lucky inner ring, and everyone outside it works cold *and* undocumented — the worst of both.
Growth doesn’t kill warm systems. It just shrinks what they can cover, while the company keeps pretending they cover everything.
—
Here’s the mistake both camps make — the culture romantics and the documentation zealots alike: treating warm and scalable as enemies, as if you must pick one.
The companies that get this right run both, deliberately, and assign them different jobs.
The scalable layer holds what must be *reliable*: the process itself, the definitions, the payloads, the answers that need to be identical no matter who asks or when. This is infrastructure. It works at 3am, in the second office, during Sarah’s vacation. It never varies and never resents being asked twice.
The warm layer holds what must be *human*: the judgment, the mentoring, the why-behind-the-what, the welcome. Sarah, freed from being a lookup table, becomes what she should have been all along — a teacher. There’s a difference between asking Sarah *what the steps are* (a query that should never have needed a human) and asking Sarah *what she’d do in this weird case* (a conversation that should never be replaced by a document).
The goal was never to make Sarah unnecessary. It was to stop spending her on questions a system could answer, so the company can afford to spend her on questions only she can.
Warmth is too valuable to waste on retrieval.
—
Which brings us to the trap most companies fall into the moment they accept this argument: *fine — we’ll document everything.*
No. That fails too, in its own special way. Next section.