Most business owners will tell you they know they need to delegate more. Fewer of them can say exactly why they don't. Underneath the 'I don't have time to train someone' explanation is usually something closer to: if I hand this over, it won't be done the way I'd do it, and I'll have to live with that.

That's a real fear, and it deserves a real answer rather than a motivational poster about trust. The answer is that 'done differently' and 'done badly' are not the same thing, and confusing the two is what keeps owners doing £15-an-hour work at £150-an-hour opportunity cost.

The maths owners rarely do

Work out, roughly, what your time is actually worth to the business — total value you generate divided by hours worked is a crude but useful starting point. Then look honestly at how many hours a week go on tasks that a £15-an-hour hire could do competently. For most owners the number is uncomfortably high, and it's the single clearest argument for delegating that has nothing to do with trust or personality and everything to do with arithmetic.

A simple framework for what to delegate first

Sort tasks on two axes: how reversible a mistake would be, and how much the task actually requires your specific judgement rather than just your time. Anything that's both low-risk and doesn't need you specifically — data entry, scheduling, routine customer replies, invoicing — is the obvious starting list, and there's rarely a good reason it's still sitting with the owner months into a business's life. Save the high-stakes, genuinely-needs-you work for later, once the muscle of delegating well has actually been built on safer ground.

In practice, for most small businesses that's some combination of: diary and scheduling management, first-line customer enquiries, routine bookkeeping data entry, social media posting against an agreed plan, and any task you've personally done the same way more than a handful of times — repetition is usually the clearest sign a task has become documentable rather than judgement-dependent.

Delegate the outcome, not the method

The instinct is to hand over a task with a precise list of exactly how to do it — which quietly delegates almost nothing, because the thinking still sits with you. A better handover describes the outcome you need and the boundaries that matter, and leaves the method open. That's what actually frees your time, and it's usually what makes the work better, because someone closer to it finds a faster way.

This is harder than it sounds for anyone who's used to being the person who does the task well. The instinct to specify every step comes from a good place — wanting the work done right — but it has the perverse effect of keeping all the actual thinking with the owner while just outsourcing the typing. A genuine handover means being explicit about what 'good' looks like and then tolerating a different route to get there.

If you're still checking every detail, you haven't delegated the task. You've delegated the typing.

Write it down once, use it forever

The handover conversation matters, but it shouldn't be the only record of how something's done. A short written checklist, or a two-minute screen recording of you doing the task while narrating why you're making each choice, turns a one-off explanation into something the next person can follow without you in the room — and something the person after that can use too, without you explaining it all over again. This is the unglamorous bit that actually compounds: the first delegation costs you time to document; every one after that is nearly free.

Start with the low-stakes stuff

Don't hand over the highest-risk, highest-visibility task first and call it a trust exercise. Start with something genuinely recoverable if it goes wrong, let it go wrong occasionally, and build the muscle — yours and theirs — from there. Confidence in delegation is built the same way confidence in anything is built: with evidence, not with a decision to feel differently.

The excuses, and the honest answer to each

'It's faster if I just do it myself' is true the first time and false every time after, once training time is weighed against the hours saved over months rather than the first attempt. 'Nobody cares as much as I do' is often true and mostly irrelevant — the bar is competent, not identical, and competent is usually enough. 'I don't have time to train someone' is the fear talking, not the maths: the training hours are a one-off cost against a permanent weekly saving, and the payback period is almost always shorter than it feels in the moment you're dreading it.

What good delegation actually sounds like

In practice it's a short conversation, not a manual: here's the outcome I need, here's the deadline, here's who to check with if you hit a wall, here's what 'done' looks like, and here's how much authority you have to make calls without coming back to me first. That last part is the one owners skip most often, and it's usually the one that determines whether the delegation actually saves them time or just adds a new layer of questions to answer.

When it doesn't work the first time

It will go wrong occasionally, and that's not proof delegation was a mistake — it's the cost of building a business that doesn't depend entirely on one person. The useful response isn't to quietly take the task back and never delegate it again. It's a short debrief: what happened, what would've made it clearer upfront, and what changes for next time. Owners who treat an early stumble as data get a team that improves. Owners who treat it as proof delegation doesn't work end up doing everything themselves indefinitely.

Common questions

What should I delegate first?

Whatever is low-risk if it goes wrong and does not genuinely need your judgement — that is the entire filter. In most small businesses it means diary and scheduling, first-line customer enquiries, routine bookkeeping data entry, invoicing and chasing, and social media posting against an agreed plan. A useful shortcut: if you have done a task the same way more than about five times, it is documentable rather than judgement-dependent, and it should not still be sitting with you. Deliberately do not start with the highest-stakes work as some kind of trust exercise. Start with something genuinely recoverable, let it go imperfectly once or twice, and build the habit where a mistake costs an afternoon rather than a client.

How do I hand something over without micromanaging it?

Describe the outcome and the boundaries, then leave the method alone. A proper handover covers five things: what done actually looks like, the deadline, who to ask when they get stuck, what they can decide without checking with you, and anything that genuinely must be done a particular way. The fourth is the one owners skip, and it is why delegation so often produces more questions rather than fewer. If you find yourself specifying every step, you have delegated the typing and kept the thinking, which saves you almost nothing. Agree a check-in point up front — at the halfway mark, say — so reviewing progress is scheduled rather than something you do by hovering.

How do I work out whether it's cheaper to delegate a task?

Compare what an hour of your time generates against what an hour of someone else's costs, and be honest about the first number. A business turning over £150,000 on 2,000 hours of the owner's work is running at £75 an hour. A task taking four hours a week is 200 hours a year, so £15,000 of your time, against roughly £3,000 for someone at £15 an hour, plus employer's National Insurance and pension if they go on your payroll, plus the hours it takes to train them. The training is a one-off; the saving repeats every week. That gap, not confidence or personality, is the actual argument, and it is rarely close.

What if I delegate something and they do it badly?

Debrief it — do not quietly take it back. The useful conversation is short and specific: what happened, what would have made the brief clearer, what changes next time. Most first-attempt failures trace back to the handover rather than the person, usually an unstated assumption, no definition of done, or no clarity about what they were allowed to decide alone. Reclaiming the task teaches both of you that delegation does not work here and guarantees you are still doing it in a year's time. Separate done differently from done badly before you react, because they are not the same thing. Only genuinely poor work needs a performance conversation.

Do I need to hire someone to delegate, or can I outsource?

You can start outsourcing this week, and for most owners that is the sensible first move. A virtual assistant, a freelance bookkeeper or a subcontractor can take a defined block of work with no employment obligations attached and no commitment beyond the current month — which is exactly what you want while you are still learning what to hand over and how. Hiring makes sense once the work is continuous, needs someone inside your systems and your culture, and is covered by revenue you would still expect in a bad quarter. Be careful about calling someone a contractor when they work set hours under your direction with no other clients: HMRC judges employment status on the facts, not the label.