The problem nobody schedules time for
Every small business has one. The person who "just knows" how payroll gets run. The office manager who's the only one who remembers how to reset the point-of-sale system. The founder who carries client relationships entirely in their own head.
It works — until it doesn't. Someone gets sick, takes a vacation, or leaves for a better offer, and a process that ran fine for years grinds to a halt. Nobody planned for this because nobody had to, until they did.
This is key-person risk, one of the most common — and most ignored — operational liabilities in growing businesses. It doesn't show up on a balance sheet. It shows up the week your ops lead is out with the flu and payroll is three days late.
Owners feel it as anxiety: a vague sense that the business would wobble if a specific person disappeared for two weeks. Team members feel it as pressure — the person holding the knowledge often can't take a real vacation without their phone buzzing. New hires feel it as confusion, because nothing is written down and everyone learns by osmosis.
If you've ever thought "I really hope nothing happens to Sarah, because I have no idea how she does half of what she does," that's the tell. You've already diagnosed the problem. The question is what to do about it.
Diagnose honestly: where does this actually live?
Before building a plan, map where the exposure sits. Walk through your core processes — sales, fulfillment, billing, support, HR — and ask three questions for each:
- Who is the single point of contact? If this person is unavailable for two weeks, does the process pause, degrade, or continue fine?
- Is the knowledge written down anywhere? Not "in an old email thread somewhere" — an actual document, checklist, or system someone else could follow cold.
- How much damage would a gap cause? A missed social media post is a shrug. A missed payroll run or a lost client handoff is a real cost.
This isn't about distrust of your team — it's an honest inventory. Most businesses find three or four processes that are genuinely fragile, surrounded by plenty of things that would be mildly annoying but survivable if a key person stepped away. Focus your planning on the fragile ones.
A useful companion exercise here is mapping the process itself before deciding what to do about it — you can't reduce a risk you haven't clearly described.
The options — and their trade-offs
Once you know where the exposure sits, you have three real options. Each solves a different version of the problem, and none of them are free.
Document it. Write down the steps, decisions, and judgment calls involved. This is the cheapest option and the fastest to start. The trade-off: documentation only helps if someone maintains it, and a written process is still a manual process — it reduces the risk of total failure but doesn't reduce the ongoing effort.
Automate the parts that are rules-based. If the risky process is mostly repetitive and predictable — data entry, report generation, recurring reminders — automation removes the dependency on a person's memory entirely. The trade-off: automation only works on the rules-based slice of the job. The judgment-heavy parts still need a documented, trained human backup.
Cross-train a second person. Build redundancy by making sure at least one other person can run the process, even imperfectly. The trade-off: this costs real time upfront, and it only works if it's revisited — skills atrophy if the backup person never actually uses them.
Most fragile processes need a blend: document the steps, automate the mechanical pieces, and make sure a second person has actually run the whole thing at least once. If you're weighing whether a given fix belongs in the "write it down" bucket or the "hand it to software" bucket, the automate-improve-or-ignore triage is the right lens to run it through.
What not to do first
The instinct, once you spot this risk, is to reach for a big system — an all-in-one platform that "handles everything" so no one person matters anymore. Resist that. A complex system nobody but you understands just creates a new single point of failure, this time made of software instead of a person.
Also resist the urge to fix everything at once. If you found six fragile processes, you don't need six projects running in parallel this month. You need a ranked list and a plan to work through it in order.
Building the prioritized plan
Rank your fragile processes using three factors:
- Likelihood of disruption. How often is this person out, overloaded, or likely to leave? A process run by someone who's been with you ten years is lower-likelihood than one run by a new hire in a high-turnover role.
- Impact if it fails. Would a gap cause a missed payment, a compliance issue, a lost customer — or just a delay of a day or two?
- Cost to fix. Some fragile processes take an afternoon to document. Others need real system changes. Cheap, high-impact fixes go first.
A simple way to visualize this: score each process 1–3 on likelihood and impact, multiply them, and use cost-to-fix as the tiebreaker. The highest-scoring, cheapest-to-fix items become month one. The high-impact, high-cost items get scheduled deliberately rather than ignored indefinitely.
Once you fix one, don't let it quietly slide back into being tribal knowledge. Whatever you document or automate needs to become the actual standard — the thing new hires are trained on, not a side note in a drawer. That's the difference between turning a fix into a real standard and just patching a crisis until the next one.
The takeaway for planning
Key-person risk is easy to ignore because it rarely causes damage on a predictable schedule — it waits for the worst possible moment. That's exactly why it belongs in your planning cycle rather than your reactive to-do list.
You don't need to eliminate every dependency on every person. You need an honest map of where the fragile spots are, a clear-eyed view of which fix — document, automate, or cross-train — fits each one, and a ranked list that gets worked through deliberately. That's a plan you can actually execute, instead of a worry you carry around indefinitely.