L&D Guide · Updated July 2026
Every organisation is one resignation letter away from finding out how much of its knowledge only ever lived in one person’s head.
Knowledge management isn’t a new idea, but in 2026 it’s become an urgent one. Teams are leaner, hybrid work has scattered conversations across Slack, email and unrecorded calls, and AI adoption means employees need faster, more reliable access to how things actually get done — not just what the handbook says.
For L&D leaders, knowledge management sits squarely in your lane. This guide covers what it actually means, what it costs you when it’s missing, and a practical framework you can start using this quarter.
What Is Knowledge Management?
Knowledge management is the practice of capturing, organising and sharing the knowledge that lives inside an organisation — so it’s accessible to everyone who needs it, not just the person who happens to hold it.
It’s often confused with “institutional knowledge” or “tribal knowledge” — the informal expertise that builds up in people’s heads over years. Institutional knowledge is the problem. Knowledge management is the solution. Left unmanaged, institutional knowledge looks like this:
Engineering
The senior developer who knows exactly why a piece of code was written the way it was — and nobody else has ever needed to ask.
Client relationships
The account manager who holds years of client context entirely in her head — every preference, every past issue, every “don’t mention X.”
Operations
The warehouse supervisor who can troubleshoot any machine on the floor because he’s been doing it for 20 years — and nobody else has learned how.
Each of these is a single point of failure. Good knowledge management is what turns that individual expertise into an organisational asset.
Why L&D Should Own Knowledge Management
Knowledge management often gets treated as an IT problem (which platform?) or an HR problem (which policy?). In practice, it’s an L&D problem, because L&D already owns the two things it depends on:
Capture. Turning what someone knows into something others can learn from.
Distribution. Getting the right knowledge to the right person at the right moment, in a format they’ll actually use.
Most businesses don’t realise they have a knowledge management problem until it’s too late, because knowledge feels invisible while the person holding it is still around. There’s rarely a trigger to capture it until someone hands in their notice — and by then, a two-week notice period isn’t enough to extract years of expertise.
The Real Cost of Poor Knowledge Management
When a senior person leaves, most organisations think first about the cost of hiring a replacement. The bigger cost is what happens after they’ve gone.
is the average cost of losing an employee earning more than £25,000 a year, across sectors like IT, accounting, legal, media and retail and that’s before you count the knowledge that walks out the door with them.
of that cost is lost productivity, not recruitment fees — the gap between someone leaving and their replacement rebuilding the context and expertise they had.
is the typical time it takes a replacement to reach full productivity without a documented knowledge base to learn from.
of employees report having to recreate files that already existed simply because they couldn’t find them — the knowledge is often there, just buried, outdated, or unsearchable.
And the cost isn’t only financial. Once the “go-to person” is gone, teams reinvent solutions that already existed, new hires ask questions nobody can confidently answer, and morale drops as everyone else absorbs the gap. Because this cost is rarely measured, it’s rarely treated as urgent until it’s a crisis.
The “Bus Factor”: How Exposed Is Your Organisation?
The bus factor is a simple, useful way to think about knowledge risk: it’s the number of people who’d need to leave (or get “hit by a bus”) before your organisation loses knowledge critical to keeping it running.
A low bus factor is a warning sign, not a badge of expertise. Ask yourself, honestly:
If our most experienced person in each team left tomorrow, could someone else do their job within a week?
Is there a single person whose absence would stall a whole process, client relationship, or system?
Could a new hire find the answer to a common question without asking a specific individual?
Action step: run a quick bus-factor audit this month. For every team, list the one or two people whose departure would cause the most disruption, and what specifically they know that nobody else does. That list becomes the starting point for the framework below.
A 5-Step Knowledge Management Framework for L&D
Most organisations start their knowledge management effort by choosing a tool. That’s backwards. Start by identifying where the risk actually is; the tool comes last, not first.
Identify your highest-risk knowledge holders
Use your bus-factor audit to prioritise. Focus first on people most likely to leave, or hardest to replace. You can’t document everything at once so start where the risk is greatest.
Audit what’s actually written down
Map what genuinely exists in a findable, up-to-date form versus what only lives in Slack threads, email chains, or someone’s head. Don’t assume as teams routinely overestimate how much documentation actually exists.
Make capture frictionless
The simpler the process, the more knowledge you’ll get. Ask experts for a short voice note or screen recording rather than a formal document, and capture it at the moment it’s used.
Centralise it in one searchable place
Scattered documentation is almost as bad as none at all. Knowledge should live in a single, structured, searchable repository not five different drives and folders only their creator can navigate.
Assign ownership and review it regularly
Knowledge decays if nobody maintains it. Give each key area an owner, and build a review cadence — quarterly is a reasonable start — into your L&D calendar.
Thirst is built around exactly this: making it as frictionless as possible to capture what your best people know before it walks out the door, and turning it into a living, searchable resource the whole team can use.
See how Thirst helps teams capture knowledge before it’s lost →
5 Signs You Have a Knowledge Management Problem
Exits
Exit interviews are the first time knowledge gets discussed — by which point it’s too late and too surface-level.
Storage
Your shared drive is a graveyard — outdated, duplicated documents nobody trusts enough to use.
Handovers
“Knowledge transfer” only happens occasionally and informally, with no consistent process behind it.
Management
Managers keep answering the same questions, because the answer lives in their head, not somewhere findable.
Onboarding
New hires take longer than expected to become productive, with no living source of truth to learn from.
What It Looks Like When It Actually Works
The difference, day to day, isn’t dramatic. It’s a lot of small things adding up:
Onboarding
New hires get productive faster because answers already exist somewhere findable, instead of living only in someone’s head.
Management
Managers stop answering the same question for the fifth time this month, because it’s written down where people can find it.
Autonomy
Teams act with more confidence, instead of constantly waiting on the one person who “just knows.”
Compounding
The organisation genuinely gets smarter over time, instead of losing knowledge every time someone moves on.
Final Thoughts
Institutional knowledge feels like a good thing until the person holding it walks out the door. Knowledge management is how L&D turns that risk into a genuine asset: a living, searchable knowledge base that gets smarter the longer the organisation runs, instead of resetting every time someone hands in their notice.
Start small. Run the bus-factor audit, pick your two or three highest-risk knowledge holders, and make capturing what they know as frictionless as possible. The system can grow from there.
thirst.io
For more expert insights and tips, check out the Thirst blog.
You might also enjoy
The 70:20:10 Learning & Development Model Explained |
Employee Onboarding Best Practices |
The Best Knowledge Management Tools for Growing Teams
