The Knowledge That Walks Out the Door

 

Date: 16 July 2026
Author: Marta

On institutional memory, silent expertise, and the crisis most organisations don’t notice until it’s too late.

There’s a specific kind of organisational pain that doesn’t show up in any report.

A senior engineer leaves after eleven years. A regional sales director moves on after building a client base from scratch. A trainer who has been running your onboarding programme since before anyone can remember decides to retire. The departure is managed professionally. The handover is done as well as handovers ever are. And then, six months later, things that used to work smoothly start requiring twice the effort - and nobody can quite articulate why.

That’s institutional knowledge leaving the building. And it happens slowly enough that most organisations don’t register it as a crisis until the damage is already significant.

The Problem With What We Can’t Write Down

Knowledge management as a discipline tends to focus on explicit knowledge - the things that can be documented, systematised, and stored. Processes. Procedures. Decision trees. Product manuals. These are important, and most organisations do a reasonable job of capturing them.

What they don’t capture - what is genuinely difficult to capture - is tacit knowledge. The understanding that lives in people’s heads rather than in any document. How to read a particular client. Which technical shortcuts work and which ones create problems downstream. Why a certain approach was tried and abandoned three years ago. The judgment calls that experienced people make in seconds because they’ve seen the situation play out before.

This kind of knowledge doesn’t transfer through documentation. It transfers through proximity - through working alongside someone, watching how they handle situations, asking questions in the moment, absorbing patterns over time. It requires the kind of sustained interaction that formal knowledge management systems are not designed to support.

When the person who carries it leaves, it largely goes with them. What remains is the explicit layer - the documented version, which is always incomplete and usually out of date.

Why It’s Getting Worse

Two forces are making this problem significantly more acute than it was a generation ago.

The first is workforce mobility. Average job tenure has been declining for decades. The assumption that an employee would spend ten or fifteen years in one organisation - accumulating deep institutional knowledge and passing it on to the next generation — no longer describes how most careers work. People move faster, which means knowledge cycles are shorter and the gaps between what an organisation knows and what it has documented are wider.

The second is distribution. When teams were co-located, tacit knowledge transferred through the ambient interactions of shared physical space. New hires absorbed things without trying to - by sitting near experienced colleagues, overhearing conversations, being pulled into situations informally. Distributed work removes this transmission mechanism almost entirely. Remote teams are particularly vulnerable to knowledge loss because the informal channels through which knowledge travels have no equivalent in most digital work environments.

Together, these two forces create a compounding problem: more frequent departures, less effective transmission.

The Handover Illusion

Most organisations respond to knowledge loss with a handover process. The departing employee documents their role, briefs their successor, perhaps does a few weeks of overlap. This feels like the responsible approach, and it’s better than nothing.

But handovers have a fundamental limitation: people can only document what they know they know. Tacit knowledge, by definition, is largely invisible to the person who holds it. Ask an expert to explain how they do something and they’ll give you the explicit version — the describable steps, the articulable principles. What they won’t tell you, because they genuinely don’t know, is the accumulated pattern recognition that makes their explicit knowledge actually work in practice.

This is why successors who receive thorough handovers still spend months figuring out how to operate at the same level as the person they replaced. The documents are complete. The knowledge is not.

The Training Connection

Here’s where this becomes a question of organisational design rather than just HR practice.

The organisations that lose the least knowledge when people leave are not the ones with the best documentation systems. They’re the ones where knowledge transfer is continuous rather than terminal — where learning from experienced colleagues is embedded in how work actually happens, not concentrated in a handover that occurs under time pressure at the worst possible moment.

This requires rethinking what training is for. Not just the formal programmes - the onboarding, the compliance certification, the quarterly upskilling - but the ongoing, informal transmission of how the organisation thinks and operates. That transmission needs infrastructure. It needs environments where experienced and less experienced people interact in ways that allow tacit knowledge to travel.

Immersive virtual environments are particularly well-suited to this kind of knowledge transfer, for a reason that isn’t immediately obvious: they recreate the conditions of shared physical space without requiring physical co-location. A senior specialist in Warsaw and a new hire in Lisbon can work through a complex scenario together in a virtual environment in a way that a video call simply doesn’t support - with the spatial presence, the shared context, and the naturalistic interaction that make tacit knowledge transferable.

This is one of the reasons organisations are using platforms like Alterland not just for formal training programmes but for the ongoing mentoring and knowledge-sharing that used to happen organically in office environments. The loss of physical co-location created a gap. Immersive technology is one of the few tools that actually closes it, rather than working around it.

The Audit Nobody Does

There’s a straightforward question worth asking inside any organisation: where is our critical knowledge concentrated?

Not documented knowledge - knowledge. The understanding that would materially damage the organisation’s ability to operate if it became unavailable tomorrow. The clients who are managed by one relationship. The systems that only two people fully understand. The institutional memory of why certain decisions were made that nobody has thought to explain to anyone who joined in the last three years.

Most organisations have never mapped this. The concentration of critical knowledge in individuals is treated as a feature - the subject matter expert, the key account manager, the indispensable engineer - rather than as the structural risk it actually is.

Running that audit is uncomfortable, because the findings are almost always worse than expected. But the alternative is discovering the answer reactively, in the six months after someone leaves, when the question is no longer theoretical.

A Different Relationship With Expertise

The deeper shift required here is cultural as much as operational.

Organisations that manage knowledge well don’t treat expertise as something that belongs to individuals. They treat it as something that belongs to the organisation - which means building systems to distribute it, infrastructure to transmit it, and habits that make knowledge-sharing a normal part of how work happens rather than a special event that occurs at departure.

That’s a different relationship with what people know and how they’re expected to share it. It requires investment - in time, in tools, in the kind of environments where knowledge actually travels. But the cost of that investment is considerably smaller than the cost of the alternative, which is discovering what you’ve lost after it’s already gone.


 

 

 

The context menu is not allowed on this page.