What happens when you refuse to delegate? One CEO went from hands-on technician to drowning in direct reports—and it nearly cost him everything. Here's how he learned that true leadership means trusting others to do the work.
What happens when you refuse to delegate? One CEO went from hands-on technician to drowning in direct reports—and it nearly cost him everything. Here's how he learned that true leadership means trusting others to do the work.
There's a moment in every entrepreneur's journey where things get weird. You go from being the person who does everything to suddenly having people who report directly to you. And if you're not careful, you end up with 45 of them.
Yes, you read that right. Forty. Five. Direct reports.
If that number makes your head spin a little, imagine how John Snyder felt when he realized he'd created a management structure that was basically unsustainable. At Net Friends, as the company grew, so did his problem—and it wasn't actually a problem of growth. It was a problem of control.
Here's something nobody tells you when you start a business: at some point, you'll become your own bottleneck.
When you're the founder, you care about every detail. You want things done right. You remember how to do them right because you did them for years. So naturally, when you hire people, you oversee them. You check their work. You make sure they understand your standards.
Then you hire more people. And more. And suddenly you're spending 80% of your day in one-on-ones, emails, and status meetings—and 20% of your time actually moving the business forward.
John hit this wall hard. Managing 45 people directly meant he was essentially running a daycare center for adults instead of running a business. Every person wanted access to the CEO. Every decision needed his sign-off. Every problem landed on his desk.
The real kicker? He thought this was what success looked like.
The breaking point came when John realized something fundamental: his team didn't trust themselves because he didn't trust them.
When you micromanage, you send a message. You're saying, "I don't think you can handle this without me." Even if you don't mean it that way, that's what people hear. And it kills morale faster than any budget cut ever could.
The irony is that John probably hired smart, capable people. But he'd created an environment where they couldn't actually prove it.
Here's where the conversation gets interesting. Letting go doesn't mean abandoning your team or pretending you don't care about quality. It means something much harder: it means building systems and trusting people to execute within those systems.
Instead of having 45 people report directly to him, John restructured the organization to create layers of management. This sounds like corporate bureaucracy, but it's actually the opposite—it's liberation.
When you have middle management, leaders in the trenches, and clear reporting structures, here's what happens:
John's story is refreshing because he didn't try to spin his 45-person management catastrophe as a badge of honor. He called it what it was: a scaling mistake.
And that's the thing about building something real—you're going to make mistakes. The question is whether you're willing to admit it and fix it.
The CEO who thinks they need to be involved in everything isn't confident. They're terrified. Confidence looks like building a team so good that they don't need you looking over their shoulder constantly.
If you're scaling, here's the hard truth: your job changes. You're not the doer anymore. You're the strategist, the culture keeper, the person who makes the big calls.
And that means you have to let other people be the doers.
This isn't weakness. This isn't laziness. This is literally the job of leadership.
The companies that scale are run by leaders who figured out early that their personal productivity doesn't matter. What matters is team productivity. And you don't maximize that by holding the leash tighter.
John's journey from hands-on tech expert to CEO managing 45 people (and then finally to a CEO who built actual infrastructure) teaches us something important: scaling isn't about doing more. It's about multiplying.
When you let go and empower your team, you're not losing control—you're gaining leverage. One CEO working 80-hour weeks is just one person. Fifty smart people empowered to make decisions? That's an actual organization.
The hardest part of building something bigger than yourself is accepting that you have to stop being the bottleneck. But that's also the most rewarding part, because suddenly you're not managing 45 people—you're leading a company.
And that's a much better gig.
Tags: ['leadership', 'delegation', 'business scaling', 'ceo mindset', 'team management', 'msp industry', 'entrepreneurship', 'organizational structure']