Knowledge Management
Every business runs on two kinds of knowledge. One is written down — in handbooks, wikis, SOPs, and onboarding decks. The other exists only in people’s heads, built up over months and years of doing the job, and it walks out the door the moment someone hands in their notice.
That second kind is institutional knowledge, and most businesses have far more of it — and far less control over it — than they realise. This guide breaks down what institutional knowledge actually is, why it quietly becomes one of the biggest risks a growing business carries, and what a practical, working system for capturing and preserving it looks like.
Institutional knowledge: the short answer
Institutional knowledge is the collective know-how, context, and expertise an organisation accumulates over time — including the parts that were never formally written down.
It covers things like why a process works the way it does, how a long-standing client prefers to be handled, or how to fix a piece of equipment that only one person on the floor really understands.
The risk isn’t having it. The risk is that most of it lives in a small number of heads, with no reliable way to capture, search, or transfer it before those people leave.
- What is institutional knowledge?
- Examples of institutional knowledge in the workplace
- The bus factor: why it’s a hidden risk
- Signs your business has a problem
- The real cost of losing it
- Why institutional knowledge gets lost
- How to capture and preserve it: a 5-step framework
- What good looks like in practice
- FAQs
What is institutional knowledge?
Institutional knowledge — sometimes called organisational knowledge or “tribal knowledge” — is the sum of what a business has learned through experience: its history, its context, its unwritten rules, and the specific expertise its people have built up over time. It’s the difference between a new hire following a generic playbook and a five-year veteran who instinctively knows why the playbook has an exception for one particular client.
Some institutional knowledge is documented — process manuals, decision logs, style guides. But a significant share of it is tacit: it exists as instinct, judgement, and pattern recognition inside specific people’s heads, and it was never written down because nobody had to. It develops naturally, it’s rarely questioned while the person holding it is still around, and it’s genuinely hard to notice until it’s gone.
That’s what makes institutional knowledge different from a standard knowledge base. A wiki page is deliberately created. Institutional knowledge accumulates as a byproduct of people simply doing their jobs well over time — which is exactly why it’s so easy for a business to lose track of how much of it exists, and where.
Examples of institutional knowledge in the workplace
Institutional knowledge shows up in every department, though it rarely gets labelled as such until someone tries — and fails — to replace the person carrying it.
Engineering
A senior developer who knows exactly why a piece of code was written a certain way — context that was never captured in a comment or a commit message.
Account management
An account manager holding years of client history in her head — every preference, every sensitivity, every past issue that isn’t logged anywhere.
Operations
A warehouse supervisor who can troubleshoot any machine on the floor purely from twenty years of hands-on experience, with nothing written down.
Sales
A sales lead who knows, without consulting a script, exactly which objections a certain type of buyer will raise — and how to defuse them.
HR
A People lead who remembers exactly how a similar policy exception was handled two years ago, and why it can’t simply be repeated this time.
Finance
A finance manager who knows which figures in a legacy spreadsheet are safe to trust, and which have a quiet, undocumented workaround baked in.
The bus factor: why institutional knowledge is a hidden risk
There’s a concept in software engineering called the “bus factor” — a blunt way of asking how many people would need to disappear (traditionally, get hit by a bus) before a project or business grinds to a halt. For a lot of small and mid-sized companies, the honest answer is uncomfortably low: one or two.
Institutional knowledge feels like a good thing right up until the point it becomes a single point of failure. Experienced people who know a business inside out are an asset — until the business realises it has no backup for what’s in their head. That’s the paradox: the deeper someone’s expertise, the more valuable they are day-to-day, and often the more dangerous their absence becomes.
A key person leaves and suddenly nobody knows how to do something that used to run without a second thought.
Teams reinvent the wheel on problems that were already solved, because nobody can find the solution or knows it exists.
New hires ask questions nobody can answer confidently, slowing onboarding and eroding trust in the process.
The “go-to person” is gone and there’s no backup — just a queue of people trying to reverse-engineer what they used to just ask.
Signs your business has an institutional knowledge problem
Most businesses don’t realise they have an institutional knowledge problem until it’s already cost them something. Knowledge lives in people’s heads, and things that live in people’s heads don’t show up on a dashboard — there’s no line item for “how much does one person know that nobody else does.” A few warning signs tend to show up well before a crisis does:
The same one or two people are copied into every escalation, regardless of team or topic.
New hires consistently take longer than expected to become fully productive, and can’t say exactly why.
Documentation exists, but people don’t trust it enough to use it without double-checking with someone.
Every time someone senior goes on leave, a handful of decisions quietly stall until they’re back.
The reason these signs get missed is structural, not accidental. Businesses are built to reward output, not the process behind it — nobody gets praised for documenting how they did something, only for the thing itself. And there’s rarely a natural trigger to capture knowledge before it’s urgent: the moment a business most wants someone to write everything down is right after they’ve resigned, by which point a standard notice period isn’t close to enough time to extract years of expertise.
The real cost of losing institutional knowledge
When a senior person leaves, most businesses think about the hiring cost first — recruiter fees, interview time, maybe a signing bonus. That’s the visible cost, and it’s rarely the biggest one.
is the average cost of replacing a single employee earning above £25,000, across sectors including IT, accounting, legal, media, and retail. Roughly 82% of that figure comes from lost productivity — not recruitment spend.
is the typical runway a replacement needs before they’re operating at the level of the person they replaced — a stretch where mistakes are more likely and institutional context is thinnest.
a week is roughly how long knowledge workers spend searching for information or tracking down colleagues who hold it, according to McKinsey’s research into workplace productivity — close to a quarter of the working week.
of employees report having to recreate files that already existed, simply because they couldn’t find them — a direct sign of documentation that exists but isn’t discoverable.
None of these costs show up on an invoice, which is exactly why they’re so easy to underestimate. They’re distributed across dozens of small delays, re-dos, and quiet frustrations rather than one line item — but added up across a year, they’re often larger than the recruitment budget spent trying to prevent them.
Why institutional knowledge gets lost
Ask most leadership teams how much of what makes their best people great is actually written down, and the honest answer is: not much. The bulk of it lives in their heads. What’s left is scattered across Slack threads, email chains, and habits passed on informally between colleagues — and what does exist on paper is often outdated, hard to find, or trusted by no one.
The usual attempts to fix this rarely work, because none of them create a living, searchable system:
Exit interviews — useful for feedback, but they happen too late and stay too surface-level to capture years of context.
Shared drives — often become graveyards of half-finished, outdated documents that nobody fully trusts.
One-off “knowledge transfer” sessions — unstructured, dependent on goodwill, and easily rushed in a departing employee’s final two weeks.
How to capture and preserve institutional knowledge: a 5-step framework
Most organisations start by looking for a tool. That’s the wrong first step. The right starting point is understanding where the knowledge gaps actually are — then building a system, not a one-off project, around closing them.
Map where the risk actually sits
Identify the roles and individuals whose knowledge would be hardest to replace if they left tomorrow. This is rarely limited to the most senior titles — it’s often whoever has been in a role longest, or whoever quietly fields the most questions.
Prioritise your highest-risk people first
Don’t try to document everything at once. Start with whoever is hardest to replace or most likely to move on, and work outward from there.
Make contribution as low-friction as possible
The simpler the capture process, the more knowledge you’ll actually get. If contributing feels like a chore on top of someone’s real job, it won’t happen consistently — regardless of how often it’s requested.
Build a single, searchable home for it
Scattered Slack messages and shared drives don’t count as documentation people can rely on. Knowledge needs to live somewhere structured, current, and genuinely easy to search — not just technically “written down” somewhere.
Treat it as ongoing, not a one-off project
Institutional knowledge is created continuously, as people do their jobs. Capturing it needs to be a habit built into everyday work, not a scramble that only happens when someone hands in their notice.
Thirst is built around exactly this idea — making it easy for teams to capture and share what they know as part of everyday work, rather than saving it for a rushed handover on someone’s last week. Knowledge stays structured, searchable, and current, instead of scattered across shared drives and Slack threads nobody can search properly.
What good institutional knowledge management looks like in practice
The difference between a business that manages institutional knowledge well and one that doesn’t rarely shows up as a single dramatic event. It shows up in dozens of small, everyday moments:
Onboarding
New hires get productive faster because answers already exist somewhere findable, instead of living exclusively in someone’s head.
Management
Managers stop fielding the same question for the fifth time this month, because the answer is written down where people can find it.
Autonomy
Teams act with more confidence, because they’re not constantly waiting on the one person who “just knows.”
Compounding
The organisation genuinely gets smarter over time, instead of quietly losing chunks of knowledge every time someone moves on.
In short: institutional knowledge stops being a liability the moment it stops being invisible. Once it’s captured, structured, and searchable, it becomes one of the most valuable assets a business has — one that compounds with every year the business operates, rather than resetting every time someone walks out the door.
Frequently asked questions
What is institutional knowledge in simple terms?
It’s everything a business and its people have learned through experience — including the parts never written down, like why a process exists, how a client prefers to be handled, or how to fix something only one person really understands.
What’s the difference between institutional knowledge and tacit knowledge?
Tacit knowledge is knowledge that’s hard to put into words — instinct and judgement built through experience. Institutional knowledge is broader: it includes tacit knowledge, but also documented processes, organisational history, and context that’s specific to one business rather than a skillset in general.
What is the “bus factor” and why does it matter?
The bus factor is a way of measuring how many key people would need to leave before a business or project is in serious trouble. A low bus factor — often just one or two people — signals that critical institutional knowledge is dangerously concentrated.
How much does losing institutional knowledge actually cost a business?
Replacing a single employee earning above £25,000 costs an average of £30,614, with roughly 82% of that coming from lost productivity rather than recruitment. On top of that, replacements typically need six to twelve months before reaching their predecessor’s level of context and output.
What’s the best way to start capturing institutional knowledge?
Start by identifying your highest-risk people — those hardest to replace or most likely to leave — rather than trying to document everything at once. Then focus on making contribution as frictionless as possible; the simpler the process, the more consistently people will actually use it.
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
