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 are still running the show, and nobody ever rebuilt them. This playbook gives you a way to see which decisions still land on you, why you cannot spot that by feeling, and how to re-home those decisions with an explicit 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 simply 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 had been rolling out security patches across roughly a thousand client sites 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, the most financially critical one in the portfolio, sat well down the alphabet. The fix was reordering the list by financial risk instead of by the letter A.
Founder decision paths usually look the same way from the inside: reasonable, established, running fine, built on an order nobody re-examined once the business outgrew the reason it existed. The read comes from measuring what happens when a decision needs to be made, not from how familiar the path feels.
The Self-Diagnostic
Run this over the next week. Write it down as it happens rather than 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. Measured in days rather than hours, the business is waiting on your calendar, not your judgment.
Escalation count
Count how many things reach you that a competent team member could have decided without you, if they had known what you would say. Skip the ones that genuinely need your judgment. Count only where you would have said yes anyway, or where the answer was obvious once someone looked at it properly. That count is your escalation load, and it is the clearest single number in this diagnostic.
The day-off test
Take a real day off, phone away. Log what genuinely stops moving because nobody else held the authority to move it, 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, waking at 2am rather than let a call drop, skipping outright only on the rare occasion there was no internet at all. The one time he handed the calls to someone else, 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, and there were zero complaints. The business did not need James personally for every decision inside the call. It needed someone trusted, informed and explicitly authorised to run the standard.
What stalls during your day off shows where authority, context or capability 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 is a real list, not 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 removing the approval layer you already have, not adding a new one. James runs an internal Slack channel called for-approval, where the team posts anything going out publicly: 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 requiring his action to make something happen, to requiring his attention to stop it. Most of what used to need a yes from him now only needs a no, and most of the time nobody needs to say either.
One boundary on this move: do not reverse the approval default for irreversible, regulated, high-value or reputationally sensitive decisions. The aim is removing routine approvals while governance stays intact.
Step 4: Build in a second owner, on purpose
A standard that lives only in your head is a memory rather than a standard. Early in his career, James was meant to be cross-trained by the person running the same role in a sister division. That colleague died in a car accident before the handover, leaving James as the only person in the company who could cover the work, carrying both workloads overnight. He calls the lesson the NOAA principle: two people should know every task. Applied to a founder's decisions, that means every standard you write down gets a second person who can run it without you, not a document that just happens to exist.
One founder who worked through this with James put a delegation document in place before an extended trip overseas, setting scope and decision boundaries clearly enough that a staff member who had never carried that kind of authority ran with it and thrived. The founder's read afterward: the document had done the founder's job for him, and the capacity it revealed had been sitting in the team the whole time, waiting for the structure to change.
What Changes
Once decisions carry standards and owners, decision latency drops because nobody is waiting on your calendar. Escalation count drops because most of what used to reach you never needs to anymore. 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 carrying $250,000 in uncollected invoices and working eighty-hour weeks, including a twenty-to-thirty-hour weekly scheduling bottleneck that only he could manage. Requiring payment before further work, combined with a fee increase that met zero pushback, improved cash flow. He was then able to recruit an operations manager who had turned him down for five years, freeing 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 quickly, and the standards and managers carry the load.
The business moves faster once you stop being the bottleneck, because 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.