When critical work depends on one person, you do not have a high-performer advantage. You have a risk that has not been named yet.

The moment it becomes obvious

I watched a VP tell a project manager to call someone who was in a hospital bed.

Not to check on him.

To get him on the release call.

He had just experienced a medical emergency. He was recovering. But the release was moving forward, and leadership believed there was only one person who could answer the questions, make the approval, or keep the work from stalling.

Everyone knew why.

• He had been with the company for more than 30 years.
• Nothing important moved without him.
• Nothing got approved, reviewed, or released without him.

He was not just experienced.

He had become the system.

Organizations rarely say that out loud.

They call that person trusted. Critical. The one who knows how things really work.

Then something happens.

A health issue. A vacation. A resignation. A family emergency. Burnout.

And suddenly, everyone sees what was there all along.

Key takeaway: When one person’s availability determines whether critical work can continue, you have a single point of failure, not a resilient system.

High performance is not the same as resilience

Your go-to person may be exceptional. They may be the reason a complex operation, transformation, or release has worked as well as it has.

But a resilient team can keep making decisions, serving customers, and moving work forward when a key person is out.

A dependent team cannot.

The risk is easy to miss when things are going well:

• Deadlines are met.
• Problems get solved.
• The same person steps in again.
• Leadership feels relieved.

But relief is not resilience.

The risk only becomes visible when that person cannot carry it anymore.

What go-to-person risk costs

When one person becomes the answer to every hard question, the cost is larger than workload.

What happens	What it costs
Decisions wait for one person	Work slows and priorities stall
Knowledge stays in one person’s head or inbox	The organization becomes fragile
Others are never given real ownership	Capability does not grow
One employee cleans up gaps repeatedly	Leaders mistake heroics for a healthy system
The go-to person keeps absorbing the pressure	Burnout and retention risk increase

Five questions leaders should ask

Use these questions to identify where dependency is hiding:

1. Whose absence would delay a release, decision, client response, or critical process this week?
2. What does that person know that is not documented or shared with others?
3. Which approvals, exceptions, or escalations automatically land with them?
4. Who gets described as “the only person who can do this”?
5. What would happen if that person took two uninterrupted weeks away from work?Important: Your answers are not a critique of the employee. They are information about the system around them.

How to reduce hidden dependency

Start with one dependency

Choose one process, approval, recurring decision, client issue, or release activity that relies too heavily on one person.

Get specific.

Instead of saying, “Jordan knows too much,” say:

“Only Jordan can approve production-release exceptions.”

That gives you something you can change.

Separate expertise from ownership

Your go-to person can remain an expert without owning every decision.

Clarify:

• What genuinely requires their judgment
• What can be delegated
• What information others need
• When escalation is necessary and when it is simply habit

Build a real backup

A backup is not someone whose name appears in a document.

A backup is someone who has:

• Access
• Context
• Practice
• Permission to do the work

If they have never managed the work without the go-to person nearby, you do not have coverage yet.

Protect the person while you change the system

Tell them they can step back.

Remove them from meetings where they are not needed.

Give another person a real opportunity to lead.

Do not treat vacation, illness, or a personal boundary as a test of commitment.

Your ability to save the day matters. But the organization should not need you to save it every time.

The leadership reflection

The question is not whether you have a valuable employee.

The question is whether your system treats that person as a source of capability or as an unlimited contingency plan.

The man in that hospital bed deserved better.

Not because he was not capable.

Because he was too capable, and the system had learned to take advantage of it.

Your go-to person is not a backup plan. They are a warning sign.

Find your hidden dependency risk

Is one person quietly holding your system together?

Take the 3-minute Go-To-Person Risk Score to see where critical knowledge, decisions, and work are concentrated in too few people, and what to address first.

Get Your Go-To-Person Risk Score →