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.

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.

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.

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.