Delegation that fails: why it isn’t your team or your software

Why the work you hand over keeps coming back to you

A lot of business owners I speak to have a story about the time they handed something over and it came back wrong. Usually one story in particular. It’s often a while ago, and they tell it as if it settled something.

“I’ve tried a dozen times to give other people stuff to do. It comes back and the quality is not good enough. I end up reworking it and doing it anyway. So what is the point of giving it to somebody else?”

And then, almost in the same breath, a quieter version. “I tried to hand it over, but I just didn’t have the time to hand it over properly. So it just fell over. I kind of knew it would.”

That second line is the one I listen to, because it’s often closer to what actually happened.

It isn’t the person, and it isn’t the tool either

What’s interesting is how little it matters who or what the work was handed to. I hear the same story about a new member of staff: “I took Bob on because Bob was already trained in X. But when I asked him to do Y and Z it didn’t work, and I don’t have time to train him for it.” I hear it about software: “I bought that system and it didn’t do what it said it was going to do. I didn’t have enough time to set it up and make sure it did what it was going to do.” And now I hear it about AI, where the drafting got handed over, the output went up, and so did the time spent checking it.

A person, a piece of software, an AI tool. Three different recipients, and the same result every time: it came back, and you did it yourself. When the same thing fails the same way regardless of who it’s given to, the problem isn’t the recipient.

What’s missing in every version of the story is the same thing. Nothing was specified. It’s likely nothing was written down about what good looks like, no worked example, no check to run before it went out, no point at which somebody other than you could say “that’s right”. What you know about how the work should be done is in your head, and the handover didn’t include it. So whoever or whatever received the work was set up to fail before they started, and when they did, it confirmed what you half expected.

That’s the loop. Hand it over with nothing specified. It comes back wrong. Take it back and do it yourself. Nothing gets written down, becauseyou’re busy doing it. Hand it over again, later, with nothing specified. Each time round it tightens, and each time round the story about the team, or the software, gets a little more settled.

Why the usual answers don’t work

The usual advice is to hire better people, or find better software, or trust your team more. None of those touches the cause.

Hiring someone more experienced helps for the tasks they already know. The moment you ask them to do something the way your business does it, you’re back to the handover, and the handover is still empty. Better software has the same problem: a system assumes a documented process to run, and if there isn’t one, you’re configuring it at ten at night and it still doesn’t do what you meant. And trust is the wrong frame altogether. You’re not checking everything because you’ve got a trust problem. You’re checking everything because there’s nothing else in the business that does the checking. That isn’t a character flaw. It’s a gap.

I’d put it like this. What looks like a delegation problem is a specification problem. That’s why the work comes back whether it went to a person or a machine. There’s nothing for it to land in.

This holds whether you’ve got a team of ten or nobody at all yet. Plenty of owners I speak to are working through a freelancer, a part-timer, an assistant or a set of AI tools, and the same thing applies. The question isn’t “who can I give this to?” It’s “what would they need in front of them to get it right without me?”

What changes when it works

Owners who get past this don’t stop checking. No owner in this position believes that’s safe, and they’re right. What changes is where the check sits. Instead of approving the output every time it comes back, you approve the specification once, and the work runs against it.

The first thing an owner tends to notice when it starts working sounds like this: “I saw my own content on Facebook the other day from my business, and I hadn’t even seen it. I’d signed it off, but I just did a quick sign-off before it was even turned into a post, and yet there it was. What a feeling, to know that something happens and it doesn’t need me involved in it now.”

Read that carefully. They still signed off. The sign-off moved from the end of the work to the start of it.

One thing to do this week

Pick one piece of work that keeps staying with you. Not the hardest one. One that’s regular, that you’ve handed over at least once, and that you ended up doing again.

Before you hand it over next time, write one page. What the finished thing looks like. One real example of it done right. The two or three things that, if they’re wrong, mean it isn’t ready. And who checks those things before it goes anywhere, which for now can still be you, but against the page rather than against your memory.

Then hand it over with the page. If it comes back wrong, don’t take it back. Go and look at which of the things on the page was unclear, fix the page, and send it again. You’re not training the person. You’re building the thing the work lands in, and once it exists, the next person, or the next tool, gets it too.

If this sounds familiar

Follow me on any of my social sites or on LinkedIn. I write about how owner-led businesses get the work to stop needing the owner, without anybody being replaced and without anybody working harder.

And if you’d like to find out why the work in your business stays with you, there’s a short check on the website that will show you, and what you might be able to do about it. It takes two minutes, and there’s a free Clarity Call after it if you want one. Twenty to thirty minutes, no obligation, and we’ll look at your business rather than a general one.

Take the check: pauljarman.coach/delegation

Book a Clarity Call: pauljarman.coach/book-a-call-delegation