From Founder Led to Function Led
By Akkul Dhand · Published 26 October 2026
Move recurring decisions out of the founder’s inbox without losing control of the business.
Who this is for: Founders whose teams keep escalating routine decisions, even after hiring managers.
Delegation works when ownership, authority and visibility travel together. A new job title cannot carry all three.
1. Diagnose before acting
Answer each question with a concrete example or piece of evidence. Mark unknowns openly. This is a discussion aid, not a validated scoring instrument.
- Which five decisions reached you most often last week?
- Did the team lack authority, information, capability or confidence?
- Can each function name one person who owns its result?
- Do people know which decisions genuinely require your approval?
- Can you see outcomes without personally checking every task?
2. Put the method to work
1. Record the dependency
For five working days, log every decision that reaches the founder. Record the decision, who raised it, the delay and the reason it could not be resolved elsewhere. Separate recurring decisions from unusual strategic calls. Start with frequency and consequence, not irritation.
2. Define a result for each function
Give each function a short mandate: the result it owns, its customers, the boundaries of its work and two to four measures. Assign one accountable owner. Map handoffs between functions so that work does not disappear at departmental borders.
3. Write decision boundaries
For the most frequent recurring decisions, specify who can decide, the evidence needed, the limits and the escalation trigger. Use limits relevant to the decision: value, customer impact, timing or risk. Validate them against the business’s actual obligations.
4. Practise before stepping away
Run real decisions through the new owner. Ask for their recommendation and reasoning before giving yours. Observe the first few cycles, close skill gaps and then stop requiring approval inside the agreed boundary. Remain available for defined exceptions.
5. Replace checking with a review rhythm
Review outcomes and exceptions weekly. Inspect a small sample of decisions for quality. Adjust boundaries when evidence warrants it. When an employee bypasses the owner, route the decision back rather than quietly taking ownership again.
3. A worked example
Illustrative example: a sales manager escalates every discount. The founder and finance lead establish a margin floor and a discount authority limit, based on their economics. The manager records the reason for each exception. Discounts inside the boundary no longer wait for the founder; unusual terms still escalate. Review approval speed alongside realised margin, complaints and cash collection.
4. Working sheet
The first row shows how to fill this in. Use the blank rows for your own business. Add evidence links and review dates to your working copy.
| Recurring decision | Accountable owner | Authority and limits | Escalation trigger | Review evidence |
|---|---|---|---|---|
| Routine customer discount | Sales manager | Within agreed margin and discount limits | Below floor or unusual payment terms | Margin, collections and exceptions |
5. Action plan
- Days 1–5: record founder dependencies and select one function.
- Days 6–10: agree its mandate and three recurring decision boundaries.
- Days 11–20: run supervised decisions, then remove routine approvals.
- Days 21–30: review quality, delays and bypasses before extending the model.
6. Check whether it worked
- Routine decisions resolved by the designated owner / total routine decisions sampled.
- Median time from decision request to resolution.
- Rework, margin or service failures after delegated decisions.
Do not celebrate fewer escalations if people have simply stopped reporting problems. Keep a clear route for bad news. The founder should retain strategic choices and material exceptions, not become unavailable.
What you should leave with: One function mandate, a decision register and an agreed weekly exception review.