Why every decision still needs the business owner.
When every decision needs the owner, growth can stall. Understand delegation, decision rights and how to reduce dependency while retaining oversight.
You take a day off. By lunchtime, the phone contains a question about a customer, a request to approve a purchase and a photograph of something nobody can identify.
The business has remained operational. Your day off has entered a more theoretical phase.
Owner dependency is not always a problem with commitment or competence. It can reflect how information, permission and judgement are distributed. This article examines why decisions keep returning to the owner and how to create more independence without abandoning control.
1. When being indispensable limits growth
At the beginning, the owner often knows every customer, every promise and where the spare key is.
As the business grows, that knowledge becomes useful to more people. Eventually, the owner becomes an extremely well-informed queue.
This is a capacity constraint around decisions. More staff can increase the number of questions without increasing the rate at which those questions receive answers.
Identify the recurring decisions that return to you and the work waiting behind them. Distinguish high-consequence choices that deserve your attention from routine matters that arrive through habit.
The objective is to use senior judgement where it adds value, while giving the operation a reliable way to handle the rest.
2. Understand why people keep asking
A manager who asks for permission repeatedly may lack confidence. They may also remember the last time someone said “use your judgement” and then objected to the judgement used.
People learn from the response they receive.
Investigate the conditions around the request. Does the person know the boundaries? Can they access the relevant information? Are they authorised to commit resources? What happens when a reasonable decision turns out badly?
Dependency can be a rational adaptation to ambiguity or inconsistent feedback.
I’d review actual examples with the people involved before prescribing more delegation. Otherwise, responsibility may move while the constraints that prevent independent action remain in place.
3. Separate expertise dependency from permission dependency
Sometimes only you know the answer. Sometimes everyone knows the answer but still needs your signature.
Those are different problems, even when they arrive in the same inbox.
Expertise dependency requires knowledge transfer, training or access to another qualified decision-maker. Permission dependency requires clear authority and boundaries.
Other cases involve coordination: no single person can reconcile conflicting commitments without an agreed route for resolving them.
Classifying the requests helps target the intervention. A procedure cannot replace expertise in every complex case, but an expert should not need to authorise every routine action simply because they designed the procedure.
This is where clearer decision roles can make a practical difference.
4. Give people usable boundaries for decisions
“Spend sensibly” is guidance of a sort. It becomes less useful when sensible means one thing on Monday and another after the monthly accounts arrive.
A boundary should reduce guessing.
Specify the decisions someone can make, the constraints, the information needed and the situations requiring consultation. The boundaries may concern cost, customer impact, uncertainty or commitments to other teams.
Bain’s RAPID framework helps distinguish the person deciding from those recommending, advising or implementing. In a smaller business, the conversation matters more than introducing the terminology everywhere.
Test the arrangement against recurring scenarios. If people still cannot determine whether they can act, the delegation remains incomplete.
5. Make escalation thresholds explicit
Some issues genuinely need the owner. A route that treats every exception as equally important makes that attention harder to obtain.
Your phone should not need to adjudicate every stationery emergency.
Define escalation triggers and the response expected. Include what the person should do while awaiting a decision, especially where customers or essential service may be affected.
An escalation should contain enough context to support action: the issue, implications, options and recommendation where appropriate.
Review patterns. Repeated escalation of the same routine matter may indicate a missing rule, unclear authority or an information problem. Fixing that pattern can reduce future interruption without weakening oversight.
6. Transfer knowledge without attempting to document your entire brain
A thirty-page manual for a five-minute decision can create another dependency: somebody now needs you to interpret the manual.
Documentation needs a practical purpose.
Capture recurring principles, reliable information sources, common exceptions and examples of acceptable decisions. Explain why the boundary exists so people can recognise when a new situation falls outside it.
Pairing, coached decisions and review of actual cases can develop judgement where written instructions are insufficient. Increase responsibility in line with demonstrated capability and the consequences of error.
Avoid assuming every decision can be standardised. The business still needs a route for genuinely novel or consequential matters.
7. Test independence without disappearing
Leaving everybody alone for a week is one way to test the operating model.
It is not always the most informative first experiment.
Start with a defined class of decisions and a supported trial. Agree what success looks like, retain visibility and review the decisions made.
Measure turnaround time, escalations, quality and consequences. A reduction in questions is only useful if people are resolving matters correctly rather than avoiding them.
Include the owner’s behaviour in the review. Reversing decisions without explaining the principle can undo the autonomy the new arrangement was intended to create.
Independence grows through a consistent operating arrangement, not a single announcement about empowerment.
8. Where independent operational support can help
If you are continually translating priorities, settling boundaries and rescuing routine work, the dependency may span the whole business.
A fresh view can help distinguish where your involvement is essential from where the operation needs a better arrangement.
DeaconOps’s Operational Diagnostic can investigate those dependencies. Improvement Projects can support changes to processes and decision rights, while Operational Reviews offer an ongoing sounding board and senior operational input.
That support is not automatically a replacement for an embedded leadership role. The right scope depends on how much authority and involvement the business needs.
Start a conversation if the business can grow its workload more easily than it can grow its independence from you.
Questions about owner dependency
Does delegation mean losing control?
It changes how control is exercised. Clear boundaries, information and review can replace routine personal approval while preserving oversight.
What if my managers are not ready to make the decisions?
Assess the gap and develop capability through suitable support and controlled responsibility. Simply transferring accountability does not create readiness.
Is hiring a senior manager always the answer?
It may be appropriate where sustained leadership capacity is missing. First establish whether the dependency is caused by workload, expertise, unclear authority or several conditions together.
About the author
Dean Cain is the founder of DeaconOps, with more than 15 years’ experience across operational delivery, leadership and regulated environments. Read about the DeaconOps approach.