Every organisation runs on a large amount of knowledge that isn't written down anywhere. How a particular approval really works. Why a customer is handled a certain way. Where the bodies are buried in a legacy system. Most of it lives in people's heads, and when those people leave, retire or move teams, it leaves with them.
This is one of the quietest risks a business carries. It doesn't show up on a balance sheet. It shows up months later, when something breaks and nobody remembers how it was supposed to work.
Why continuity is getting harder
People change jobs more often than they used to. Teams are more distributed. And a lot of institutional memory that once passed on informally, over a desk, in a corridor, now simply doesn't get transferred. The result is that organisations are steadily leaking knowledge they don't even know they had.
The systems you already run can capture more than you think
It's easy to think of the systems you already run, HR, service management, CRM and document stores, as administrative plumbing. But they sit at exactly the points where knowledge continuity can be designed in, if you use them for it. A few examples:
- Structured onboarding and offboarding. A proper offboarding process is a chance to capture what someone knows before they go, the handover notes, the "here's what you need to know" that otherwise never happens.
- Documents and policies in one place. When the current version of how things are done lives in a system rather than a person's inbox, it survives their departure.
- Clear roles and responsibilities. Knowing who does what, and who did what, makes it far easier to pick up the thread when someone moves on.
- Performance and development records that show not just outcomes but how work was approached.
Make capture a by-product, not a project
The trap is treating knowledge continuity as a special initiative, a big documentation drive that everyone dreads and nobody maintains. It works far better when capture is a by-product of processes people already do: joining, changing role, leaving, being reviewed. If the system prompts for the right information at those moments, the knowledge accumulates on its own.
Done well, your systems aren't just recording that a person was here. They help make sure that what they knew stays behind when they aren't.
The questions worth asking
Before reaching for any tool, it helps to understand the shape of the risk. Where is critical knowledge concentrated? Which roles create the biggest dependencies? What actually happens when an experienced person retires, resigns or changes role? Where are the single points of failure, and how well do current handovers really work? This is an emerging area we're actively exploring at TRANSCIM, and it starts with those questions rather than with a product.
Keeping knowledge in the business is part of how we think about transformation and change. If organisational resilience is a concern for you, we'd be glad to talk it through.