You Have to Let Go the Only Person Who Knows How

You have to fire an employee who is the only one who knows the job, and the honest answer is uncomfortable: if none of that job is documented, you are not ready to act yet. Start documenting now, openly, for every role and not just for theirs, and describe the program as exactly what it is. Work the timeline with your employment counsel while it runs. The reason this hurts is that documentation was supposed to be a standing practice long before today, and it was not.

How Do You Fire Someone Who Is the Only One Who Knows the Job?

Slowly, and with the documentation already running. That is not the answer most owners want, because the decision feels urgent and the writing down feels like a project for next quarter.

Treat the role as a load-bearing wall. You do not knock one out and then go find out what it was holding up. Owners end up here because they have lived with the bottleneck so long it stopped registering as a risk, and it is worth understanding why your best person ends up holding it all before you decide the problem is the person.

If the process this person runs exists nowhere outside their head, you are not ready to act, and no clever sequencing fixes that.

That is not a delay tactic and it is not a loophole. It is a real constraint, and it usually costs you weeks you did not plan for.

Documenting Only on the Way Out Is the Failure State

The common advice is to capture the work first, while the person still has a reason to answer questions, and act second. Run your company that way and you have already lost, because you are doing the most important documentation you will ever do at the worst possible moment.

Look at the conditions. The person is on their way out, whether they know it yet or not. The material is being pulled out under time pressure by people who do not understand it. Somebody in the room knows the plan and somebody does not, and that gap is precisely the thing employment lawyers find interesting afterward.

The moment you say the words, you stop being someone they teach and start being someone they negotiate with.

Even a decent person who takes the news well stops volunteering the small things: the exception they handle every third Tuesday, the client who has to be called before the invoice goes out, the workaround for the field that never saves. One financial planning principal put the dynamic more bluntly than any consultant would. People control stuff because they do not want to give it up. That is true when the news is good, and much truer when the news is that they are leaving.

There is a worse version. If the documentation push is a pretext, a sudden interest in process aimed at one person whose fate you have already settled, you are asking your team to take part in something they will recognize later. Announce it accurately or do not run it. A program that cannot survive being described honestly to everyone is the wrong program, and it is the same error as treating the exit interview as your knowledge transfer plan.

The Version That Works Runs Continuously

The practice that actually protects you is not termination planning. It is knowing your bus factor and refusing to let it sit at one. What the bus factor measures is how many people would have to vanish before a process stops, and a role sitting at one is a role you cannot safely fire, promote, or send on a long vacation.

Every role gets documented on the same schedule, whether or not anybody is leaving.

That schedule is unglamorous. Recorded working sessions in the ordinary rhythm of the week, one role at a time, an hour at a time, with somebody other than the expert running the process back afterward to find the holes. When we run these sessions with clients, the ones that produce the most are the ordinary ones, because nobody is guarding anything.

The company that can part ways with anyone is the company that was already writing everything down.

You learn the cost of skipping it in miniature every time a key person calls in sick and you spend the day discovering what actually breaks without them. A termination is that same day with legal exposure attached.

What to Do If You Are Already Here

Most people reading this have no standing practice and a decision that will not wait. Here is the honest sequence, and every step of it happens in the open.

1. Score the risk first. Which roles sit at a bus factor of one, what breaks first if each one disappears, and how fast. Scoring your single points of failure usually turns up two or three real problems, and not only the person you were already thinking about.
2. Announce a program, not a project about one person. Every role, a published schedule, a stated reason. Say plainly that the company documents how work gets done because it has been carrying too much risk in too few heads.
3. Book recorded sessions, not write-ups. Nobody writes a manual. They will do the job on a screen share for an hour. Plan on two to four hours per process, and capture purpose, decision points, and steps, in that order. The middle one is the part that walks out the door with people.
4. Have someone else run it back. Not read it. Run it, live, with the source watching. Anything that stalls is a gap, and gaps found now are cheap.
5. Work the timeline with counsel in parallel. Your employment counsel or HR advisor should know what you intend and by when, because notice, final pay, and documentation rules vary by state and are not worth improvising.

Two weeks of focused effort gets you two or three processes documented well enough for a competent replacement to run them badly at first and correctly by month two. It does not get you a library.

Check What They Personally Own

Separately from all of that, find out what is registered in this person's name rather than the company's. This step gets skipped, and it produces the ugliest surprises.

At one staffing firm, a departing employee personally owned the company's video hosting account. Every training video the business had made sat behind a login that belonged to him, and ownership had to be transferred before he went dark. At a real estate investment company, an employee had recorded a training video with social security numbers and credit reports visible on screen, and the whole thing had to be blurred before anyone could use it. Neither of those is solvable after the last day.

So audit the accounts, the vendor portals, the phone numbers that ring to a personal cell, the shared drives with one owner, and the recordings that may hold things you cannot legally circulate. That audit belongs on the offboarding checklist that protects the business, and the better version runs annually for everyone, so no single departure is ever the reason you finally look.

Grade on Countable Behavior While You Decide

If you have not made the call yet, the trap is judging on feel. A staffing agency's customer service trainer had two representatives on the chopping block, both below the 76 percent attainment bar and two percentage points apart from each other.

One was systematic and hit her volume but never acknowledged what the caller had just said. The other applied coaching on the very next call and still sounded robotic doing it. On paper, both were following instructions.

His fix was not to argue about tone. He moved the grading to things that cannot be debated: call avoidance and schedule adherence. He also reworded a rubric item from "show empathy or enthusiasm when needed" to "empathy or enthusiasm statement," because he wanted his graders hunting for one specific, findable sentence in the first thirty seconds rather than forming an impression.

If you cannot name the countable behavior you are firing someone for, you are not ready to fire them, and you are definitely not ready to defend it.

That reframing tells you something about documentation too. Countable standards are transferable. Impressions are not, and a role built entirely on one person's instincts is a role you will have to rebuild rather than refill.

---

The Day You Tell Them, and the Day After

By the time you hold the conversation, the company should already own what the company owns. Account transfers are routine hygiene from the annual audit, not a special operation run the night before. Keep the conversation short, be specific about the countable thing rather than the feeling, and have your employment counsel or HR advisor sign off on the sequence and the paperwork before a date goes on the calendar.

Expect the temperature to change immediately. Access removal should follow a written order you wrote last week, not one you improvise in the hallway. Assume any promise of a clean handover in the final two weeks will be partial, and that the promise made warmly on day one thins out by day four.

The day after is the real test, and it is almost always quieter than owners fear. What goes wrong is rarely dramatic. It is the third-party portal nobody could log into, the report that stops arriving, the recurring task that existed only as a repeating reminder on somebody's phone.

How Do You Make Sure You Are Never Here Again?

You stop letting any single role become a wall you cannot inspect, and you make documentation a calendar item instead of an emergency. That is the entire prevention. It is boring, which is exactly why it does not get done.

The Systems Effect exists mostly because owners call after the decision is already made, and the honest version of that work is triage rather than the thing we would rather have built with them a year earlier.

Do one thing this week, whether or not you have a termination coming. Pick the person whose absence would hurt most, book one hour, and record them running their single most important process while the relationship is perfectly normal. Then book the next one, for a different role, so that it reads as a practice and never as a signal.

Frequently Asked Questions

How do you fire an employee who is the only one who knows the job?

Not quickly, if nothing is documented. Start an open documentation program covering every role, get the two or three highest-risk processes recorded and run back by somebody other than the expert, and work the timeline with your employment counsel while that happens. Fire first and ask for a handover second and you lose the process along with the person. The decision is only cheap in companies that were documenting all along.

Should you document a key employee's work before telling them they are being let go?

Document every role continuously, before anyone is on the way out. That is the only version that holds up, because a sudden push aimed at one person whose fate you have already decided produces poor material and looks exactly like what it is. If you have to start late, start openly and for the whole team. Once someone knows they are leaving, cooperation turns into a negotiation and the small unwritten exceptions stop flowing first.

What do you check before terminating a key employee?

Anything in their personal name rather than the company's: software and video hosting accounts, vendor portals, domains and phone numbers, shared drives with a single owner. One departing employee personally owned his company's entire video hosting account, and ownership had to move before he went dark. Also review existing recordings for sensitive data on screen, because material with customer information visible cannot be reused until it is edited.

How long does emergency knowledge capture take?

Two weeks of focused effort gets the highest-risk processes documented well enough for a replacement to run them, at roughly two to four hours of the expert's time per process. It does not produce a complete library, and it should not be sold to yourself as one. Treat it as triage, which is what continuous documentation costs when you buy it late, under pressure, with the relationship already strained.