Every leadership team eventually has one name that changes the temperature in the room.
You know the person.
They know the business.
Customers love them.
They solve problems nobody else can solve.
They have been there forever.
When something breaks, everybody calls them.
They might generate a lot of revenue.
They might hold an entire department together.
And they may also be making everyone around them miserable.
That is where the conversation gets interesting.
Because someone inevitably says:
“We can’t afford to lose them.”
Maybe.
But I think leadership teams should also ask another question:
What is it costing us to keep the situation exactly as it is?
Performance can hide a lot
A strong performer creates obvious value.
The damage around them is usually harder to measure.
A manager stops speaking up.
A good employee quietly leaves.
People avoid certain conversations.
Processes get bypassed because one person “has their own way.”
New employees learn that the rules apply differently depending on who you are.
The leadership team spends an unreasonable amount of time managing around one individual.
None of that appears neatly on a financial statement.
But it has a cost.
Sometimes the company created the problem
This part matters.
It is easy to turn the high-performing employee into the villain.
That is often too simple.
Maybe leadership allowed the behavior for years because the results were good.
Maybe the business became dependent on knowledge that should have been distributed.
Maybe nobody ever clearly defined expectations beyond “get results.”
Maybe every difficult conversation ended with:
“That’s just how they are.”
If leadership tolerates something long enough, tolerance becomes permission.
That does not make the person bad.
It means the system has adapted around them.
And now changing the system feels dangerous.
Dependency feels a lot like value
The more dependent a business becomes on one person, the more valuable that person appears.
Sometimes they truly are exceptional.
But exceptional performance and organizational dependency are not the same thing.
A healthy company should ask:
What knowledge only exists in this person’s head?
Which relationships depend entirely on them?
What decisions can nobody else make?
What processes stop if they are gone?
Who could step in tomorrow?
If the answer to that last question is “nobody,” leadership has work to do regardless of whether the employee stays for another 15 years.
That is not succession planning for executives.
That is basic operational resilience.
The wrong conversation is usually binary
Leadership teams often frame the issue like this:
Keep them or fire them.
That is too narrow.
There are several questions before that.
Have expectations been made clear?
Has someone actually addressed the behavior?
Does the person understand the impact they are having?
Is the role a fit?
Does the individual have strengths that would be more valuable somewhere else?
Can responsibilities be redesigned?
Can knowledge be transferred?
Is leadership willing to hold the same standard for a top performer that it holds for everyone else?
Sometimes the person changes.
Sometimes the role changes.
Sometimes the company realizes the problem was broader than one employee.
And yes, sometimes the relationship eventually needs to end.
But avoiding the conversation because the person is valuable is not a strategy.
Your strongest employee should make the organization stronger
This is the standard I keep coming back to.
The best people do more than produce.
They make the organization around them better.
They develop others.
They share information.
They improve the process.
They challenge things productively.
They create confidence rather than dependency.
That does not mean they have to be easy.
Some of the best people I have worked with were demanding.
There is a difference between being demanding and being destructive.
Good leadership knows the difference.
And good leadership does not outsource culture to whoever happens to produce the biggest number.
So if there is one employee everyone is afraid to lose, recognize their contribution.
Respect what they have built.
Then ask the harder question:
Have we built a stronger company around them—or simply a company that cannot function without them?
Those are very different things.
