Your Best People May Be Hiding Your Worst Systems
Your best people may be doing more than delivering great results. They may also be compensating for weaknesses the organization has learned not to see. This article explores the difference between true operational excellence and systems that only appear strong because capable people keep rescuing them.
DEVELOPING PEOPLELEADERSHIP
Your Best People May Be Hiding Your Worst Systems
Every organization has them.
The person who knows whom to call.
The one who remembers the exception nobody documented.
The one who notices the customer order that somehow disappeared between two systems.
The one who stays late when something goes wrong, calls the supplier personally, finds the missing part, corrects the spreadsheet, explains the workaround, and makes sure the customer never realizes how close everything came to failing.
We call them our best people.
And many times, they are.
But there is another possibility worth considering:
Your best people may be hiding your worst systems.
Not intentionally.
Quite the opposite.
They care.
They are experienced.
They feel responsible.
And because they are capable, they continuously compensate for weaknesses the organization has learned not to see.
When competence becomes invisible infrastructure
Imagine a process that works only because María checks it every afternoon.
Nobody formally asked her to.
She simply learned, years ago, that if she does not check it, mistakes appear the following morning.
So she checks.
Every day.
Eventually, everyone assumes the process works.
But the process does not work.
María works.
Or think about the employee who knows that one particular supplier frequently ships the wrong revision.
The purchasing system does not flag it.
The receiving process does not catch it reliably.
The specification is not particularly clear.
But Daniel remembers.
Every time the order arrives, he walks over and checks it himself.
No defect reaches production.
Management sees excellent supplier performance.
Daniel sees something very different.
He sees a problem he has quietly prevented from becoming visible.
That distinction matters.
A system can appear stable because it is well designed.
Or it can appear stable because capable people are continuously stabilizing it.
From a distance, the two may look exactly the same.
Until one of those people goes on vacation.
“We can’t afford to lose her”
There is a phrase I have heard many times in organizations:
“We can’t afford to lose her.”
Sometimes that is simply recognition of an exceptional person.
But sometimes it is also a warning.
Why can’t we afford to lose her?
Because of her judgment?
Her relationships?
Her creativity?
Her leadership?
Those are reasonable answers.
But if the answer is:
Because nobody else knows how this works.
Because everything goes through him.
Because she is the only one who knows how to fix it.
Because he remembers all the special cases.
Then perhaps what we are describing is not only talent.
We may also be describing systemic dependency.
And dependency can easily masquerade as excellence.
Heroics create dangerous reassurance
Organizations love recovery stories.
A shipment was about to miss the deadline, but someone drove across town to retrieve the missing material.
A machine failed, but maintenance worked through the night and production restarted before morning.
A customer was furious, but one experienced manager made three phone calls and saved the account.
These stories feel good.
They demonstrate commitment, competence, and teamwork.
And all of those things deserve recognition.
The danger appears when the recovery becomes the end of the story.
Because every heroic recovery contains another question:
Why was heroism necessary?
If extraordinary effort repeatedly saves an ordinary process, the extraordinary effort can become part of the process without ever appearing on the process map.
The emergency call.
The personal reminder.
The unofficial spreadsheet.
The extra verification.
The relationship someone has cultivated with a supplier.
The knowledge stored only in one person’s memory.
The ten minutes somebody adds “just to make sure.”
None of these may appear in the standard.
Yet the system may depend entirely on them.
The paradox of great people
The better your people are, the longer a weak system can survive.
That is the paradox.
A weak team exposes problems quickly because the system cannot rely on people compensating for every flaw.
A highly capable team can do the opposite.
They adapt.
They improvise.
They remember.
They coordinate informally.
They solve problems before anyone else even knows there was a problem.
From a customer perspective, that can be wonderful.
From a learning perspective, it can be dangerous.
Because the organization receives the result without seeing the effort required to produce it.
And when results look good, there is little pressure to investigate the system underneath them.
This is one reason performance metrics can occasionally deceive us.
The number may say:
98% service level.
But it does not necessarily tell us how that 98% was achieved.
Did the process naturally produce that result?
Or did three experienced employees spend every afternoon chasing orders, negotiating exceptions, calling warehouses and manually reconciling information?
The outcome matters.
But so does the mechanism producing the outcome.
Ask what your best people are compensating for
There is a different conversation we can have with high performers.
Instead of only asking:
“What makes you so good at your job?”
ask:
“What do you have to do that you wish the system did for you?”
That question can reveal an enormous amount.
What do you check manually?
What do you keep in your own spreadsheet?
What do you remind people about?
What mistakes do you routinely prevent?
What information do you know cannot be trusted?
What do you do before going on vacation because you know nobody else will notice?
What decisions always come back to you?
What workaround has become so normal that nobody calls it a workaround anymore?
Those are not complaints.
They are clues.
Your most experienced people often possess a map of the organization’s hidden weaknesses.
Unfortunately, because they have become so skilled at navigating those weaknesses, we often admire their navigation instead of fixing the terrain.
Do not remove the person. Remove the dependency.
The goal is obviously not to make outstanding people less important.
Nor is it to standardize every ounce of judgment out of their work.
Some knowledge really does come from years of experience.
Some situations genuinely require expertise.
And organizations need people capable of responding when reality refuses to behave according to the procedure.
The goal is different.
We should distinguish between expertise that creates value and expertise being consumed to compensate for avoidable system weakness.
Those are not the same thing.
Your best engineer should be solving difficult engineering problems.
She should not be spending two hours every week correcting information that two databases cannot exchange properly.
Your most experienced supervisor should be developing people and improving the operation.
He should not be the human reminder system for twenty routine activities.
Your strongest customer-service employee should use judgment when unusual situations arise.
She should not have to personally chase every normal order because the workflow cannot make status visible.
When we improve the system, we do not make great people unnecessary.
We release their capability for better work.
A good system makes excellence scalable
Perhaps one of the best compliments we can give a great employee is not:
“We couldn’t survive without you.”
It may be:
“Because of what you taught us, the system no longer needs you to rescue it every day.”
That does not diminish the person.
It multiplies what the person contributed.
Their knowledge becomes a better process.
Their judgment becomes better training.
Their experience becomes better standards.
Their workaround becomes an improvement.
Their ability becomes capability shared by others.
That is a very different kind of recognition.
And it creates something much more sustainable than dependency on a hero.
So celebrate your best people.
Learn from them.
Reward them.
Keep them.
But also watch carefully what happens around them.
Because sometimes the people we admire most are quietly carrying weaknesses the organization has stopped noticing.
And sometimes your best people are not evidence of a great system.
They are the reason you have not yet noticed how fragile it is.