You book a week off. By day three, your phone is full. A client wants to renegotiate scope. A manager isn’t sure whether to authorise a £3,000 supplier invoice. The operations team is holding on a hire because the salary sits above what anyone else can approve. You answer from a sun lounger. Nobody thinks that is strange. But it tells you something important about how your firm actually runs.
A 2023 Barclaycard survey of 1,000 UK SMEs found that 53% of business leaders felt personally overwhelmed by daily decisions, and 38% said that volume was actively constraining growth. The constraint in those businesses was not strategy, talent, or market opportunity. It was the decision-making capacity of one person.
What is the founder bottleneck?
The founder bottleneck forms when all significant decisions flow back to one person because the information needed to decide is locked in their head and no documented criteria guide the team. Asking the founder becomes faster than guessing, and the queue builds invisibly until it caps the firm’s growth. Scaling Up’s research on high-growth firms places this constraint typically at the 10-to-20 employee mark.
Harvard Business Review identifies this as one of the primary reasons owner-managed firms plateau: capacity to decide becomes the ceiling, ahead of market demand or talent. The mechanism is structural. When a firm grows beyond one person’s direct oversight, it needs decision infrastructure to replace the informal “ask the founder” system that worked at ten people.
Research on managerial decision patterns suggests that up to 60% of recurring decisions in small firms are candidates for standardisation: discount approvals, project scope changes, spend authorisation within a band, client complaint resolutions, and hiring below a salary threshold. These decisions repeat weekly or monthly. Documenting the criteria for them is the first act of building a firm that runs without you.
Why does it slow your business down more than you realise?
The cost extends well beyond your diary. Microsoft’s 2023 Work Trend Index found that leaders spend an average of 32% of their working week on low-value coordination tasks, including routine approvals, status updates, and queries that documented processes could handle. That is roughly one and a half days every week spent making decisions your team could make if the criteria existed in writing and the authority was clear.
Be the Business, a UK productivity organisation that works with owner-managed firms, found that businesses where owners delegated operational decisions were 20% more likely to report above-average productivity. The condition mattered: the gain appeared only when delegation was paired with clear objectives and feedback loops. Simply handing over decisions without the surrounding system produced inconsistent results, with authority often recentralising within months.
There is also a slower cost that compounds over time. When every decision comes back to you, your team stops developing decision-making capability. They get better at managing upward rather than thinking independently. A firm that has trained its people to await approval is harder to sell, harder to scale, and considerably harder to step back from.
Where do the daily decisions actually jam up?
The decisions that create the bottleneck are concentrated in a predictable set of categories for services firms in this size range: pricing and discount approvals, scope change sign-offs, spend above a certain threshold, key hiring decisions, client complaint resolutions, and supplier or vendor changes. McKinsey’s research on decision rights identifies these as the areas where unclear ownership produces escalation by default, with decisions flowing upward regardless of their actual complexity.
The practical fix has two parts. First, list the ten recurring decisions that currently require your sign-off, and categorise each by type: standard process decision, judgement call, or regulated responsibility. Second, establish explicit authority tiers. A project manager can approve scope changes up to £2,000 or 10% of project value. A department head can authorise spend up to £10,000. Beyond that, the decision escalates. The thresholds are yours to set; the principle is that every tier is documented and tested before the founder steps back.
Atlassian’s research on internal documentation shows that teams with well-maintained playbooks and wikis report roughly 25% fewer blocking questions to senior leaders. The documentation doesn’t need to be comprehensive to be useful. A one-page decision guide covering the three or four most common scenarios for each decision type is enough to start.
When does delegation actually stick?
Delegation fails when it is a one-off handoff rather than a system. Be the Business research shows that firms where owners delegated without pairing the transfer with clear objectives and feedback loops saw authority recentralise within months. For delegation to hold, you need documented decision criteria, explicit spend and risk thresholds, and a weekly leadership rhythm in which decisions are reviewed and the team builds confidence in its own judgement.
Two failure modes are worth knowing before you start. The first is under-developed managers. Be the Business identifies management capability as the key mediator between delegation and performance gains. If your team hasn’t been developed to hold decisions, handing them authority creates noise rather than relief. Leadership development is a parallel workstream, not a reason to delay.
The second failure mode is the shadow veto. Research on decision patterns shows that when founders retain an informal approval on every significant decision, team members learn to anticipate the founder’s preferences rather than applying documented criteria. The playbook exists on paper, and the bottleneck hasn’t moved. Fixing this requires a genuine practice of staying out of decisions that sit inside someone else’s defined remit, including the discipline of letting a decision you would have made differently stand.
What does the 90-day shift actually look like?
A 90-day window is a realistic timeline for materially shifting decision ownership in a 5-to-50 person firm, based on Markinly’s founder transition framework and Human at Scale’s practice with professional services businesses. The sequence runs in three phases: auditing your decision load in weeks one to four, building the infrastructure of documented criteria in weeks five to eight, and transferring authority with a deliberate stress-test in weeks nine to twelve.
In the first month, track every decision you make and categorise it: recurring process, one-off judgement, regulated responsibility, or strategic choice. Microsoft’s Work Trend Index data suggests roughly a third of a founder’s week sits in that recurring-process category. That is where the release is.
In months two and three, document decision criteria for the five to ten recurring decisions that typically land on your desk each week. Set explicit authority thresholds. Build playbooks where they help. Then step back deliberately: a planned three-to-five day absence is a diagnostic, not a reward. Review what broke and adjust the criteria before you extend further.
For regulated firms, the 90-day plan carries a compliance dimension. The FCA’s Senior Managers and Certification Regime requires clearly allocated decision-making responsibilities; you cannot decentralise regulated decisions without documented oversight structures. The NCSC’s guidance on board-level responsibilities similarly expects pre-defined incident decision chains rather than ad-hoc founder calls. The ICO expects documented human oversight for any AI-assisted decision-making involving personal data. In a regulated services firm, the documentation you build for this transition is also what your regulator expects to see.
The founder who cannot leave is a firm that hasn’t been designed to run without them. Decisions don’t get simpler as the firm grows, but the criteria for making them can be written down, authority can be distributed, and your role can shift from approving everything to building the system that handles it. If you’re working through that transition and want a second view, Book a conversation.
