What happens to company knowledge when an employee leaves?

Every company has a Daniel. The person who has been there for years, who knows which supplier was difficult in 2021, where the signed version of the contract lives, and why the price list has two files with almost the same name.

When Daniel hands in his notice, two things happen. Everyone says "we must get Daniel to write things down", and then everyone is too busy for Daniel to do it properly.

What knowledge actually leaves with an employee?

It is tempting to think that years of knowledge walk out of the door with one person. Most of it does not.

Think about how an experienced person really works. They agree terms with a supplier by email. They save the signed contract to a shared drive. They answer a colleague's question in a chat. They keep a spreadsheet of who to call for what. Almost all of what they know has been written down, somewhere, in the course of ordinary work.

What leaves is the map. Daniel knows that the Northwind contract is under Final › Old, not Final. He knows the email from March is the one that matters. He knows that "Prices_FINAL_v3" is current and "Prices_FINAL_v3_new" is not.

The records stay. The map in his head goes.

What does losing an experienced employee cost?

Replacing an employee is expensive before anyone has opened a single folder, and the searching starts on the first day.

Gallup's estimate counts recruitment, training and the time lost while a new person learns the job. Atlassian's survey of 12,000 knowledge workers shows how much of every working week already goes on looking for information. And when 42 per cent of what someone knows is theirs alone, the searching gets harder the day they leave, because the colleague who could help has gone.

There is rarely a second Daniel to ask.

Knowledge transfer: what does not work

The goodbye email. "The contracts are on the shared drive, some are under Old, which is confusing, sorry." Written in a hurry on the last afternoon, it is out of date within a month.

The handover document. Better, but it covers only what the leaver remembers to write, in the time they have left. The question that matters next spring is rarely in it.

Asking them later. Most leavers are happy to take a call. Few are reachable when you need them, and none should have to be.

How to reduce dependence on one key person

You do not need to wait for someone to resign. Start from what you already have. The leaver's emails, files and chats are the most complete record of what they knew. The task is to make them findable by the people who come next:

1. Keep shared records shared. Agreements, decisions and procedures belong in shared folders and shared mailboxes, not on one person's desktop.
2. Decide what happens to the mailbox. If it matters, give their successor access to it for a set period, rather than deleting it or forwarding it to nobody in particular.
3. Make the records searchable in plain words. A new person should be able to ask "how much notice do we need to cancel the Northwind contract?" and get the answer, with the clause it came from, without knowing which folder to open.

In short

Most of a leaver's knowledge stays behind in your records. What goes is the knowledge of where it is. Keep records in shared places, decide what happens to the mailbox, and make everything searchable for the next person. Then the next Daniel can leave without taking the map with him.