Most owners have tried to delegate. They hand a job to someone capable, explain it once, and a week later the questions start. The work comes back half done, or done differently, and fixing it takes longer than doing it. So the owner takes it back, and concludes that “it’s quicker if I just do it myself.”
That conclusion is usually wrong about the cause. The person wasn’t the problem. What was handed over was a task, while the knowledge needed to do it well stayed in the owner’s head: the order of steps, the exceptions, what “good” looks like, and which customer needs special handling.
Delegation that sticks hands over three things at once:
Miss any one and the work drifts back to your desk. This is why delegation is really a systemising problem (see how to systemise your business), and why it sits alongside removing key-person dependency and fixing the operational problems that appear as a business grows.
You don’t need a framework to know you have a delegation problem. Look for these:
Each one is a process that lives in one head: yours. The goal of delegation is to move those processes out of your head and into the business.
For two weeks, write down every task you do, roughly how long it takes and how often it comes up. Don’t filter. Include the five-minute jobs, the “quick checks” and the questions you answer on the fly.
Then sort the list into four groups:
| Group | What it is | Examples | What to do |
|---|---|---|---|
| Repeat | Same steps every time | Invoicing, ordering stock, opening checks, posting on social | Delegate first |
| Judgement within rules | Varies, but follows rules you could explain | Refunds, quoting standard jobs, scheduling staff | Delegate with a written rule and a limit |
| Relationship | Depends on who you know | Key accounts, suppliers you negotiated with | Introduce, then hand over gradually |
| Owner-only | Direction, hiring senior people, big money decisions | Strategy, pricing changes, partnerships | Keep |
Most owners find that the owner-only group is far smaller than they expected, and that the repeat group takes most of their week.
Don’t start with the hardest job. Start with the one that takes the most of your time, comes up most often and needs the least judgement. Early wins matter: they free up hours and prove to you, and the team, that delegation works.
A simple test for each task: if someone followed clear written steps, would the result be good enough? If yes, it’s ready to delegate now. If not, it needs the rules written down first (step 3).
“Good enough” is the right bar. A process that runs at 90% of your standard without you is worth more than one that runs at 100% only when you’re there.
This is where most delegation fails. Owners don’t have time to write a manual, so they explain things verbally, and the knowledge leaves with the conversation.
The fastest way to capture a process is to do it once while recording. Talk through what you’re doing and why, including the exceptions: “if the supplier is out of stock, we call this one instead”; “never refund over $200 without a photo”.
From the recording, produce a standard operating procedure (SOP): numbered steps, screenshots, and the decision points. Our guide on how to create SOPs with AI walks through doing this in minutes, and the free SOP template works if you’d rather write it by hand.
A good delegation SOP answers five questions:
| Question | What to write | Example: “Order stock” |
|---|---|---|
| What starts it? | The task and its trigger | Every Monday, or when a shelf drops below its marker |
| What does done look like? | The standard, with an example | Order placed by noon, confirmation saved to the orders folder |
| What are the steps? | In order, with screenshots where there’s a screen | 1. Count the shelf. 2. Check last week’s sales. 3. Order in the supplier portal… |
| What if it goes wrong? | The exceptions | Supplier out of stock: order from the backup supplier |
| What can they decide alone? | The limits, and when to escalate | Orders up to $1,500; above that, ask first |
The last row is the one owners forget. Without a limit, people either ask you about everything or decide things you’d never agree to. With one (“you can approve refunds up to $200 and discounts up to 10%”), they can act confidently and you only hear about the exceptions.
Where a process branches a lot, a process map shows the decisions more clearly than a list of steps. If you’re unsure which format fits, see SOP vs work instruction vs process map.
“Can you do the invoicing?” delegates a task. “You own getting every invoice out by the 3rd and chasing anything unpaid after 30 days” delegates an outcome.
Owning the outcome changes behaviour. The person thinks about the result rather than the instructions, spots problems earlier and improves the process over time. It also makes clear who to ask, which stops questions defaulting to you.
Make ownership visible. Put each process against a named owner on an org chart, so everyone, not just you, knows who looks after what.
Handing someone an SOP isn’t training. Walk through it with them once, let them do it while you watch, then let them do it alone with the SOP open. Expect questions the first few times; each one usually means a step is missing from the document, so add it.
That last habit is what makes delegation scale. Every question answered in the SOP is a question nobody asks you again, including the next person you hire. Over time, your SOPs become training modules and role-based training programs, so new staff learn from the system instead of from you. See how to create effective training manuals for the detail.
The fear behind most owners’ reluctance to delegate is losing control. The answer isn’t to stay involved in the work. It’s to see the result without asking.
For recurring work, turn the SOP into a checklist that’s ticked off each time it runs. You can see that the opening checks were done, the stock was counted and the invoices went out, with times and names, without a single message.
Then agree a short, regular review: a weekly 15-minute look at what went out, what went wrong and what the SOP should say differently. Review the result and the process, not the person’s every step.
Resist the urge to redo work that’s “not how I’d do it”. If the result meets the standard, it’s done. If it doesn’t, fix the SOP or the training, then let them try again. Taking it back teaches the team that delegation is temporary.
| Mistake | What happens | Do this instead |
|---|---|---|
| Delegating the job but keeping the decisions | Every exception still comes to you | Write the rules and limits down |
| Explaining verbally | You explain it again to the next person, and the one after | Record it once as an SOP |
| Delegating only to your best person | They become the new bottleneck | Spread processes across the team, each one written down |
| Handing over without a standard | “Do it properly” means something different to everyone | Show an example of done |
| Checking in constantly | People learn you don’t trust the system | Use the checklist and a weekly review |
| Giving up after the first mistake | The team learns delegation is temporary | Fix the SOP or the training, and let them try again |
If this feels like a lot, start small:
| Day | What to do |
|---|---|
| Monday | Keep a log of everything you do today. |
| Tuesday | Pick the one repeat task that takes the most of your week. |
| Wednesday | Record yourself doing it, talking through the exceptions, and turn it into an SOP. |
| Thursday | Name the owner and the outcome, walk them through it once and set their limits. |
| Friday | They do it alone. You check the result, not the steps, and add anything they asked to the SOP. |
Repeat weekly. In three months you’ll have handed over a dozen processes, and you’ll have the start of an operations manual: the written record of how the business runs without you. When someone with knowledge you rely on is about to leave or change roles, the employee handover document template captures their part of it too.
Delegation fails when it depends on memory: yours, to explain the work, and theirs, to remember it. It works when the business has a system that holds the method, names the owner and shows the results.
Wikidoc brings those pieces together. Record a process once and get an SOP with screenshots, turn it into training, give it an owner on the org chart, and run it as a checklist so you can see it’s done. The work leaves your desk, and the knowledge stays in the business.
Start free and document the first process you want off your plate.
Owners usually hold the knowledge of how the business runs in their heads, so handing over a task without that knowledge leads to mistakes and questions. The work then drifts back. Writing the process down first, with its standards and limits, is what makes delegation stick.
Start with repetitive work that takes a lot of your time and needs little judgement, such as invoicing, ordering, scheduling or routine checks. These are the easiest to write down and hand over, and they free up the most hours quickly.
Keep the work that sets the direction of the business: strategy, major financial decisions, senior hires and key partnerships. Almost everything else can be delegated once it’s documented, including judgement calls, if you write down the rules and limits.
Hand over the outcome with a clear standard, give the person written limits for decisions, and check results rather than activity. Recurring checklists and a short weekly review show you the work is done without needing to supervise each step.
Systemise it: document each recurring process as an SOP, give every process a named owner, train people from the documentation rather than by shadowing you, and use checklists to see the work is done. Over time this becomes an operations manual the business runs on.
