
The short answer
What to know before you act
Founder dependency exists when routine progress requires your memory, relationships or permission. Start by classifying the decisions that return to you. Transfer a repeatable decision with its boundaries and evidence; keep genuinely strategic or irreversible decisions where the accountability belongs.
- Count decision types, not messages: twenty pings may be one unresolved rule.
- Transfer judgement with the task: responsibility without authority leaves the dependency intact.
- Test absence in stages: an observed handoff is more useful than suddenly becoming unavailable.
Imagine taking a day away from messages. Orders are still arriving, but a quote waits, a refund waits and a team member cannot choose between two priorities. The problem is not simply the number of hours you work. Several different decisions have only one route through the business.
A useful independence test asks what stops, why it stops and whether the founder is adding judgement that genuinely belongs at founder level. The answer may be better information, explicit authority or a standard that somebody else can apply.
Which dependency are you actually trying to remove?
| What you see | What to check | Next move |
|---|---|---|
| Quotes wait for a price | Is there a margin floor and exception rule? | Delegate quotes inside an agreed commercial boundary. |
| Delivery needs founder coordination | Are commitments and blockers visible to an operating owner? | Give one owner a shared dispatch view and escalation rule. |
| Customers only trust the founder | Does account history exist outside private conversations? | Introduce a second relationship owner with complete context. |
| Priorities reset every morning | Are weekly trade-offs and decision rights explicit? | Agree priorities and the conditions that justify changing them. |
A quoting process that keeps returning to the same desk
Hypothetical example · not a client case study
Suppose an industrial supplier sends every quote to its founder, including repeat orders with unchanged terms. The sales lead already knows the customer and stock position, but has no written authority to approve the price. Recruiting another salesperson would add another person waiting for the same decision.
The team separates ordinary quotes from unusual credit, delivery and margin exceptions. The sales lead can approve ordinary quotes within the agreed limits. For two weeks the founder samples decisions instead of approving all of them. They compare turnaround, margin and exception quality; fewer founder messages alone would not establish success.
- 01LogRecord recurring decisions
- 02ClassifyRoutine, exception or strategic
- 03TransferAuthority plus context
- 04ReviewSample outcomes and exceptions
Build one dependable handoff before widening the test
1. Observe a normal week
Log what needed your intervention, who asked, the missing input and the waiting time. Include interventions you made without being asked. Quietly correcting everything can conceal the same dependency as a busy approval queue.
2. Write the decision boundary
State the outcome, owner, available information, authority and escalation conditions. Explain what must never be traded away. Let the receiving owner describe how they would handle a normal case and an exception before changing the workflow.
3. Replace approval with evidence
Agree what you will review and how often. Use a small sample of completed decisions plus a log of exceptions. If the owner still needs your private information to act, fix access to the information before treating hesitation as a capability problem.
Put it to work
Founder dependency handoff worksheet
Work through the four prompts using evidence from your business. These notes stay in this page, are not sent or saved, and disappear when you reload. Copy them before leaving.
Trace the return
Choose one recurring decision that reached you this week. What was missing?
Set authority
Name the owner, permitted range and genuine exceptions.
Run an absence test
Choose a normal operating window and the evidence needed to act without you.
Review independence
Check turnaround, quality and escalations before broadening authority.
Choose your next step
Keep the first handoff small enough to understand. Founder independence grows when decisions remain sound without your intervention, not when the founder simply stops answering.


