Knowledge loss when a senior employee leaves

The day a senior employee leaves there's a checklist that works perfectly: they return the laptop, their access is revoked, they sign the papers, someone organises a farewell lunch. Everything the company gave them is logged and recovered. And for what that person gave the company — years of judgement, of context, of shortcuts — there is no checklist. It leaves with them, silently, and nobody writes the loss down anywhere.

What exactly is lost: tacit knowledge

«Knowledge» sounds abstract, so let's get concrete. What leaves isn't the documents — those stay in their folders — but everything that never got written down:

The judgement. Why we don't touch that process even though it looks improvable. Which supplier delivers and which one promises and then doesn't. When a problem is genuinely urgent and when it can wait until Monday.
The context behind decisions. Why that client has special terms. Why the migration was done that way and not the obvious way. What was tried three years ago and why it failed.
The shortcuts. The way to unblock that piece of admin in half the time. The exact person to ring when something breaks on a Friday.
The map. Who knows what, inside and outside the company. That map isn't drawn anywhere: it was in their head.

A hypothetical example anyone will recognise: six months after a departure, someone asks why a certain supplier is asked for everything in writing and with confirmation. Nobody remembers. The rule gets relaxed. And the problem that prompted it — the one someone solved once, years ago — happens again at full cost, as though it were the first time. Multiply that scene by all the unwritten rules holding your operation up and you'll get a sense of the real size of the hole.

Why nobody measures it

Because the loss doesn't arrive as an invoice. It arrives diffuse and spread out: decisions that take longer, mistakes that repeat, a replacement who needs months to rebuild judgement that already existed. And the accounting records it all backwards: as the newcomer's «learning curve», not as knowledge lost from the person who left. The cost exists, but it falls into someone else's budget, later and under another name. So it never shows up in any report.

I'm not going to invent a figure for what it costs: the numbers doing the rounds are hard to verify, and this argument doesn't need them. Do the sum with your own company, which is the only one that matters. Think of your best person. How many of the day's decisions go through them? How many questions do they answer each week? Where is all of that written down? If they didn't come in tomorrow, what would stop?

And that's the best case, where the departure is planned with notice and there's time for a handover. An unexpected absence gives no warning: from one day to the next, half the operation is left waiting for someone who is no longer there. The vulnerability was never technical; it was memory.

The wiki isn't going to save you

The classic reaction is «we need to document more». A wiki is opened, ten pages are filled in enthusiastically and, three months later, it's out of date and nobody consults it. It isn't a lack of discipline: it's that documenting is a separate job, competing with the real work, and it always loses. And when it finally does get written, what gets written is the obvious part (the steps, the processes) and precisely the valuable part is left out: the judgement, the why, the nuance. That is tacit knowledge, and it isn't lost through negligence: it's lost because nobody knows what to ask to get it out.

The other classic reaction is the exit interview: two hours of handover in the final week, when the person's head is already somewhere else, trying to pour out years of judgement. The four urgent things get noted and everything else is lost. Not because nobody wants to do it well, but because compressing an entire career into one meeting is, quite simply, impossible.

Useful knowledge isn't produced in documentation sessions. It's produced by working: in the quick answer over chat, in the decision explained in a meeting, in the «watch out for this» said in passing.

Capturing it without asking anyone for anything

That's the idea Savia is built on: if knowledge is expressed every day while the team works, the system should capture it there, passively, without asking anyone to fill anything in. Savia detects the valuable information moving through everyday conversations and documents and saves it with author, date and context. When someone asks, it answers citing the source. And when nobody has ever given the answer, it doesn't invent it: it locates the expert, asks them, and that answer is recorded as official knowledge — including for the day that person is no longer there.

You can't stop people leaving. What you can decide is how much they take with them when they do.