The Founder Bottleneck You Can't See From Inside
Every recurring decision that unnecessarily needs you is a ceiling on the business. Find the ones that do not require founder judgment this week, write the standard, and hand them off.
By James Schramko · Updated August 2026
Purpose
Founders build their businesses by making one decision after another. Early on, that is the job. Years later, many of those same decision paths still run the show. Nobody ever rebuilt them. This playbook shows you which decisions still land on you, and why you cannot spot that by feel. Then it shows how to move those decisions onto a clear standard instead of working longer hours.
The Problem
You built every path this business runs on. Pricing exceptions, hires, content approvals, the call on a client pushing back. At some point you were the only person who could make those calls well. So you made them, and the team learned to bring them to you.
From where you sit, that just looks like how the business runs. You are busy, you are deciding things, and the day is moving. That is the read from inside.
James once found his web team rolling out security patches across roughly a thousand client sites. They were doing it in alphabetical order. Nobody built that order to cause harm. It was just the order the list came in, and it had run that way for years. His own site was the one the money depended on most. It sat well down the alphabet. The fix was to reorder the list by financial risk instead of by the letter A.
Founder decision paths usually look the same from the inside: sensible, settled, running fine. Built on an order nobody looked at again once the business outgrew the reason for it. The read comes from measuring what happens when a decision needs making. How familiar the path feels tells you nothing.
The Self-Diagnostic
Run this over the next week. Write it down as it happens instead of relying on memory afterward.
Decision latency
Pick five decisions that land on you this week. A pricing call, a hire, a content approval, a client exception, a vendor choice. Log the time each one was raised and the time you decided it. That gap is decision latency. If it runs in days rather than hours, the business is waiting on your calendar more than on your judgment.
Escalation count
Count how many things reach you that a capable team member could have decided without you. The test is whether they knew what you would say. Skip the ones that truly need your judgment. Count only the ones where you would have said yes anyway. Or where the answer was obvious once someone looked properly. That count is your escalation load. It is the clearest single number in this diagnostic.
The day-off test
Take a real day off, phone away. Log what truly stops moving because nobody else held the authority to move it. Keep that separate from what simply feels stressful to be away from.
James has missed only three or four calls in thirteen years running his Mentor group. He has woken at 2am rather than let a call drop. He skipped outright only on the rare occasion there was no internet at all. The one time he handed the calls to someone else was across two trips to the Maldives. He paid a trusted member of the group to run them. She already knew how the group ran and had the context to make the calls herself. It was the first time in thirteen years anyone else had run his calls. There were zero complaints. Every decision inside the call could be made without James. It needed someone trusted, informed and clearly authorised to run the standard.
What stalls during your day off shows where the authority, the context or the skill still lives only with you.
Re-Homing Decisions: The Process
Step 1: List what lands on you
Pull the list straight from the decision latency and escalation logs above. That gives you a real list instead of a guess.
Step 2: Write the standard, not the answer
For each recurring decision, skip writing down what you would decide this time. Write the rule that produces the right answer every time. "Refund under $200, approve on the spot" is a standard. "Ask me" is a bottleneck with a different name.
Step 3: Flip the default
The strongest re-homing move is to remove the approval layer you already have. Adding a new one is the weaker move. James runs an internal Slack channel called for-approval. The team posts anything going out publicly there: emails, blog posts, reviews. It publishes on its own after a set delay unless James steps in. His own description of the change: it went from needing his action to make something happen, to needing his attention to stop it. Most of what used to need a yes from him now only needs a no. Most of the time nobody needs to say either.
One boundary on this move. Keep the approval step for decisions you cannot undo, that are regulated, that carry high value, or that could hurt your name. The aim is to remove routine approvals while the real controls stay in place.
Step 4: Build in a second owner, on purpose
A standard that lives only in your head is a memory. Early in his career, James was meant to be cross-trained by the person in the same role in a sister division. That colleague died in a car accident before the handover. James became the only person in the company who could cover the work. He carried both workloads overnight. He calls the lesson the NOAA principle: two people should know every task. For a founder's decisions, that means every standard you write down gets a second person who can run it without you. A document that just happens to exist does not count.
One founder who worked through this with James wrote a delegation document before a long trip overseas. It set out clearly what the staff member could decide and how far. That person had never carried that kind of authority before. They ran with it and thrived. The founder's read afterward: the document had done the founder's job for him. The capacity it revealed had been sitting in the team the whole time. It was waiting for the structure to change.
What Changes
Once decisions carry standards and owners, decision latency drops. Nobody is waiting on your calendar. Escalation count drops, because most of what used to reach you never needs to. The day-off test stops being a test. It becomes an ordinary day off.
On my podcast, Mandy Ellison walked through the case of a service business owner. He was carrying $250,000 in uncollected invoices and working eighty-hour weeks. That included a twenty-to-thirty-hour weekly scheduling bottleneck only he could manage. He started requiring payment before further work, and raised his fees with zero pushback. Cash flow improved. He was then able to recruit an operations manager who had turned him down for five years. That freed those twenty to thirty hours each week.
James once described a well-designed operation as steering a Formula 1 car at 350 kilometres an hour with one finger on the wheel. The business moves fast, and the standards and managers carry the load.
The business moves faster once you stop being the bottleneck. Decisions stop waiting in a queue with only one person in it.
Quick Reference
- Decision latency: how long does a decision wait for you?
- Escalation count: how many decisions reached you that a standard could have handled?
- Day-off test: what stopped because authority or context lived only with you?
- Re-homing: write the standard, assign authority, train a second owner, and replace approval with exception reporting where it is safe to do so.
This playbook pairs with The Load You Can't Hire Your Way Out Of. This one asks which decisions should leave the founder. That one asks which decisions should stay with the founder and be tested from outside. They answer opposite halves of the same question.
If you want a hand working out which decisions in your business are yours to keep, that is the work we do together in Mentor.