Lose the person. Keep the knowledge.
Someone resigns and fifteen years of “how we actually do it” walks out with them. That isn’t a people problem. It’s a documentation problem, and it’s only fixable before it happens.
The resignation isn’t the problem. What leaves with them is.
Two weeks’ notice sounds like enough time. It never is. What you’re trying to extract is the workaround nobody mentioned because it stopped feeling like one, the client who has to be handled a particular way, the supplier who needs chasing on a Tuesday or the delivery slips.
You can’t download a person. And by the time you’re trying, they’re already halfway out the door.
Three reasons the handover never works.
They’ve already left
A notice period is the worst possible time to ask for someone’s best work. They’re mentally gone, they’re being counter-offered, and the handover doc gets written on the last Friday afternoon.
They don’t know what they know
Expertise is invisible to the expert. Ask a fifteen-year veteran to write down how they do the job and you get the version on the org chart, not the version that actually runs.
There’s nobody to hand it to
The replacement usually isn’t hired yet. So it goes to whoever is standing nearby, who already has their own job, and it decays from there.
Some of it doesn’t leave in their head any more. It leaves in their account.
When your operations manager builds an AI assistant that prices jobs, drafts proposals or triages the inbox, they have documented a process. A real one, often better than anything in your shared drive. But it lives under their login, with no owner, no review date, and no way for anyone else to know it exists.
Old key person risk
The knowledge sat in someone’s head. Painful, but you could at least sit them down and ask how they did it.
New key person risk
The knowledge sits in an automation. You can’t interview an automation. When they go, it goes, and often nobody even knows to look for it.
It happens before the resignation, not after.
You cannot capture fifteen years in a fortnight. You can capture it one process at a time while nothing is on fire.
Start with the money path
How a customer goes from first contact to paid. That’s usually 10 to 15 processes, and it covers about 80% of what actually runs the business.
The person doing the work records it
Once, on screen, while they’re still motivated to do it well. Somebody else turns that recording into the written process.
Give every process an owner
A name and a review date. So the day someone resigns, you know exactly what just became unowned, instead of finding out three months later when it breaks.
The platform that holds it after they’ve gone.
What stays behind when someone walks out.
Thirty years of knowledge. One resignation away from a crisis.
“Thirty years of knowledge in people’s heads. One resignation away from a crisis.”
The Sydney String Centre had grown over three decades into a 40-person family business. Every department worked differently, and the long-tenured staff held it all. Andrea took the Systems Champion seat, started with the Critical Client Flow, and built a single source of truth across the business.
“Now the team suggests systems to us. That’s the cultural flip we were chasing.”
Other paths to the same destination.
Replace Yourself
Stop being the operator. Stay the owner.
Learn more → HolidayTake a Real Holiday
Step out properly, without the phone ringing.
Learn more → ExitBuild to Sell
Make the business worth buying, and able to run without you.
Learn more → SuccessionFamily Business Succession
Hand it to the next generation without handing over the chaos.
Learn more →Things owners ask when someone hands in their notice.
Someone has already resigned. Is it too late?
Not entirely, but be realistic about what a notice period can produce. Pick the three things only they can do and record those first. Screen-share and talk it through rather than asking for a written document, because you’ll get more out of them in an hour of conversation than a week of typing. Then treat the rest of the business as the real project, so the next resignation doesn’t cost you the same way.
Who does the documenting if the person is leaving?
Not you, and not really them either. They record themselves doing the job once. Someone else, usually a Systems Champion, turns that into the written process. That way you capture what they actually do, rather than what they think they ought to say they do.
How long does it take to capture one role?
For a focused role, a few days of recording and a week or two of writing up. Doing the Critical Client Flow across a whole business is normally a few months at a sensible pace. The mistake is trying to capture everything at once, which is why most attempts stall in the first fortnight.
What if they won’t cooperate?
Some won’t, and that tells you something worth knowing. Most people are more willing than owners expect, particularly when it’s framed as leaving a legacy rather than as being made replaceable. The ones who genuinely refuse are precisely the risk you were worried about in the first place.
What about the AI tools they built?
Ask before they go, because nobody else will know these exist. Any prompt, custom GPT or automation doing real work is a documented process sitting in a personal account. Get it into the business while you still can, and put the next one somewhere the whole team can see it.
We’re small. Is this overkill for us?
Smaller businesses carry more key person risk, not less. When there are five of you, one person leaving takes a fifth of the operating knowledge with them. Small is also easier to capture, because there’s less of it and no legacy to unpick.
Lose the person. Keep the knowledge.
Start with one process. The one that would hurt most if the person who does it handed in their notice tomorrow.
Start Free Trial