Operations
The founder bottleneck: five signs it all runs through you
In the early years, a founder who decides everything is an advantage. Decisions are fast, standards are consistent, and nothing slips. Somewhere past fifty people the same habit starts to cost growth, quietly, because the company can only move as fast as one person can approve.
The bottleneck rarely announces itself. Revenue may still be rising. What changes is the texture of the work: more waiting, more chasing, more decisions made late or made twice. Here are five signs to look for.
1. Approvals wait for your return
If routine decisions such as a discount, a hire, a supplier change or an exception to process pile up while you are travelling, decision rights were never delegated. They were borrowed, and they come back to you by default.
The test: look at what was approved in the last two weeks you were away, and by whom.
2. Your managers report, they do not decide
Weekly meetings walk through activity: what each team did, what is late. They end without decisions, because the people in the room do not believe they are allowed to make them. The meeting exists so you can decide.
The test: read the last three sets of minutes. Count the decisions, each with an owner and a date.
3. The same problems return
A customer complaint is fixed, then appears again next month in a slightly different form. Each fix was a personal intervention, not a change to how the work is done. You solved the instance; nobody owned the cause.
The test: list the last five escalations that reached you, and ask whether the same type has happened before.
4. Nobody else knows the numbers
You can quote the month's revenue, margin and pipeline from memory. Your leadership team cannot, or they each quote different figures. The business is measured, but only in your head.
The test: ask three leaders, separately, for the same three numbers.
5. You are the escalation path for everything
When two teams disagree, they come to you. When a customer is unhappy, they come to you. You have become the operating system, and an operating system that runs on one person has a single point of failure.
The test: for a week, write down every decision brought to you that someone else could have made.
The order in which to fix it
Trying to fix all five at once usually fails. The sequence matters.
- Write down decision rights. Who can approve what, up to what limit. Most of these decisions are already being made by someone; the document makes it legitimate.
- Install a cadence that decides. A weekly operating review, a monthly business review and a quarterly plan, each with a purpose, an agenda, and a rule that it ends with decisions, owners and dates.
- Give the numbers an owner. A short set of measures, each with a definition, a source and a named person, reviewed in that cadence.
- Fix causes, not instances. When a problem returns, the question becomes what in the process allows it, and who owns changing that.
- Step back from escalations. Only once the first four are working. Stepping back first leaves a vacuum.
This is the work a fractional COO is usually brought in to do: installing the operating system, then handing it to the team so the founder can step out of the middle. For more on the cadence itself, see running an operating cadence without the founder bottleneck.
If you would like a quick read on where your own company stands, the free eight-minute Operations Health Check scores six dimensions of your operating model.