Good morning.
Your best employee may be hiding your worst system
Every community has one.
The nurse who knows how everything actually works.
The scheduler who can fill a 3–11 hole when nobody else can.
The department head every difficult family gets sent to.
The CNA who can calm the resident nobody else seems able to redirect.
The business office manager who knows the weird workaround nobody bothered to write down eight years ago.
We call these people our rock stars.
And we should.
But sometimes your best employee is also hiding your worst system.
Because every time they save the day, they prevent the broken process underneath them from becoming painful enough for leadership to fix.
Think about the phrases we use:
“Just ask Maria. She knows.”
“Don’t worry. Mike always handles that.”
“She’s the only one who can get Dr. Smith’s office to respond.”
“If she’s off, wait until Monday.”
Those sound harmless.
They’re not.
They’re telling you where your operation has single points of failure.
The scary part is that hero-dependent departments can look like high-performing departments.
Things get done.
Families are happy.
Problems disappear.
The administrator doesn’t get dragged in.
Then your superstar takes PTO.
Or gets promoted.
Or burns out.
Or quits.
And suddenly everyone discovers that what looked like a system was actually one really good person holding six things together with duct tape.
Great operators should absolutely develop great people.
But there is a difference between:
“This person makes us better.”
and
“This place doesn’t work without this person.”
The first is talent.
The second is operational risk.
5-Minute Building Audit: The Hero Dependency Test
Ask each department head one question:
“If you couldn’t come to work for the next 30 days starting tomorrow, what would break?”
Then don’t accept:
“Nothing. My team has it.”
Push once more:
“What do you know, do, approve, fix or remember that nobody else can reliably reproduce without calling you?”
Now we’re getting somewhere.
Look for:
- processes that live in someone’s head
- relationships only one person owns
- passwords or systems only one person understands
- recurring problems only one person knows how to fix
- decisions nobody else feels authorized to make
- families or physicians who will only deal with one
leader
- reports nobody knows how to produce
- frontline situations where “only Sarah can handle him”
Pick one.
Don’t create a 47-page SOP nobody will read.
Have the person teach somebody else.
Document the critical steps.
Give the backup a chance to actually perform it.
Then let the rock star stop doing it once or twice and see whether the system survives.
That’s the part we miss.
A backup isn’t somebody whose name appears on an organizational chart.
A backup is somebody who has successfully done the work without the expert standing next to them.
And there’s another reason this matters.
Your best people usually won’t complain first.
They’ll just keep fixing things.
That’s why they’re your best people.
Until one day the organization has rewarded competence with an ever-growing pile of everyone else’s problems.
So today, thank your rock stars.
Then ask yourself a slightly more uncomfortable question:
What are they protecting me from seeing?
Because the goal isn’t to build an operation that doesn’t need great people.
It’s to build one where great people can make the organization better instead of spending every day preventing it from breaking.
— Kevin | 