A business can have employees and still depend on its founder for almost every decision. The dependency often appears in approvals, customer exceptions and knowledge that exists only in the owner's head. An audit makes those dependencies visible without assuming the founder should disappear from the business.
Follow the interruptions
For one working week, record every request that reaches the founder. Capture the decision, why it came to them, the consequence of delay and whether another person had enough information to act. Separate strategic choices from repeat operational approvals.
Classify each interruption:
- Missing information: the answer exists but is hard to find.
- Missing authority: the team knows the answer but cannot approve it.
- Missing skill: judgement or training is required.
- Genuine escalation: risk or unusual circumstances justify founder involvement.
Fix one dependency at a time
Suppose every small booking change requires approval. Document permitted changes, limits and exclusions. Name the role that can approve them. Trial that authority on a small set of cases and review the decisions, rather than demanding approval for every case forever.
Keep serious complaints, safety concerns and commitments outside delegated limits on an escalation route. Delegation is stronger when its boundaries are explicit.
Repeat the audit monthly. Track repeat interruptions, waiting time and mistakes after handover. A lower interruption count is useful only if customers and staff are still getting sound decisions. The objective is dependable authority across the business, not silence around the founder.