Blueprint & Pillar

Most organizations don't need to be convinced they have key person dependency. They can usually tell you exactly who their key people are. The more difficult question is why it continues even after everyone recognizes it's a problem.

​

The System Rewards the Dependency

Being the person everyone depends on can be stressful, but it also reinforces behaviors that have been rewarded for years. Sometimes the quickest way to keep work moving is to solve the problem personally rather than investing time in making the work independent of you.

​

This isn't typically a conscious withholding. Instead, it shows up in the following ways:

​

• Anticipating what will need to be done and doing it before anyone else has a chance to

• Still reviewing work anyway after handing it off to someone else

• Being the only person clients ask for

• Being the only person trusted to resolve edge cases

• Being the only person who understands a legacy system

​

Leadership Avoids the Disruption

There's a shorter-term cost to acting and a longer-term cost to not acting, and organizations are generally better at responding to the former. The slowdown caused by dependency is gradual and quiet. The disruption caused by directly confronting it is immediate and loud.

 

Reducing the dependency usually means having an uncomfortable conversation with someone who has been carrying a heavy weight for the organization for a long time. Asking them to change how they operate can read as a criticism of the exact thing that made them valuable in the first place. It's easier to work around the problem quietly than it is to have that conversation directly.

​

The Organization Adapts

Once work begins flowing through a key person, everyone develops habits that assume and ensure that dependency will continue. Over time, the workaround becomes the default process.

​

Most organizations don't address key person dependency until it becomes expensive. A delayed product launch, an extended leave of absence, rapid hiring, or an acquisition can suddenly expose how much work depends on one person. By then, the dependency has usually been building for years.

​

Recognizing the Problem Isn't the Same as Having a Reason to Fix It

None of this means the people involved are acting in bad faith. The person holding the dependency is usually doing exactly what has been asked of them. Leadership is usually managing real, competing priorities. The organization is usually just getting work done the only way it can be done.

​

Identifying key person dependency explains where work slows, but it doesn't explain why the workflow depends on that person in the first place. That requires looking beyond individual behavior and examining how work, information, and ownership move through the operating system.