When One Employee Knows How Everything Works — and the Financial Risk of Key-Person Dependency

The tolerated pain

Businesses often celebrate the person who can fix every exception. Over time that competence becomes infrastructure: colleagues wait for them, approvals route through them, suppliers know only them and undocumented work stops when they are unavailable.

How it becomes money

• critical work queues behind one person;
• leave, illness or departure can interrupt operations;
• new employees take longer to become productive;
• management cannot confidently change systems or suppliers;
• high-value specialists spend time answering repeatable operational questions.

dependency exposure = critical processes with one capable operator × business impact of interruption × expected recovery time

This is a scenario model, not a generic benchmark. Use the business's own process criticality and recovery assumptions.

What better looks like

Critical procedures have named owners and backups; credentials use managed access rather than personal custody; recurring exceptions are documented; supplier contacts are organisational; and important operating knowledge is embedded in systems, runbooks and workflows.

Practical actions

1. Identify processes with only one competent operator.
2. Rank them by revenue, customer, compliance and continuity impact.
3. Document normal steps, exception rules, dependencies and recovery actions.
4. Cross-train a backup and test the handover.
5. Move shared credentials and vendor records into governed systems.
6. Redesign recurring manual coordination that keeps recreating the dependency.

Bottom line

The problem is not having indispensable people. It is allowing the business to become technically incapable of operating without them.