When One Person
Becomes the Entire Process

What Happens When the Person Everyone Relies On Is Unavailable?

Every organization has people who make difficult work look easy. They remember the exceptions, know which vendor to call, and recognize the small warning signs before anyone else notices. Their experience is valuable. The risk appears when that experience becomes the only way the work gets done.

A process can look dependable for years because one person keeps repairing it behind the scenes. Then a vacation, illness, role change, or departure reveals how much of the operation existed in someone’s memory.

Week 1 asked what you can see. Week 2 asked what matters and who owns it. Week 3 asks a different question: Can the work continue when its owner is unavailable?

Five Warning Signs of Key-Person Dependency

Look beyond job titles. These signs can appear in finance, operations, security, customer service, or a small team that has grown faster than its processes.

1. 
   1. Every question leads to the same person. Routine decisions, exceptions, and approvals wait for one individual.
2. 
   2. The instructions live in someone’s head. Documents describe the ideal process but omit the steps people actually follow.
3. 
   3. Access and recovery depend on one individual. Only one person can administer the system or reach its recovery methods.
4. 
   4. Work pauses when that person is away. Deadlines slip, issues accumulate, or someone must interrupt their time off.
5. 
   5. The backup has never completed the work. A name on a coverage list is the only evidence that someone else could take over.

1. Every Question Leads to the Same Person

Notice what happens when an invoice fails, a customer asks for an exception, or a report produces unexpected numbers. Does the team follow a clear decision path, or does everyone send a message to the same colleague?

Having an accountable owner is useful. Requiring that owner to resolve every routine question creates a bottleneck. Record which decisions others can make, what information they need, and which exceptions require escalation. Ownership should make a process clearer, not make one person its only doorway.

2. The Instructions Live in Someone’s Head

A procedure may say “run the monthly report” without explaining which source files to use, how to handle missing records, or how to confirm the result. The experienced employee fills in those gaps automatically. A substitute cannot.

Ask the person doing the work to walk a colleague through a real example. Capture the inputs, sequence, checks, exceptions, and evidence of completion. Store the instructions where the team can find them, assign a document owner, and review them when the process changes. A short, usable guide beats a polished document nobody can follow.

3. Access and Recovery Depend on One Individual

Sometimes the team understands the work but cannot reach the tools. One employee may be the sole administrator, the only vendor contact, or the holder of a recovery method tied to a personal phone or email account. An ordinary absence can then become an access problem.

Identify who can administer each critical service and how authorized backup access would be obtained. Use individual accounts, appropriate permissions, and organization-controlled recovery arrangements. Keep sensitive credentials in an approved secure system rather than placing them in process notes. Coverage should preserve accountability and access controls.

4. Work Pauses When That Person Is Away

Look at the last absence. Which tasks waited? Which deadlines moved? Who received an urgent call during vacation? Those interruptions are evidence of a process depending on someone’s availability.

Separate tasks that can safely wait from those that affect customers, cash flow, security, or contractual commitments. Agree on how long each essential task can pause and what coverage it needs. That gives the team a practical way to prioritize improvements instead of treating every dependency as equally urgent.

5. The Backup Has Never Completed the Work

“Taylor covers for Jordan” sounds reassuring. But has Taylor actually performed the process, with the required access and current instructions, without Jordan guiding every step?

Choose a low-risk example and let the backup run it while the owner observes. For sensitive or disruptive work, use a safe test or a walkthrough before attempting a live handover. Record where help was needed, correct the instructions, and repeat the relevant steps. The goal is demonstrated coverage, not an exercise that puts the business at risk.

Map One Dependency Before It Becomes a Disruption

Start with one important process that repeatedly leads back to the same person. Ask the owner and a potential backup to map it together:

1. Name the outcome and the impact of delay. What must happen, by when, and who is affected if it does not?
2. Capture the real workflow. Include inputs, systems, decision points, exceptions, and the checks that show the work was completed correctly.
3. Confirm authorized coverage. Identify a backup, verify permissions and recovery arrangements, and clarify when escalation is required.
4. Try the handover. Have the backup follow the guide in a controlled setting. Record gaps, assign fixes, and set a review date.

For example, a monthly billing process may depend on one employee to export data, correct exceptions, and submit the final file. Documenting only the export misses the judgment that makes the output accurate. A useful handover includes the reconciliation checks, the approval boundary, and what to do when the numbers do not match.

This work should happen with the experienced employee, with time allocated for it. Do not turn the person who already carries the process into the sole person responsible for fixing the dependency. Leaders need to provide capacity, assign coverage, and follow through on the gaps.

The aim is to preserve valuable expertise and make essential work repeatable. When knowledge, access, and decision-making have appropriate coverage, your people can step away and your organization can keep moving.