“That Operation Runs Itself” Is Usually the Beginning of the Problem
I’ve heard this sentence for years in operations:
“That operation runs itself.”
It’s usually said with pride.
Great leader. Strong team. Numbers look good. No drama. No fires to put out.
Perfect.
So we do what leaders naturally do. We turn our attention to the places that need us more.
One less visit. One less call. One less question. One less moment of, “What are you seeing that I’m not?”
And because nothing immediately falls apart, we assume our absence is proof that everything is working.
It may be.
But I’ve been around operations long enough to know something else can be happening.
Drift.
Not the dramatic kind. The dangerous kind. The kind that still looks good on a report.
Standards don’t suddenly disappear. They bend a little. Decisions that used to include others get made inside four walls. Communication becomes mostly updates: Here’s what happened. Here are the numbers. Here’s what we need.
The leader is still capable. The team is still functioning. The work is still getting done.
But somewhere along the way, the operation starts becoming an island.
And here’s what makes this so easy to miss:
Disengagement doesn’t always look like failure. Sometimes it looks like stability.
Reports are submitted. Guests or clients are taken care of. Targets are hit. Nobody is calling you with a problem.
Meanwhile, nobody is challenging much either. Nobody is asking whether the way they’ve always done it is still the best way. Nobody is bringing fresh thinking into the operation.
And the person leading it may slowly stop feeling like part of something bigger and start feeling like the person responsible for keeping their place running.
Same company. Same logo. Same standards on paper.
Different operation in practice.
I’ve seen this happen with very good leaders. Actually, I think good leaders can be especially vulnerable to it.
Because competence earns trust. Trust earns autonomy.
And autonomy, without enough connection, can quietly become isolation.
That doesn’t mean the answer is more oversight.
Please don’t read this and schedule twelve new meetings.
Micromanagement isn’t connection.
The answer is meaningful presence. Autonomy still needs visibility. Trust still needs conversation. Strong leaders still need to be challenged. And people who rarely need your help still need to know they have your attention.
TRY THIS: THE ISLAND CHECK
Think about the location, department, team, or even the person, you worry about the least.
The one you describe as: “They’ve got it.”
Now ask yourself:
When was the last time I had a conversation with them that wasn’t about an update, a number, a problem, or a deliverable?
Then go a little deeper:
What are they seeing that I haven’t asked about? What have they started doing differently that I may not even know about? Where have standards slowly become preferences? Who is challenging their thinking right now? Do they still feel connected to the larger organization—or simply responsible for their piece of it?
And perhaps the most uncomfortable one:
Am I giving them autonomy… or have I simply stopped paying attention because they make my life easier?
There’s a difference.
Leadership isn’t about making yourself necessary. The goal should absolutely be to build people and operations that can perform without you standing over them.
But “they don’t need me” should never become “they don’t hear from me.”
So this week, reconnect with the place you rarely check on.
Not to inspect. Not to catch something wrong. Not because there’s a problem.
Go because there isn’t one.
And ask a question you probably won’t find on a report:
“What’s changing here that I might not see from where I sit?”
Then listen.
Because nothing runs itself.
Sometimes it just runs long enough without our attention that we stop noticing the story is changing. If this made you think of a team, a location, or even your own leadership, it may be worth looking a little closer. Sometimes that’s where coaching starts.
Comments