It's Friday afternoon, and the problem is back on your desk.
Not a new problem. The same one you thought you handed off three weeks ago, the one that belongs two levels down, to people you hired precisely so it wouldn't reach you. But here it is again, waiting on you to make the call.
You know the rhythm. You get pulled back into a conversation you thought was settled. You're carrying a dozen open questions you have to keep chasing down, because you're not confident the work is actually moving, or that it'll get finished the way it needs to be.
Other times it's the opposite of noise: silence. You haven't heard a word on something critical your team is carrying, and you sit in that silence getting more nervous the longer it goes, not knowing whether it's handled or quietly going sideways.
And then there are the dependencies. Two teams that don't report to each other hit a snag and just stop. Neither side pushes to work it out; each one waits on the other. They hand the same issue back and forth like they're passing a ball, and you're the only one who ever catches it. When you follow up, you realize nobody was actually trying to keep it moving, and now it's back on your plate to unstick. So eventually you stop waiting. Where's the answer? Fine—I'll do it myself.
One CEO I worked with, who has a leadership team of ten, put it more plainly than I could. Her problem, she told me, was never strategy. It was that nothing ever got closed.
When we actually measured where her time went, the number was about 900 hours a year. Not on strategy. Not on the vision she kept meaning to get to. Nine hundred hours spent chasing, nudging, and closing loops that were never hers to close. Nearly half her working year, spent being the person the whole company routes through.
She's not unusual. When Harvard Business School researchers logged 60,000 hours of CEO time, more than a third of it went to reacting to issues as they unfolded, and nearly nine out of ten CEOs reported spending time putting out fires.
And here's the part worth sitting with: this isn't proof that your people aren't good enough. It isn't even proof that you're doing something wrong. It's a design problem, not a you problem. Somewhere along the way, the company got built so that you became the only part of it that isn't a silo. Everything has to pass through you to get done.
What 900 hours actually costs
The hours are the easy part to count. They're not the real cost.
Think about what those 900 hours were supposed to be for. The strategy that never gets written, because every time you sit down to think, a Slack DM slides in: a "got a sec?", a text, a thread that can't move until you weigh in. The vision you can describe in a sentence but have never had two clear days to build. The new market, the next product, the business development only you can really drive. All of it idling, because the person who should be steering is down in the engine room again, fixing something. And it compounds as the company grows: in McKinsey's global research on decision-making, leaders reported spending more than a third of their working time on decisions, and said over half of that time was used badly. The more layers a decision has to climb to reach you, the worse it gets.
That's one side of it. Here's the other.
The evenings that get eaten. The weekend that wasn't really a weekend. Dinner you sat through with one eye on your inbox. The thing that used to be just yours, that you can't remember the last time you made room for: the workout you keep skipping, the instrument gathering dust in the corner, the trip you never get around to booking. Leaders rarely lead with this part, but it's usually what's quietly wearing them down. They didn't build a company in order to disappear into it.
And underneath both of those is a third cost, the one nobody puts a number on: trust.
Here's how it erodes. A problem that should belong to your team comes back to you. You handle it. You're good at handling it. But something small just happened: you learned, again, that you can't quite count on them to close it themselves. And they learned something too: that if they wait long enough, or escalate fast enough, it'll land back with you. So next time they bring it sooner, and you, having been burned before, reach for it faster.
Every loop that routes back through you spends a little trust in both directions. You trust them less to carry it. They get fewer chances to prove they can: fewer reps at the exact judgment, agency, and understanding that would let them carry it next time. The capability never builds, because the situation never lets it. The more you step in, the less reason they have to step up, and the more you have to step in.
That's the trap. It tightens on its own.
And here's the cost that outlasts all the others: it caps what you can build. Ask a leader in this position whether they could grow the business, and most will tell you, without hesitation, yes. No doubt at all. But in the same breath they'll admit they can't, because they know exactly what growth would do. More clients, more scope, more people means more loops, and every one of them still runs through you. At the next level, the team buckles. Then you do. And the next thing to break is the business you spent all those years building. So you hold it smaller than your own ambition, because you've become the one part of it that can't scale.
The research on founders says the quiet part out loud: four out of five are eventually forced to step down. Most not because the vision failed, but because the company outgrew the way they were running it.
Why "just delegate more" doesn't get you out
The usual advice is to delegate more. It sounds right, and it mostly doesn't work, at least not the way it's meant.
Delegation hands off tasks. You give someone a thing to do, and they do it. But your problem was never really the tasks. Your problem is that the work has to travel across teams to get finished, and the only place those teams reliably connect is you. You're not the person doing the work. You're the bridge the work crosses to get done.
You can't delegate a bridge. Hand off a task and you've moved one item off your list; the next cross-team loop still has nowhere to close except through you. That's why "delegate more" leaves so many leaders more tired, not less. They give away pieces of the work and keep the part that was actually crushing them: being the single point everything routes through.
What's broken isn't how much you've handed off. It's the design of the conversation between your teams: how a problem gets owned, moved, and closed when it doesn't sit neatly inside one person's job. Fix that, and loops start closing somewhere other than your desk. Don't, and you can delegate all day and still be the bottleneck. I've written before about why delegating more usually makes a founder bottleneck worse; this one—the silo trap—is the version delegation alone can't touch, because it lives between your teams, not inside any one job.
Become the space, not the bridge
There's a different way to hold the role, and it's the center of how I coach leaders out of this trap. I describe it as becoming the space between.
Stop trying to be the bridge that connects your people. Start building the space that lets them connect, own, and drive the work themselves.
I know that sounds abstract, so here's what it means in practice. Your job stops being the person in the middle that everything routes through, and becomes the person who builds the structure around what each person owns: who's accountable for what, how a problem moves between teams, where decisions actually get made, and what "closed" means, so everyone knows when something is genuinely done. Then you give people the room, and the support, to grow into carrying it: to truly own their work, and to start driving it forward without your constant oversight or involvement.
That's the shift. You stop being the integration point and become the person who designs how the work flows and grows around you.
I watched it land with a founder who was stuck exactly where you might be: the default decision-maker, the place everything came back to. The change wasn't that he learned to delegate harder. It was that he rebuilt the structure so his people could own the work and move it forward without him in the middle. He and his partner grew into genuine shared leadership. A rising member of the team stepped into a lead role she could actually hold. They felt the shift within the first month, and the loop they'd been stuck in started closing without him.
This is where trust starts compounding instead of leaking. Give a capable person the room and the structure to own something end to end, and they get the reps. They build the judgment, the agency, the understanding to handle the next thing without you. Google saw the same thing when it spent years studying its own teams: the single biggest factor in team effectiveness wasn't who was on the team. It was psychological safety, the shared trust that makes real ownership possible. One leader I worked with had spent years as a designer before she ran a team, and the moment it clicked for her was realizing that managing people is really just another kind of design challenge, something she could spot and solve on her own. That's the whole game. Not you solving it faster. Them building the capability to solve it at all.
And it isn't soft. When Gallup studied the CEOs of America's fastest-growing companies, the ones who handed their people genuine ownership, not just tasks, grew meaningfully faster and created more jobs than the ones who kept control. Gallup's read on the leaders who couldn't let go: they don't trust others, so they centralize every decision. The trust loop, measured.
This is the real transformation. You stop managing fires and start leading the vision. You stop being a manager inside your business and start leading it, and growing the people in it into leaders of their own.
And when it works, it holds without you. The best version of this I've seen was one I helped build myself: a team that learned to lead itself. When I stepped back, they kept making it better.
Where to start
If you recognized yourself in the first few paragraphs, the instinct is to fix it by working harder: tightening up, staying later, pushing through. Don't. Working harder inside the same design just makes you a more efficient bottleneck.
The first move is quieter, and more honest: find out where your time actually goes. Not where you think it goes. Where it actually goes. Almost every leader I work with is closer to the bottleneck than they believe, and the gap between the two is the most useful thing on the table. You can't redesign a system you can't see clearly.
That's what a Leadership Load Review is for. We map where your hours are really going, which loops keep routing back through you, and the first few changes that would let them close somewhere else, so your team starts carrying what's theirs, and you get your time back for the work only you can do. No overhaul. Just a clear picture, and the first moves.
And it almost doesn't matter what you're building toward. Maybe you want to grow with real ambition: scale it, or pass down an enterprise that outlasts you, a legacy your family carries for generations. Maybe you want to keep it small on purpose: protect the culture you've built and love the work every day, for as long as you choose to do it. Or maybe you want a life that isn't swallowed by the business: to stay connected and run it well, while the people inside it carry it for you.
The destination changes. The work doesn't. Every one of those futures runs through the same shift: a business that closes its own loops, a team that owns its own work, and a leader who's become the space around them instead of the bottleneck in the middle.
You didn't build your business to become the part of it that can't be removed. Whatever you're building it toward, the work is the same—and it starts the moment you can see clearly where everything routes through you. Let's get you back to it.
.png)
