Start by recording the decisions that come back to you. Pick one recurring decision, agree who owns it, what they can decide and when they need your input, then test the handover on real work. You reduce the bottleneck when your team has the authority, information and capacity to act.
This usually becomes commercially important once a founder-led business reaches roughly 20 to 50 employees. The team is capable, but work still returns to the founder for context, permission or rescue. Growth adds more decisions, and the founder becomes the limiting factor.
1. Record five decisions that came back to you this week. Write down who asked, what they needed and what happened while they waited.
2. Find the reason for each return. Check ownership, authority, missing information, capability and competing commitments before deciding what to change.
3. Choose one recurring decision to hand over. Start with a category the manager can handle within your existing business rules.
4. Agree one owner and the outcome. Describe what a sound decision should achieve and who needs to hear about it.
5. Set decision limits and escalation triggers. Name the exceptions that need your involvement so the owner can recognise them.
6. Provide the information and capacity to act. Check access, skills, workload and how the owner resolves conflicting priorities.
7. Test the agreement and review the result. Use a suitable real case, examine what still came back to you and adjust before widening the responsibility.
Use the free Seven-Day Decision Handover Plan to record one decision, its owner, limits and review. It includes a fillable worksheet and worked example.
For a closer look at what is sending decisions back to you, use the five-decision ownership review. It helps you examine actual returns with your managers before agreeing one handover.
Founder dependency is not simply being busy. It is a structural condition: important outcomes slow down or become less reliable when the founder is unavailable.
Common signs include senior people waiting for approval, decisions being reopened after meetings, clients escalating directly to the founder, priorities changing without a clear mechanism, and managers delegating responsibility upward when information is incomplete.
The founder often responds by becoming more available. That keeps the business moving today but strengthens the dependency that constrains it tomorrow.
Delegation fails when responsibility moves but authority, information and decision boundaries do not. A manager can own an outcome in name and still need the founder to approve the choices that produce it.
Effective delegation therefore needs four things: a named owner, a clear outcome, explicit decision rights and a defined escalation threshold. Without those, delegation is task distribution rather than operating independence.
Use your five-decision log to look for repeated causes. Is ownership unclear? Is authority missing? Does the manager lack information, experience or capacity? The next change depends on what you find.
Next, define who can decide what without you. Set thresholds for spend, client commitments, hiring, pricing and operational exceptions. Make escalation triggers observable, not subjective.
Install a management rhythm that separates routine operating decisions from genuine strategic choices. A weekly operating review should expose performance, risks and unresolved decisions early enough for the team to act, without turning the meeting into another approval queue.
Finally, improve operational visibility. The founder should be able to see whether the business is on track without personally collecting the story from each department. Useful reporting connects measures to named owners, expected ranges and agreed responses.
Control does not come from making every decision. It comes from knowing which decisions matter, who owns them, what limits apply and how a poor outcome will be detected. Clear governance gives the team freedom inside boundaries while preserving the founder's control over genuinely consequential choices.
Begin with one recurring decision category. Transfer the decision right, agree the evidence the owner will use, set an escalation threshold and review outcomes after four weeks. Expand only when the mechanism works.
Illustrative example: a customer asks to move a delivery date. The delivery manager currently checks with the founder every time, even when there is an available slot.
The handover agreement could let the manager offer a date within confirmed capacity, provided it does not change the agreed price, scope or another customer’s commitment. Capacity clashes and commercial changes follow the named escalation route. The founder and manager agree those boundaries before using them.
Give the manager access to the delivery schedule and a route for resolving conflicts. After a suitable case, review whether the customer received an answer, whether commitments were kept and whether the same approval still returned to the founder.
A fractional COO can help when the problem is not a lack of ideas but a missing operating system: unclear accountabilities, weak management cadence, inconsistent cross-functional execution or decisions that keep returning to the founder.
The useful test is whether the support builds organisational capability. If the consultant merely becomes another person who coordinates everything, the dependency has moved rather than reduced.
The right measure is not how many days the founder can take off. It is whether the business can make sound decisions, maintain operational control and keep priority work moving without routine founder intervention.
Antony Draper Advisory helps founders of UK businesses build that capability. The Founder Independence Assessment identifies where the business still relies on the founder and which operating changes are most likely to reduce that dependency.
A fillable decision handover worksheet, worked example and conversation prompts.
Discuss the ownership and handover problems behind recurring escalations.
Explore ongoing senior operating support alongside your team.
Examine five actual decisions that returned before agreeing one suitable handover.