Every small business has a person who knows how everything works. Sometimes it is the founder. Sometimes it is the office manager who has been there twelve years. Ask anyone else how a particular job gets done and the answer is usually "ask Sarah."
This is not a criticism. It is how small companies run, and for a long time it works. Sarah knows which supplier to call, which spreadsheet has the real numbers, what to do when the invoice run fails, and which step in the onboarding everyone else forgets. The knowledge is real and it is valuable. The problem is where it lives.
It lives in one head. And a person takes time off, gets sick, retires, or leaves for a better offer. When that happens, the business finds out how many of its processes had a step that only happened because someone remembered it.
The scale of that exposure shows up in the research on succession. In a 2024 Gallup survey of 1,264 US business owners, a third had no plan or were unsure what would happen to the business when they stepped back, and the researchers kept landing on the same cause: the business runs on the owner personally, which makes it hard to hand over or even to describe. If that holds for the owner, it holds several times over for the systems only one other person understands.
The usual response is "we should write this down." People say it after every near miss. Then nothing happens, because writing it down is a project with no deadline and no owner, and the person who would do most of the writing is the busiest person in the building.
Even when it does happen, the document is usually the wrong thing. Someone spends a weekend on a forty-page manual, it goes in a shared folder, and nobody opens it again. The knowledge that matters is not a list of instructions. It is the judgment: why this customer is handled differently, when to escalate, what "done" actually means for this kind of job. That does not survive being written as a numbered list.
What works is smaller and more boring. You take the processes that would hurt most if they stopped, and you move them out of one person's memory into something the rest of the team can see and use. A form instead of a habit. A checklist built into the tool people already work in, not a separate document. A record of what happened, so the next person can follow the trail rather than reconstruct it.
Done properly this takes weeks, not a weekend, and it is worth doing in order. Start with the process that is one illness away from a bad month. Leave the things that are annoying but survivable for later.
This is usually the first thing a review of a small business turns up, which is why we start there. Before anyone talks about software, we map how work moves through the business, including the steps that only exist as habits, and write that down before proposing a single change. Often the plan that comes out is not "buy this system." It is "these four things are fragile, here is the order to fix them in, and here is what each one costs." What was a single point of failure becomes something the business owns.
If your business would struggle to run for two weeks without one specific person, that is worth a conversation.