When one person leaves, the pain shows up three weeks later. At first, everything runs on momentum, and then the little things start to slip: who places the orders, who gets the report, why this one supplier wants every confirmation twice. You can always buy more hours. What’s missing are the processes nobody ever wrote down.
I hear this over and over in consultations. The owner pulls out a job ad before sitting down to write what that person actually did all week. I don’t blame them: the pressure is immediate, and there’s nothing on paper. But hiring takes weeks, and the work doesn’t go anywhere in the meantime.
They take the processes with them
Every role has two layers. You’ll find the first one in the job description, and you can hand it over in an afternoon. The second is written down nowhere, and it’s the one holding the operation together.
That’s exactly why losing someone who’s been with you for years hurts far more than losing a new hire. Along with their hours, they take the way things get done at your company. The new person then has to rediscover it by trial and error, and your customers notice too.
Silent workload
The part of a job that isn’t in any job description, yet decides whether everything keeps running. Which supplier needs reminding, which customer only wants calls in the morning, why one report still gets put together by hand. It lives in the head of the person doing it, and the company usually finds out about it only when that person leaves.
Hiring starts long before the job ad, with a list of what that person actually did. Almost nobody has one.
Break it down first, then decide
Break the workload down into individual tasks before you start looking. Forget org charts and job descriptions. This is a plain list: what happened, how often, and how long it took. Once you have it, it almost always splits into three piles:
- repetitive work, where the process is the same every time and you can check the result against a list,
- decision-making work, where the input changes every time and it takes judgment and knowledge of the business,
- relationship work: phone calls, meetings, apologies, and agreeing on exceptions.
The ratio between the three piles usually comes as a surprise. In administrative roles, the first pile is by far the biggest, and it’s also the one where people feel least needed.
One-minute self-test
Pick the person who’s been with you the longest. Try to describe their typical Thursday from memory, hour by hour, then ask yourself how much of it you could hand over to someone new without their help. The gap is your silent workload, and you pay for it in weeks of onboarding.
What a system can take off those piles
Today, a system can handle almost all of the first pile. For the second, it prepares the groundwork and leaves the decision to you. Leave the third alone. A phone call with a customer is the reason they stick with you, not a cost.
Compared with onboarding a new colleague, one thing is different. A process you describe once stays valid and never leaves. You teach a skill once, and the next time it runs the same way, without reminders or retraining. Responsibility for the result still sits with a person, even when AI does the work.
Learned skill
A process written in plain language so the AI does it the same way every time: what the input is, how it’s done, when to stop and ask. You write it once, and from then on you can call it up by name. There’s a practical side effect worth mentioning: the same text is also the best handover document you could have for a new colleague.
Thirty days, not thirty months
A month is enough to break down the workload and replace the first pieces of it, if you go in this order.
Week one is for recording. While the person is still at the company, walk through their typical week with them and record it. The task list then comes from the conversation rather than your memory, and a meeting archive that answers your questions pulls out details you’d never have thought of.
In week two, take three tasks from the repetitive pile. Three of them, not ten: the most frequent and the most boring ones. Write up the process for each one and let it run for the first time under supervision.
Week three is a trial run. The routines run, and you just check the output. When the system keeps its own log, you see in the morning what happened overnight, and you don’t have to ask anyone.
In week four, you decide. Only now do you know how much work is left and what kind. That tells you whether you’re looking for a full-time hire, a part-timer, or a freelancer for a few hours a week. It’s the same order that works for bringing AI into a company: one process first, the whole thing later.
Safety net
Throughout the trial run, nothing goes out without approval. The system prepares the order, email, or document and waits. For steps a customer sees or that involve money, this rule stays in place for good, not just for the first month.
Who shouldn’t bother
This exercise isn’t for everyone. If the person you lost had their whole workload in the third pile, a breakdown won’t help. A salesperson who lives on personal relationships or a tradesperson in the field can’t be written up as steps, and it’s more honest to start looking for a replacement right away. And there’s no point starting the day after someone gives notice. When tomorrow’s orders are on fire, you plug the hole first and break down the workload after.
The whole process in a nutshell
- Walk through the departing colleague’s typical week with them and record it.
- Break the workload into individual tasks: what was done, how often, and how long it took.
- Sort them into repetitive, decision-making, and relationship work.
- From the repetitive pile, pick the three most frequent tasks and write them up as processes.
- Let them run for a month under supervision and watch what’s left.
- Only then decide who you’re looking for and for how many hours.
And the job ad from the beginning, the one that got written before the list? You can still write it, and usually you should. Only now you’re writing it from the list instead of a gut feeling. The difference is that you’re hiring someone for the work that’s left, not for the seat that opened up.
