Why your best employee is your biggest operational risk
The most valuable people in your business often carry knowledge that exists nowhere else. That's not a strength — it's a liability you probably haven't priced.
You know exactly who I'm talking about.
The person who knows where everything is. Who remembers the supplier's mobile number, the exception to the returns policy, the weird thing you have to do with the old EFTPOS machine when it freezes. The one new staff always go to first because they know they'll get a straight answer.
They're invaluable. They're also a single point of failure.
The problem with irreplaceable people
Here's the thing about operational knowledge: it doesn't transfer automatically. Every piece of know-how that lives in someone's head — every workaround, every process shortcut, every "well actually, the way we do it here is..." — is one sick day, one unexpected resignation, or one holiday away from being unavailable.
Most small business owners understand this in theory. In practice, they rely on these people so heavily that the thought of documenting everything feels overwhelming. So it doesn't happen. Until it has to.
Three moments that expose the gap
When they call in sick. You're fielding texts from staff who can't find the procedure, can't remember the code, can't reach your go-to person. What should have been a normal operating day becomes a minor crisis. You end up handling things remotely that you shouldn't have to touch.
When they go on leave. You brief them on everything before they go. You think you've covered it. Then day three, someone asks a question you forgot to cover, and nobody knows the answer. The customer waits. Or a bad call gets made.
When they leave. This is the worst one. The exit interview is a blur. The handover document is incomplete by definition — people don't know what they know until they're asked, and they're rarely asked systematically. Weeks later, you're discovering gaps you didn't know existed.
The documentation trap
The instinct is to solve this with documentation. Write it all down. A Google Doc. A Notion wiki. A shared drive full of PDFs.
This works up to a point, then it doesn't.
The problem isn't the documentation itself — it's the retrieval. When a staff member needs an answer at 7am on a Saturday, they don't want to search through a folder of files, skim a 40-page procedure manual, or wait for someone to reply to their message. They want the answer. Quickly, clearly, and in a form they can act on.
Static documents require you to know what you're looking for. Most staff don't — especially newer ones, or people encountering a situation for the first time.
What actually works
The businesses that handle knowledge continuity well share two habits.
First, they're systematic about capture. They don't wait for someone to leave before documenting what they know. They build the habit of writing things down as they go — procedures, workarounds, exceptions, anything that gets repeated.
Second, they make it easy to access. Not easy to store — easy to retrieve. There's a difference. A perfectly organised knowledge base that requires three clicks and a search query is less useful than something a staff member can ask in plain English and get a direct answer from immediately.
The best employee in your business is still going to leave eventually. What they know doesn't have to leave with them.