Most CEOs Are Still Operators and Don’t Know It
There’s a version of leadership that looks like running hard and staying involved in everything. It feels like accountability. It feels like caring. And for a long time, especially in the early stages of a business, it works. The CEO is the one who knows the most, moves the fastest, and gets things done. That’s how a lot of businesses get built.
It’s also how a lot of businesses get stuck.
Slade McLendon, CEO of Sunbelt Fire, described this moment in a recent episode of The Fast Slow Motion Podcast: How a Third-Generation Family Business Built Something Worth Passing Down with more honesty than most leaders are willing to offer. He was moving fast, thinking big, and assuming his team could see what he saw. They couldn’t. He was already three steps ahead before the meeting had started, and the people around the conference table were still trying to figure out where they were going.
That’s an operator problem, not a leadership problem. And the distinction matters.
What an Operator Does vs. What a Leader Does
An operator runs the business. They’re in the decisions, managing the details, solving the problems as they come up. In the early days, this is exactly what the business needs. The founder’s hands need to be on everything because there’s no one else and no system yet to carry the weight.
A leader builds the system so others can run it. They set the vision, put the right people in the right seats, create the structure that makes good decisions possible without them in the room, and then get out of the way.
Most CEOs are good at the first thing. The ones who build businesses that last get good at the second.
The problem is that the shift from operator to leader doesn’t happen automatically. It has to be chosen, deliberately and repeatedly, because the operator instincts don’t disappear. They’re the instincts that built the business. They feel productive. They feel responsible. And every time something goes wrong, they pull the CEO back in.
The Wake-Up Call Slade Didn’t See Coming
Slade describes a specific moment that landed differently than most feedback he had received. Someone on his team told him directly: you come into a meeting and you’re already in LA. You’ve already got a facility set up, you’re ready to go, and we’re all sitting around the table asking what we’re doing.
That’s a leader who is operating so far ahead of his team that the team can’t follow. The vision was real. The thinking was sound. But none of it was accessible to the people who needed to execute it.
This is one of the most common patterns in growing businesses. The CEO’s strengths — speed, vision, pattern recognition, bias toward action — start working against the team’s ability to function. What made the leader effective in year two becomes the ceiling in year seven.
Slade’s phrase for it is direct: he was using his strengths to an extreme, and they were becoming weaknesses.
Why the Operator Identity Is So Hard to Let Go
Part of what makes this shift hard is identity. For many founders and CEOs, being the one who knows, decides, and solves things is deeply tied to how they see themselves as leaders. Stepping back feels like stepping away. Delegating feels like losing control. Trusting the team feels risky until the team has proven it can be trusted — and the team can’t prove it if the CEO never gives them the space to try.
There’s also the short-term math. An operator-CEO can often solve a problem faster than the time it takes to explain it, delegate it, and wait for someone else to handle it. So they solve it. And the team learns that when things get hard, the CEO will step in. Which means they stop developing the capacity to handle hard things on their own.
It’s a pattern that compounds. The CEO stays busy. The team stays dependent. And the business stays limited by how much one person can carry.
What EOS Gave Slade That Nothing Else Had
When Slade found EOS, what clicked wasn’t just the framework. It was the language. EOS gave him a way to articulate the difference between a visionary and an integrator, between a role that sets direction and a role that executes it. It gave his team a shared operating system so they could function without Slade having to translate his thinking into every decision.
He built that out over time, eventually developing not one integrator but four, each owning a distinct part of the business: sales and revenue, operations, finance, and organizational development. Each empowered to lead their area. Each accountable to the vision without needing Slade to be the connector between every piece.
That structure didn’t happen quickly. EOS takes time to implement correctly, and getting people into the right seats was the hardest part. But the outcome is a leadership team that runs the business while Slade leads the direction.
The Question Worth Sitting With
If you’re a CEO, the honest question is this: are you leading your business, or are you running it?
The answer isn’t always obvious. Operators often look like leaders from the outside. They’re decisive, visible, and involved. But if the business slows down or stalls when you’re not in the room, if your team waits for your input before moving forward, if the hardest problems always end up back on your desk, you’re probably still operating more than you’re leading.
That’s not a failure. It’s a stage. The question is whether you’re willing to do the work to move past it.
For more on how Slade navigated this shift at Sunbelt Fire, the full conversation is on The Fast Slow Motion Podcast: How a Third-Generation Family Business Built Something Worth Passing Down.
Listen to the full podcast episode here.