Every organisation has at least one person who is irreplaceable in a way that has nothing to do with their formal role. They know how the system was configured and why. They remember the conversation with the client that changed the scope of the contract. They know which supplier to call when the normal one cannot deliver. They have the relationship with the regulator that makes difficult conversations manageable.
When that person leaves, the organisation does not just lose a role. It loses a body of knowledge that was never written down, never transferred, and may take years to rebuild.
This is the handover problem. It is extremely common, it is almost entirely preventable, and most organisations only address it after they have experienced it.
Why knowledge stays in people's heads
The short answer is that writing things down takes time, and time spent writing things down does not feel as productive as doing the actual work. In most organisations, knowledge capture is not a priority until the moment it is urgently needed, which is usually the day someone hands in their notice.
There is also a subtler dynamic. The people who hold the most critical knowledge are often the most experienced and the most busy. They have developed their expertise over years and much of it is so embedded in how they work that they are not conscious of it as knowledge that needs to be transferred. They just know how things work. It does not occur to them that someone else does not.
The organisations that manage this well do not rely on people's initiative to document what they know. They build knowledge capture into how work is done, so it happens continuously rather than in a panic when someone is about to leave.
What knowledge is actually at risk
Not all knowledge is equally critical or equally hard to replace. The knowledge worth focusing on falls into a few categories.
Process knowledge. How specific tasks actually get done, including the workarounds, the exceptions, and the informal steps that do not appear in the official process documentation. This is the knowledge that is most often undocumented and most disruptive to lose.
Relationship knowledge. Who the important contacts are, how the relationship works, what has been agreed informally, what the other party's preferences and sensitivities are. This kind of knowledge is particularly hard to reconstruct because it lives in interactions rather than documents.
Institutional memory. Why certain decisions were made, what was tried before and did not work, what the history is with a particular client, system or supplier. This context is often the difference between making a good decision and repeating a mistake that was already made and paid for.
System and configuration knowledge. How the technology that runs the business was set up, what the custom configurations are, why certain things were done the way they were. In many organisations this knowledge lives with one or two people who have been there since the system was implemented.
What to do about it
Document processes as they are done, not after.
The most useful process documentation is created by the person doing the work, at the time they are doing it, not retrospectively by someone trying to reconstruct it later. Simple tools, a short video recording, a step-by-step note in a shared document, a checklist, make this practical without being burdensome. The standard to aim for is: could someone with reasonable competence follow this and get the right outcome without needing to ask questions?
Build handover into the offboarding process.
When someone leaves, a structured handover should be a standard part of the offboarding, not an optional extra that gets squeezed into the last week if there is time. A good handover covers the current state of active work, the key relationships and contacts, the knowledge that is not written down anywhere else, and the things the successor will need to know that are not obvious from the role description. Four to six weeks of overlap is better than two. Plan for it.
Identify your critical knowledge holders now.
Do not wait for someone to hand in their notice to find out who the irreplaceable people are. Map the knowledge that is concentrated in specific individuals across the organisation. Ask: if this person left tomorrow with no notice, what would we not know how to do? That question surfaces the risk in a way that makes it actionable before it becomes urgent.
Use mentoring and cross-training deliberately.
The most durable solution to the handover problem is distributing knowledge across the team before it is needed. Pairing experienced people with less experienced ones, giving people exposure to processes and relationships outside their immediate role, and rotating responsibilities where it is practical all reduce the concentration of critical knowledge in single individuals.
The technology piece
Knowledge management tools, from shared wikis to AI-assisted documentation systems, have improved significantly in recent years and are now accessible to businesses of all sizes. The technology is not the hard part. The hard part is the discipline of using it consistently.
The organisations that get the most out of these tools are the ones that have made knowledge capture a cultural expectation rather than an optional activity. The tool matters less than the habit.