The Founder's Grip

Nothing moves without one person's approval, and everyone else has learned to plan around it. The people who couldn't live with the wait already left.

Nothing significant happens here without one person's approval. You've learned to plan around it, building in the extra week, timing your ask for when they're not traveling, mentioning something twice before you expect it to actually move.

That person isn't malicious, and they're usually not even wrong when they finally weigh in. They're just overextended, hard to reach, and often making the call on information that's a week or two out of date by the time it gets to them. You've stopped being surprised by the lag. You've started building it into your own timelines as a fixed cost of doing business here, the way you'd account for a slow vendor or a known supply delay.

The Structure Behind the Bottleneck

It's tempting to read this as a personality issue: this person just needs to let go, needs to trust the team more. That's rarely the whole story, and treating it as one usually leads to interventions that don't stick. The approval chain that runs through one person wasn't built on purpose, most of the time. It's just how the organization worked at a smaller size, when one person having full context on everything was a genuine advantage rather than a constraint. Nobody sat down and decided that every contract, every hire, every meaningful decision would route through a single desk. It simply never got redesigned once the organization outgrew the size where that structure made sense.

You're not dealing with someone who enjoys the control for its own sake, in most cases. You're dealing with a structure that never got rebuilt once it stopped fitting the organization it was serving. Structures don't rebuild themselves just because they've become inconvenient.

What You've Already Adjusted For

You've probably stopped bringing certain things forward at all, not because they don't matter, but because you've quietly weighed whether raising them is worth the wait, and increasingly the answer has been no. A contract that sits two weeks because they were traveling. A hire that falls through because the offer needed sign-off during a week they were buried in three other decisions and yours wasn't the one that got attention. You've learned to route around the bottleneck where you can and absorb the delay where you can't, and neither one of those workarounds is actually free. They cost you time, they cost the organization opportunities that had a shelf life, and they cost you some amount of trust in a process you've learned not to rely on.

Why the Senior People Keep Leaving

The colleagues who couldn't live with this have already left. Not loudly, and rarely citing the bottleneck directly in an exit conversation, because naming it plainly tends to feel like a criticism nobody asked for on the way out the door. They ran a quieter calculation instead: how much of their actual judgment is being used here, day to day, and is that going to change in any meaningful timeframe. When the honest answer was no, they took that judgment somewhere it would be used, and they usually gave a cleaner, more diplomatic reason for the move. If you've watched more than one strong person leave this way, in relatively close succession, that pattern is worth naming plainly to yourself, even if nobody above you has done it yet.

The Shape It Takes Day to Day

Decisions stall specifically waiting on one person, not on the work itself. The team has done everything it can with what it has. The remaining step, every time, is someone's calendar opening up.

Strong hires don't last long in this environment. They arrive expecting to use the judgment they were explicitly hired for, and within a few months discover how little of it the actual structure permits them to exercise.

People have quietly started working around the approval chain rather than through it. Informal sign-offs, decisions mentioned only after the fact once they're already in motion: the organization adapting to a bottleneck nobody has named out loud, one small workaround at a time.

Hoping They'll Let Go First

Hoping the person at the center eventually delegates more, on their own timeline and at their own initiative, usually means waiting indefinitely. The incentive to hold on tends to feel considerably stronger from inside that seat, where letting go feels like losing control of something you built, than the cost of holding on ever registers from the outside. If you're in a position to actually influence this rather than just absorb it, the more useful move is proposing one specific, bounded decision category to release first, not asking them to trust the team more in the abstract: something genuinely low-stakes, concrete enough that a "no" would require an actual stated reason rather than a reflexive one, and small enough that testing whether the structure holds without their sign-off doesn't feel like a referendum on their leadership.

If you're not in a position to propose that, the honest read is this: the pattern you're watching won't resolve itself on any timeline you can plan around, and the same calculation your colleagues already made is available to you too, whenever you decide it's worth running.