Blueprint & Pillar

Key person dependency occurs when a workflow relies on one person because they hold knowledge, authority, relationships, or experience that nobody else in the organization can easily replicate.

​

That dependency can take many forms:

​

• Customer onboarding decisions that rely on one experienced operations manager

• Knowledge of legacy core banking processes that exists only in one employee's head

• High-risk customer reviews (KYC/KYB or EDD) that depend on one compliance specialist

• Client relationships that depend solely on one relationship manager

​

These dependencies develop naturally in every organization. Work tends to concentrate around the people who are the most experienced, knowledgeable, and trusted. It can go both ways: people naturally give the work to the person who is best at it, and the person who is best at it may accept that they are the most well suited to do the work.

​

Eventually, the same dependency that initially made the organization successful becomes what limits its growth.

​

The Costs Are Usually Invisible

The cost of key person dependency is measured in lost time. It may look like:

​

• Projects consistently finishing later than expected

• Tasks waiting for approvals before moving forward

• Managers spending their days answering routine questions

• New employees requiring excessive handholding

• Cross-functional work breaking down during handoffs

​

Each delay seems small on its own, but in totality, they slow down execution significantly.

​

Situations Where Key Person Dependency Becomes Visible

In certain scenarios, it becomes immediately evident who a key person was. For example:

​

• A compliance officer is out and regulatory approvals stop

• An experienced fraud analyst is unavailable and investigations begin piling up

• A senior operations manager leaves and no one understands how a critical process works from end to end

​

Why Hiring Doesn't Solve It

Many organizations assume that adding headcount will increase capacity. The problem with only hiring more people is that it does not fix the underlying workflow structure. If the workflow still depends on key people, then hiring more people will create more work for those key people without resolving the root cause of the issue.

​

New hires will ask them more questions, they will still own the same approvals, clients will still depend on the same people, and the backlog will grow instead of dissipating. This is why organizations can double their headcount while feeling no faster than they were six months earlier.

​

Documentation Alone Isn't Enough

Documenting processes and knowledge is often talked about as if it will solve key person dependency problems. While it is a vital component of mitigating the problem, documentation alone does not eliminate key person dependency risk.

​

A process may be perfectly documented, but if a workflow contains an excessive number of handoffs or approvals, then you can still have dependencies that slow work down.

​

A knowledge base may be well-developed, but if it does not clarify who owns each step of the workflow, then you can still have dependencies that slow work down.

​

The Goal Isn't To Remove Experts

Every organization needs experts to survive, particularly in industries that involve highly regulated or technical work. There are some roles where a certain degree of dependency is necessary for logical reasons.

​

For example, a fraud investigator may develop specialized knowledge that makes them highly effective at identifying risks and responding to them quickly. That is not a job you can quickly train anyone to do because it is the result of years of experience and pattern recognition. You wouldn't try to remove their specialized education, training, and experience from a workflow because their expertise is valuable to both the organization and clients.

​

The goal of reducing key person dependency is to ensure that when a qualified person transitions into a role, they have the appropriate workflow, information, and ownership structure needed to succeed without relying on undocumented knowledge or informal workarounds.

 

For a deeper discussion of how to distinguish valuable constraints from unnecessary friction, read The Difference Between Necessary Constraints and Unintentional Friction.