In the early days, the fact that everything lives in someone’s head feels like an asset. Your team is fast, flexible, intimate. You don’t need documentation because you have people who just know. And there’s something genuinely good about that — the relational density of a small team, the shorthand, the trust.

Then someone leaves.

Or gets sick. Or gets promoted. Or goes on parental leave. And suddenly the thing that felt like tribal knowledge reveals itself for what it actually is: a single point of human failure. The process that lived in Jenna’s head walks out the door with Jenna. The institutional memory that took three years to accumulate disappears in a two-week notice period. The workarounds nobody ever wrote down because everyone ‘just knew’. Well, nobody just knows anymore.

I’ve watched this happen in organizations across sectors. A nonprofit loses its operations director and spends six months trying to reconstruct systems nobody documented. A small business promotes its best employee and watches everything she carried fall to the floor because there’s no one behind her who knows how it worked. A city department loses its longest-tenured administrator to retirement and then spends two years making the same mistakes that person had learned to avoid — because none of what she knew was ever written down.

“It’s not that documentation is the answer to everything. It’s that undocumented processes are processes you have no control over.”

The absence of documentation doesn’t mean the absence of process. It means you have no way to examine it, improve it, teach it, or protect it. It means your organization’s operational knowledge is stored in the most fragile medium available: human memory, which is fallible, temporary, and non-transferable.

There’s a concept I use with clients called process debt: the compounding cost of deferred documentation. Every time you make a decision to just handle something without writing down how or why, you’re taking out a small loan against future organizational capacity. Individually, each decision seems fine. Accumulated over years, you wake up one day and realize your organization is held together entirely by the muscle memory of people who have been there long enough to remember how it all works. When any of those people leave, you don’t just lose an employee. You lose infrastructure.

The instinct in a lot of organizations is to document everything at once, usually in a panic after the first painful departure. That almost never works. The task feels impossible, nobody knows where to start, it all becomes a someday project that never gets done.

The better approach is selective and sequential: figure out what’s actually at risk if it walks out the door, document that first, and build the habit from there. Not everything is worth capturing. Some processes are so simple or so rarely repeated that documentation adds more overhead than it saves. But the processes your organization depends on daily, the ones with real consequence if they’re done wrong or forgotten…those need to live somewhere other than someone’s head.

Your institutional knowledge is an asset. Store it accordingly.