Identify work that depends too heavily on the founder
Start by observing where work waits for one person. Gather approval requests, repeated questions, postponed tasks and information that exists only in the founder's head. This picture distinguishes decisions that need their involvement from activities that remain centralised through habit or a lack of clear instructions, helping you choose a practical starting point for delegation.
Over a representative period, record interruptions and what was needed to resolve them. It may be enough to locate a document, explain a criterion or approve a change with real customer impact. These cases should not all receive the same solution, because they involve different needs and levels of responsibility within the business.
Begin with recurring work whose result is observable and whose consequences you can follow. If the activity changes constantly or relies on implicit knowledge, document some real cases first. The choice should consider more than what the founder dislikes doing: examine time released, team capability and the value of creating continuity in the company's day to day operations.
Define the result before listing tasks
Clear delegation describes what needs to be completed and how a good delivery will be recognised. Explain context, recipient and relevant conditions before listing steps. This allows the person to understand the purpose of the work and make coherent small decisions, including when a situation appears that the procedure does not yet describe in sufficient detail.
“Prepare the meeting” can mean different things to two people. Naming the required materials, information that must be current and questions that should be identified is clearer. The steps may remain flexible as long as the result and verification criteria are understood by both the person doing the work and whoever follows it.
Avoid making personal preferences the only measure of quality. Distinguish what customers need, what protects the process and what is a matter of style. This reduces unhelpful revisions and leaves room for the team to find better ways of working. When a criterion is mandatory, explain the reason and show an example that makes its application understandable.
Write a procedure someone can actually use
A useful procedure brings together required inputs, main steps, decisions and evidence of completion. It should be easy to find and short enough to support actual work. Begin with a frequent case and add exceptions as they arise, rather than turning the first version into an attempt to anticipate every possible situation before anyone has used it.
Observe someone performing the task and record where they seek information or ask for help. Those moments reveal what the procedure lacks. A document can appear complete to someone familiar with the process while remaining difficult for a person receiving it for the first time. Testing its use is part of documenting the work.
Include properly protected real examples when they help identify the expected result. State where materials live and who can clarify questions. If several document versions exist, choose an authoritative reference and name its maintainer. The team should be able to distinguish current instructions from old notes without relying on someone's memory or searching through scattered messages and conversations.
Make decision boundaries explicit
Delegating work also requires clarifying which decisions the person can make and which require approval. Define boundaries around impact, scope and existing commitments, supported by understandable examples. This reduces both excessive dependence and actions beyond the assigned responsibility, allowing the person to act independently within conditions previously agreed by the team and the person accountable for the work.
Distinguish executing a defined task, choosing between known options and proposing a process change. These require different context. Someone may update a record without approval while needing confirmation for a change affecting price, timing or what was promised to a customer. Naming these distinctions makes everyday decisions easier to take consistently.
When an exception arises, specify what should accompany a request for help: the situation, options considered and consequence of waiting. The founder then receives a prepared decision rather than a question without context. Where the case may recur, use the answer to improve the procedure so the same uncertainty does not keep interrupting work indefinitely.
Follow progress without taking every decision back
Follow up should examine results, difficulties and learning at a frequency appropriate to the risk and the person's experience. Agree review moments and information to present, avoiding constant interruptions. As execution becomes consistent, adjust the level of oversight while preserving visibility over the points that genuinely affect customers, resources or commitments made by the business to others.
Initially, reviewing a first delivery before repeating the task many times can be useful. Explain gaps and criteria during that review so the next attempt improves. If the founder silently redoes everything, the team loses the chance to learn and work remains centralised despite being formally assigned to someone else.
Distinguish an individual mistake from a condition that makes error likely. Incomplete information, contradictory instructions and missing access can undermine anyone's work. Correcting those conditions strengthens the process and avoids attributing every problem to execution. Review records should improve the work without creating a separate control operation whose effort is disproportionate to the task being delegated.
Use a delegation sheet as a starting point
A simple sheet gathers the working agreement in an accessible place. It should show the result, resources, authority, verification and exceptions, with one person responsible for keeping the information current. Use it to start the conversation and confirm understanding through real execution, because filling in fields does not by itself prove that the transfer is complete.
| Field | Information to agree |
|---|---|
| Result | What should be ready and for whom |
| Inputs | Information, materials and access required |
| Responsibility | Who performs and follows the work |
| Criteria | How to recognise an acceptable delivery |
| Authority | Permitted decisions and required approvals |
| Exceptions | When to stop and how to ask for help |
| Review | When to observe execution and update instructions |
Ask the person to explain the task in their own words and identify a situation where they would be unsure. This reveals differences in interpretation before they affect delivery. The sheet can support strategic business planning, connecting selected priorities with the team's actual capacity to execute the work needed to make progress.
Improve the process before automating it
Automation should support an understood process with defined inputs, rules and owners. Before selecting a tool, check whether the task remains necessary and whether it can be simplified. When human execution already reveals ambiguity, automating without resolving it may repeat the problem faster and make responsibility for emerging exceptions less visible to the people operating the business.
Some tasks benefit from a checklist or document template before any integration is built. Others can be partially automated while retaining review at decision points. The page on AI for business owners connects this choice with costs, quality and responsibility, without assuming every recurring task needs an AI system to perform it.
To reduce dependencies and organise your team, use the individual mentoring form. Describe tasks that keep returning to you, who could take them on and what you have already tried. We can use those examples to choose a concrete transfer, define criteria and follow the learning that allows the team to gain operational independence.