Every company tracks revenue churn. Almost none track knowledge churn.
When a salesperson leaves, you see the revenue risk. You calculate the pipeline at risk, the accounts that need warm introductions, the relationships that need rebuilding. The loss is visible.
When the same salesperson leaves and takes with them six years of institutional knowledge — the objections that actually work, the customers who seem happy but are about to churn, the quirks of each product integration — that loss is invisible. It doesn't show up in a dashboard. It surfaces six months later when someone makes a mistake the departing employee would have caught.
Knowledge churn compounds
The problem with invisible losses is that they compound before you notice them.
The first time a new hire doesn't know something the previous person knew, they make a decision with incomplete information. That decision shapes other decisions. By the time the gap surfaces — a customer complaint, a process failure, a repeated mistake — it's the fourth or fifth consequence of the original loss, and tracing it back is hard.
Organizations that have high employee turnover don't just lose people. They lose the tacit knowledge that makes the documented knowledge useful — the context, the judgment calls, the "in practice it works like this, not like it says in the doc."
What documentation doesn't capture
Documentation captures what someone thought was important enough to write down. It rarely captures the things that feel too obvious to document (but aren't obvious to a new hire), the exceptions that everyone knows but nobody has codified, or the reasoning behind a decision that's now just a rule.
The gap between the written process and the practiced process is where institutional memory lives. It's also where institutional memory is lost.
The capture moment
The most reliable way to preserve institutional knowledge is to capture it at the moment it's exercised — when someone asks a question and a knowledgeable colleague answers it, when a problem gets solved in a Slack thread, when a decision gets made and explained.
Those moments happen every day. The question is whether anything captures them. Most companies don't have a system that does.
When Freddy answers a question in a customer's workspace, that exchange doesn't disappear. It joins a growing record of what the team knows, when they needed it, and how they explained it. The institutional memory that's usually lost when people leave gets captured as a byproduct of the work they do while they're there.
Top comments (0)