Founder Dependency FAQ

Start by identifying where your involvement is still required: decisions, approvals, client communication, handovers, follow-up or knowledge that only exists in your head. The practical goal is not to remove you from the business. It is to make one important workflow clearer, more visible and easier for the team to run.

This usually points to unclear decision rights, missing context, weak handovers or a lack of confidence about what happens next. A team may be capable but still escalate routine questions because the boundaries and information are not clear.

Begin with one recurring workflow rather than trying to redesign the whole company. Map how the work actually moves, clarify ownership, document the decisions and handovers that matter, and give the team practical next steps and boundaries.

Start with repeatable work that consumes your attention but does not require your unique judgement every time. Look for recurring approvals, follow-up, client onboarding steps, reporting, handovers and routine decisions. Delegation works better when the expected outcome and decision boundaries are clear.

Delegation is not the same as abandoning oversight. Define the outcome, the owner, the information they need, the decisions they can make and the situations that should be escalated. Then use a visible review point instead of checking every step.

Ownership becomes practical when people know what they are responsible for, what good completion looks like, which decisions they can make and when to ask for help. If every route back to the founder stays open, ownership remains unclear even when tasks have been assigned.

Document the real workflow as it happens: the trigger, the outcome, the steps, the owner, the information required, common exceptions and the next handover. Start with the workflow causing the most repeated questions or founder involvement. A useful guide is better than a large manual nobody uses.

Not every task needs a formal SOP. The best starting point is a short, usable guide for work that is repeated, easy to get wrong, dependent on one person or difficult to hand over. The format should fit the team and the work.

Capture the explanation once in a form the team can use: a checklist, example, short process guide or recorded walkthrough. Then test it against a real task and improve the guide when people get stuck. Training and documentation should reinforce each other.

The business becomes slower and more fragile because people must ask before they can act. Start by recording the decisions, exceptions, relationships, warning signs and judgement that sit behind the task — not only the task list itself.

Track where work waits, repeats, loses context or returns to you. Look at approvals, handovers, client follow-up, unclear ownership and recurring questions. The most useful starting point is usually the workflow creating the greatest pressure now, not the one that looks most impressive on paper.

Test one important workflow while you are less available. Identify what the team cannot find, decide or complete without you, then improve the ownership, information, handovers and escalation rules around that workflow. This gives you evidence of the dependency instead of relying on assumptions.

The Diagnostic is a focused, paid review of one real workflow. It examines how the work moves through people and tools, where decisions, ownership, information or handovers depend too heavily on the founder, and what should change first. It includes a workflow map, dependency points, practical recommendations, a prioritised 30-day action plan and a Roadmap Review.

The current Diagnostic process is designed to run over 7–10 working days and starts at R7,500 for selected pilot clients. The fixed fee is confirmed after the Clarity Call, once the workflow and scope are clear.

You can begin with the Founder Dependency Self-Audit if you want to identify possible pressure points yourself, or book a free 30-minute Clarity Call to discuss the workflow that keeps returning to you.