Every small business has people who matter more than their job title suggests.
It might be the operations manager who knows which suppliers can be trusted, the developer who understands how the company’s oldest system actually works, or the account manager who has spent years building relationships with the biggest customers.
If that person is away for a week, things may get slower.
If they are away for three months — or leave altogether — the problem can become much bigger.
For a small business, the risk is not simply losing an employee. It is losing knowledge, relationships and processes that may never have been documented anywhere else.
That is why employers should ask an uncomfortable question before a key person becomes unavailable:
What would stop working if this person disappeared tomorrow?
The Key-Person Problem Is Bigger Than a Job Vacancy
Replacing someone is usually framed as a recruitment problem.
But the first problem may actually be operational.
A small company can have dozens of processes that exist mostly inside people’s heads. One employee may know how to handle a particular customer, where an important file is stored, which software integration breaks occasionally, or which supplier needs to be contacted when something goes wrong.
None of that may appear in their job description.
This creates what is effectively a single point of failure.
UK government business-continuity guidance specifically identifies the loss of key staff or skills as a potential disruption to business operations. It recommends identifying critical activities, resources and responsibilities rather than waiting for a disruption to reveal what the company depends on.
For a small company, that exercise does not need to become a giant risk-management project.
It can start with one question:
Who knows how to do something that nobody else knows how to do?
The Person You Rely On May Not Be the Person You Think
Key-person risk is not always obvious.
The founder is an obvious example, but the dependency can sit much lower in the organization.
Consider a remote company with 15 employees.
The head of marketing may be the only person who understands the analytics setup. A customer success manager may be the only person who knows the history of several major accounts. A developer may be the only person who can deploy a critical part of the product.
None of these people necessarily have unusual titles.
Their importance comes from what they know.
A useful exercise is to list the company’s most important activities and then ask:
- Who owns this process?
- Who could perform it if that person were unavailable?
- Where is the information needed to do it?
- How long would it take someone else to learn it?
- What would happen if the person left permanently?
The answers can be surprisingly revealing.
Remote Work Can Hide the Problem
Remote teams have an additional challenge: visibility.
In an office, people sometimes pick up knowledge simply by being nearby. They overhear conversations, see how colleagues solve problems and know who handles what.
Remote work relies much more heavily on systems.
If a process exists only in someone’s private messages, personal notes or memory, the rest of the team may not even know that they depend on it.
That makes documented processes more important.
The UK’s National Cyber Security Centre recommends that small businesses identify critical systems and processes, make key documents accessible and up to date, and assign shared responsibility so someone else can provide cover when the usual person is unavailable.
The principle applies well beyond cybersecurity.
If only one person knows how to perform an important task, the company has a knowledge problem.
Don’t Make Everyone Learn Everything
The obvious response is to cross-train everyone.
That sounds sensible until a 12-person company tries to make every employee capable of doing everyone else’s job.
The result can be more meetings, more documentation and less time for actual work.
The goal is not to eliminate specialization.
It is to eliminate dangerous dependency.
A better approach is to identify the handful of tasks that would seriously disrupt the business if they stopped and make sure at least one other person can handle each of them.
That might mean:
- a second person knows how to access a critical system;
- customer information is stored somewhere the team can access;
- another employee can handle a key account temporarily;
- important processes have short written instructions;
- more than one person knows how to approve essential payments;
- critical supplier and contractor information is not held in one person’s inbox.
The backup does not need to become an expert.
They need to be able to keep the business moving.
Document the Things Nobody Thinks Need Documenting
Documentation often gets postponed because it feels less urgent than client work.
That is exactly why it becomes a problem.
The most valuable documentation is not necessarily a 50-page manual. A few pages can be enough to prevent a major disruption.
Start with the processes that would cause the most trouble if the person responsible suddenly became unavailable.
For each one, record:
What happens?
A short description of the process.
A short description of the process.
Who needs to be contacted?
Include customers, suppliers, contractors or internal decision-makers.
Include customers, suppliers, contractors or internal decision-makers.
Where are the files?
Link to the relevant folder, system or document.
Link to the relevant folder, system or document.
What access is required?
Make sure the business handles permissions and security appropriately.
Make sure the business handles permissions and security appropriately.
What happens if something goes wrong?
Include the most common problems and who should make the decision.
Include the most common problems and who should make the decision.
The goal is not to document every action employees take.
It is to make critical knowledge transferable.
Test the Backup Before You Need It
A company can have a beautifully written procedure that nobody has actually tried to follow.
That is not much of a backup plan.
The easiest test is simple: ask the backup person to perform the task.
If they immediately need to call the original owner for instructions, the process is not yet transferable.
This can be particularly useful for remote teams.
A manager might discover that the second person technically has access to a system but does not know which reports matter. A colleague might have the right documents but no idea which customer needs to be contacted first.
Those gaps are much easier to fix when the key employee is still available.
Sometimes the Answer Is Another Person
Documentation and cross-training cannot solve every dependency.
Some roles genuinely require more capacity.
A small company may have one person managing too many customers, one engineer responsible for an entire technical area, or one operations employee handling several unrelated functions.
In those cases, the answer may be another employee, a part-time specialist or a project-based professional.
Online.jobs’ 2026 listing data shows that employers on the platform have used several remote hiring models. Between March and May, full-time remote listings increased from 24 to 74, while part-time listings increased from 20 to 63 and project-based listings from 10 to 56. These figures are specific to Online.jobs and do not represent the entire remote labor market, but they illustrate the range of hiring arrangements available to employers.
The right question is therefore not always:
“Who can replace this employee?”
It may be:
“What capacity or expertise are we actually missing?”
Don’t Wait Until Someone Resigns
Key-person risk is easiest to see after something goes wrong.
An employee gets sick. Someone takes parental leave. A person resigns with two weeks’ notice. A contractor becomes unavailable.
Suddenly, everyone discovers that one person was holding together five different processes.
The better time to identify that dependency is when everything is working normally.
Managers can make it a simple quarterly exercise:
- List the business’s most important processes.
- Identify the person currently responsible for each one.
- Mark anything with only one knowledgeable owner.
- Decide whether it needs documentation, cross-training or additional capacity.
- Test the backup.
- Review the list when the business, team or technology changes.
It does not need to become another corporate process that nobody wants to maintain.
It just needs to be accurate enough to answer a basic question:
If this person is unavailable tomorrow, can we still operate?
A Strong Team Should Not Depend on One Person
Every business has people whose experience makes them especially valuable.
That is not a problem.
The problem begins when valuable knowledge becomes inaccessible without them.
For small businesses, resilience does not mean having a backup employee for every possible scenario. It means understanding where the business is most exposed and reducing the dependencies that could cause serious disruption.
Sometimes that means documenting a process.
Sometimes it means training another employee.
Sometimes it means hiring.
And sometimes it means admitting that a role has simply become too important — or too broad — for one person to carry alone.
The goal is not to make anyone replaceable.
It is to make sure the business remains functional when the person who knows the most is not there.
Building a remote team? Find the people your business needs to grow.
Sources
- Manchester City Council — Developing your business continuity plan
- National Cyber Security Centre — Small Business Guide: Response & Recovery
- CIPD — Absence Measurement & Management, 2026
- Online.jobs — Original 2026 remote job listing data, March–July 2026