Why am I still the bottleneck, even though I delegate?

10:34am. Pieter taps his fingers on the coffee machine, willing his espresso to express faster. He scans the day's calendar: a rainbow cake of layers covering the whole day. Lunch will get eaten in four separate courses while running between meetings, as usual.

During the slot planned for board prep, he notices a Slack thread going sideways. The new landing page isn't converting and three people are debating the headline. He sees the page is selling to a different buyer than the ads are targeting, and rewrites the section on the spot. Twenty minutes of flow state later, it’s done. He was always good at copywriting. The team would have workshopped it for a week and still be arguing about which buyer to pick. Shipped, moving on.

Three more interruptions later, and a couple more quick fixes, and it's gone noon. He still hasn’t started the board prep. It'll move to tonight, after the kids are down. They’ll get a shorter story than normal.

He's good at this. Fixing things fast, himself. That's the part that's started to nag at him. He keeps thinking he needs another manager, and keeps not doing it, because it's hard enough keeping the four he has on the same page, and every one he's hired has added more ambiguity than removed. One more might be one too many.

If you're a founder of a startup that’s grown past forty people, every day is different, but there’s a recurring theme. The "quick question" in Slack that isn't quick. The decision that's been waiting on you since last Tuesday. The constant busyness of growth that keeps you from growing your business. You've become the bottleneck.

Why scaling makes the founder bottleneck worse, not better

You've done the hard part. You found product-market fit, proved it enough to raise a Series A, then a Series B. You’ve got the team and the resources to execute, and customers are beginning to queue up.

The next bit should be easy. It’s “just execution”, isn’t it?

But despite sprinting through every day, everything is way too slow, because you’re still the bottleneck. The company is built to run through you. For a long time, that was the right way: while searching for product-market fit, you need agility and all the context in one head - the founder's. But now you're scaling up, and you need to share the decision-making out so it all goes faster.

You hired managers - good ones. You delegated everything you could. For a while you worried that you’d have nothing left to do except look at dashboards and strategise.

But each new hire arrived with their own context and the instincts they honed elsewhere. Despite regular vision and strategy workshops, weeks setting OKRs, and endless alignment meetings, they still feel like a herd of highly motivated cats following different mice. They each work from a slightly different read of where the company is going. Hard decisions get passed back to you, and ones you thought were resolved get reopened again and again.

Your throughput is fixed; the queue isn't.

And the cost isn't just the queue. Every time something stalls, waiting on you to get it moving again, it chips away at momentum. The team learns to wait for you. You learn that everything depends on you as the founder and ultimate decision-maker. What was meant to be theirs becomes yours again, and you both feel it. Your head fills up with details, not strategy, and you wonder if you’re micromanaging. It's exhausting.

Every change is a week of progress not made, and often a worse decision for having gone back and forth. Every week of progress not made burns runway. Customers aren't waiting. Someone else is building for them, and every time you lose a week, a competitor banks a small win, and the gap widens. Breakeven slips further out of sight.

—

How many decisions are waiting on you right now? 

How many need you?

—

It’s not about delegation, it’s about shared strategy.

Delegating a small project is fairly easy because there are clear boundaries to decision-making. You explain your expectations, the parameters, some guidelines, and give whatever context the project needs.

When you’re delegating something really big, it’s different, because so many of the decisions have interdependencies with other areas. You can’t just delegate that area to someone without them sharing enough context with all the other people they need to interact with. And the best way to organise that context is through a strategy - it gives a narrative framework for the context that people can understand intuitively.

But it’s not enough that the strategy in your head ends up in theirs. If you broadcast the strategy, the message will land differently in each person’s mind. Without anyone being aware they are doing it, they will interpret and adapt it as they go to fit in with the beliefs and context they have. Delegating the big stuff requires a shared strategy, not five different versions tugging people in subtly different directions.

It goes deeper than that, too. The best strategy for your company may not be the one that is in your head. Each of your leaders knows something you don't, or has an insight that could change things for the better. That's why you hired them. All of that needs to come together into one cohesive whole that is better than its parts.

You can see the gap in the small things. The same question, answered three different ways to three different people. A decision you thought was clear gets reopened a fortnight later. Two teams building toward goals that conflict. It looks like a hundred small misalignments, each easy to fix, but like whack-a-mole, they keep coming up until you’ve got that shared strategy.

A shared strategy is not just better, it holds across different leaders in different situations. Decisions get made the way you'd make them, by people who aren't you, because they're working from a shared picture. And because they helped build it, it sticks.

Try this with your leadership team

Here's the test: Ask each of your leaders to write down the strategy as they understand it. Half a page, on their own: the market your customer is in, the problem they have that nothing else solves, what you're building to solve it, and why that’s going to beat the alternatives.

Read them side by side. They'll differ from each other, and they'll differ from what’s in your head. Some will name something true you hadn't considered. Some will show they are missing context you’ve had. That spread between people who all thought they knew the strategy is the thing routing every decision back to your desk.

Don't rush to correct the gaps. The spread is the raw material. Somewhere in there is a sharper strategy than the one you walked in with, but only if you treat the differences as information, not error.

When Pieter ran this with his team, the answers came back further apart than he expected. Marketing was writing for an enterprise buyer: procurement, demos, a signed contract. Product and Pieter had been moving towards self-serve, the kind where someone puts in a card and expenses the first month. They were halfway into a Product Led Growth motion without ever agreeing what it meant or who it was for. No wonder the same questions kept landing back on his desk: pricing, the landing page, which leads sales should chase. Every one of them was really the same question, and only Pieter was holding both halves.

He brought me in to run a facilitated strategy alignment session with them to bring together what the team already knew into one clear picture. What came out wasn't either side's version. Self-serve was the way in, the motion that won individual users one card at a time. Enterprise was the expansion, the named-account upsell once a company had enough users inside to make the case obvious. Neither marketing nor product had been wrong. They'd each been holding one end of a strategy that only made sense once you saw both at once.

That one picture changed what product built next, who marketing wrote for, which accounts sales worked, and in what order. None of them could have drawn it alone. And once they all had it, the decisions that used to land on Pieter's desk started resolving without him. The next landing page draft needed only a light review. It was already pointing the right way.

They didn't need a strategy change. They needed the whole team in one room, getting clear on the same picture. And the picture didn't expire when that decision did. The next time leaders pulled different ways, they had the same shared view to settle it from, and it didn't route back to Pieter. The session solved one problem. What it left behind solved the next ten.

The reason this is hard to catch is that every individual decision you make is good. You're not getting the calls wrong. The strategy in your head is sound. So nothing feels broken. The gap only shows up in aggregate, in the drift between what you decided and what got built, and aggregate drift doesn't show up in any one meeting.

—

A few questions to sit with:

• How many decisions are waiting on you right now? How many need you?

• When did a major decision last get made without you, and stick?

• If your reports each wrote down the strategy as they understood it, how many different versions would come back?

—

What changes — and why it's coaching, not consulting

Right now it can feel like spinning plates, keeping everything up by hand because the moment you stop, something wobbles, and everything falls down in a heap of sticky tape, string and broken plates.

Picture the other version.

Your exec meetings are about the things that matter: a real change in direction, new data, where to put resources, how to unblock thorny problems. Substantive debate you want the team in. Not re-running last quarter's settled arguments, not clarifying things you thought you'd already decided. When you delegate responsibility, it's clear what needs to be done, how it fits into the overall vision, and how it will be reviewed. When they disagree on something, there's a real debate to be had, and it's worth having.

The executive team starts to feel like an extension of your own brain. More bandwidth in more rooms at the same time. Your week has room in it again for clients, for deep work, and for building the next big thing. Your days are predictable enough that you have time to think, even when there’s an emergency, because your team can be trusted to handle it and pull you in when it matters.

And you're doing all of it in your own words. Your strategy, your ideas, your culture, not a copy of someone else's strategy you don't fully believe in, or an operating system copied from another company that doesn’t quite fit the culture you’re building.

That's the work I do. This isn't about installing someone else’s playbook or adopting their strategy. The strategy is already yours, and your team's. The work is getting it into the open and aligned, so the company runs on all of you. Not a better operating system. A better way to lead.

A few months on, Pieter still has a full calendar. The difference is what's on it. Fewer fires that only he can put out, more of the work he's actually there to do. He finally made the hire he'd been thinking about for a year. The difference this time: there was one strategy to hand her, not five interpretations to reconcile. She was calibrated in weeks, not fighting him for months. Hiring her removed ambiguity instead of adding it as it had before.

The hard problems haven't stopped coming. They've stopped routing through him by default, because his team is working from the same picture he is. They make the calls he'd make, and the ones they bring him are the ones that genuinely need him.

He's stopped being the thing the company runs through. And the next stage of growth doesn't feel like something he has to hold together on his own. The leverage finally compounds, instead of the problems.

If that's your calendar too, let's have a conversation. Not a pitch. A working call, to find out whether the thing slowing your company down is the thing you think it is.

A note on Pieter: He's a composite drawn from some of the founders I've worked with, not an alias of any single one of them. The details are made up, but the story is representative of real engagements.