Write down the decisions only they made, not the tasks only they did. Tasks get relearned in a few weeks, while judgment takes years – which client escalates, which supplier actually delivers, which figure is always wrong. So spend their notice period asking questions, not requesting a manual.
They resigned on a Tuesday. By Wednesday you’d started a list of everything they touch, and it kept getting longer. Somewhere on it is something you didn’t know they did.
The panic is real, but it’s also pointing at the wrong problem.
My best employee just resigned – what do I do in the next two weeks?
Stop asking them to write documentation and start asking them questions, with other people in the room.
Handover documents written alone are almost always a table of contents. They list what the person does, but they skip the deciding – which of four options was right – because after six years that stops feeling like information.
So use the notice period differently – put the two or three people who’ll absorb the work next to them and work through live cases together. Record the sessions. The valuable material comes out as an aside – “don’t send that one before Friday, she never reads anything on a Thursday”.
How do I replace an irreplaceable employee?
Usually you don’t replace them with one person, because the job they were doing was never one job.
Someone who’s been with you five years has quietly absorbed parts of three roles. Their job description never changed to reflect it. Hire against that old description and you get someone who does the written job well and none of the rest.
Split the real work on paper first: list what actually needs doing, mark who could hold each piece today, then hire against the biggest gap left. Slower for a fortnight, much faster after that.
If one person leaving can stall your business, that’s a design problem – and you designed it.
It’s how companies between ten and two hundred people almost always grow: someone is capable, so they get handed more – and it stays efficient right up to the day it isn’t.
Why doesn’t anyone use the process documents we already wrote?
Because they describe steps, and what people are stuck on is decisions.
A document that says “raise the PO, get approval, send to supplier” won’t tell you whether this supplier really delivers in five days. So people walk over and ask the person who knows. Panopto surveyed 1,001 US employees: they reported losing around five hours a week waiting on colleagues, and eight hours hunting for information.
| What usually gets written down | What actually walks out the door |
| The steps for closing the month | Which two figures are always wrong and need checking twice |
| The client list | Which client rings the founder if you’re one day late |
| Where the files live | Which version everyone actually uses |
| The supplier’s contact details | Who at the supplier says yes to a rush order |
| The approval workflow | When it’s fine to skip a step, and when it absolutely isn’t |
So what do you actually do
Pick the two or three decisions only one person can currently make. Make the next one of each in front of someone else, reasoning out loud, and let them take the notes – theirs will be better than yours, because they’re recording what surprised them. Then rotate.
Don’t start by buying knowledge management software. A team that doesn’t share decisions out loud won’t start sharing them in a new tool.
FAQ
Should I counteroffer when a key employee resigns?
Usually not, and almost never out of fear. A counteroffer made because you’re scared of the gap teaches everyone that power comes from being indispensable – the exact behaviour that got you here. If they’re leaving over something you can fix – scope, manager, pay that was always wrong – fix it and say so. If you’re buying time, buy it honestly: a longer notice period with a bonus attached to a real handover.
How do I get my team to document what they know without them thinking I’m replacing them?
Ask them to teach rather than to document. “Write up your process” reads as a threat; “spend an hour a week showing Marta how you handle the tricky accounts” reads as seniority, because it is. Make it visible that the people who train others are the ones who get promoted, and the resistance mostly disappears.
What do I do when my best employee is also the one hoarding information?
Treat it as a signal about their job security, not their character. People hoard when being the only one who knows feels like the only thing protecting them. That’s a conversation about their future at the company first, and a process conversation second.
Do I need an operations manager or am I just disorganised?
If your problems are mostly “nobody knows who decides this”, you need clearer ownership, not a new hire. If they’re mostly “we know who decides, but nothing gets followed through”, that’s an operations hire. Bringing someone in before you’ve untangled ownership just gives the confusion a new owner.
How long does it take to get back to normal after a key person leaves?
In our experience, three to six months for the work itself, and longer for the team’s confidence. Recovery is quicker where the leaver spent their notice teaching rather than writing, and slower where the answer to every question was one name.
The bottom line
Nobody takes your business’s knowledge with them when they go – what they take is the only copy of decisions that were never made out loud.
The fix isn’t a better handover template, but making more decisions in front of more people, starting while nobody has resigned. That’s much of what we do at Sigma Growth Specialists – getting the business out of a few heads before the question turns urgent.
