You handed off the task. It came back wrong, late, or not at all. So you took it back, did it yourself, and told yourself you’d try delegating again “when things calm down.” That moment, right after the first failure, is where most owners decide delegation doesn’t work for their business. I’ve watched that decision get made a hundred times, and it’s almost always wrong. One failed handoff doesn’t mean delegation doesn’t work. It means one specific piece of the handoff was missing, and that piece is fixable.
What “Failed” Actually Means
Before fixing anything, separate two problems that get lumped together constantly: a hiring failure and a delegation failure. A hiring failure means you put the wrong person in the role. A delegation failure means you had the right person and still didn’t hand off the work in a way that let them succeed. I see owners write off good employees over what was actually the second problem, not the first. If the person has done solid work elsewhere, on other tasks, in other seasons, the failure probably isn’t about them. It’s about what they were handed and what they weren’t.
That distinction matters because the fix is completely different depending on which one you’re facing. A hiring failure means you make a personnel change. A delegation failure means you look at how the task left your hands in the first place, and in almost every case I’ve seen, one of three things was missing.
The Three Things Most Owners Skip
The first is a clear definition of done. Owners know what a finished task looks like because they’ve done it themselves a hundred times. That picture lives in your head, not on paper, and you hand off the task assuming the picture transfers with it. It doesn’t. If you can’t describe, in writing, what the result should look like before you hand something off, the person receiving it is guessing, and guessing is where delegation starts to fail before it even begins.
The second is authority, not just the task itself. This is the one that trips up owners running on EOS the most, because EOS gives you language for it: an accountability chart assigns a seat, but a lot of owners fill the seat without transferring the actual decision-making power that seat is supposed to hold. You hand someone the task of managing a vendor relationship, but you still want final say on every email. That’s not delegation. That’s supervised typing. If the person can’t make the calls that come with the job, you haven’t delegated the job, you’ve delegated the busywork around it and kept the job.
The third is a follow-up checkpoint that isn’t a rescue. Most owners either check in so often it reads as distrust, or they don’t check in at all until something breaks. Neither one works. A scheduled checkpoint, set before the work starts, gives the person room to work and gives you a real look at progress before it’s too late to course-correct. Skip this step and you’re stuck choosing between hovering and finding out too late, and most owners end up doing both on the same task.
Why Owners Take the Task Back Too Fast
Here’s the part that actually costs you the most. When a delegated task goes sideways once, the instinct is to grab it back immediately. It feels responsible. It feels like damage control. Harvard Business Review points to the same pattern across companies of every size: taking work back after one miss confirms to that person, and to everyone watching, that they were never really trusted with it in the first place. The next time you hand something off, they’ll do the bare minimum and wait for you to take it back again, because that’s what happened last time.
I’ve seen this play out with owners who are otherwise sharp operators. One bad handoff, and they quietly start doing that function themselves again, permanently. Six months later they’re back in my office wondering why nobody on the team steps up. The team didn’t stop stepping up. The owner stopped letting them.
How to Re-Delegate the Same Task Without Repeating the Failure
The fix isn’t a different person. In most cases, it’s the same task handed to the same person, done differently. Before you hand it back, write down what done actually looks like this time, specific enough that there’s no ambiguity about whether the work met the bar. Name, out loud, what decisions come with the task and confirm the person can make them without checking with you first. Set one checkpoint on the calendar before the work starts, not after something looks off.
Then let it run. This part is harder than it sounds, because the instinct to check in early is strong right after a failure. Resist it until the checkpoint you already set. If the work comes back right this time, you’ve fixed a delegation problem. If it comes back wrong again in the exact same way, you’re now looking at a hiring conversation, not a delegation one, and you’ll know the difference because you gave the handoff a real shot the second time.
Frequently Asked Questions
Should I give the task to someone else after a delegation failure?
Not yet. Most first failures are delegation problems, not people problems. Fix the handoff, same person, before you conclude the person is the issue.
How do I know if a delegation failure was my fault or theirs?
Check whether the person had a clear definition of done, real authority over the decisions involved, and a set checkpoint. If any of those were missing, the failure started with the handoff, not the employee.
What is the difference between delegating a task and delegating a decision?
Delegating a task hands off the work. Delegating a decision hands off the authority to make the calls that work requires. Most delegation failures happen because owners do the first and skip the second.
Ready to Stop Being the Bottleneck?
I’ve worked with over 100 business owners who hit this exact wall, one failed handoff away from deciding delegation just doesn’t work for their business. It almost always does. It just needs business coaching built around EOS, not a task list. If you’re ready to build that structure, start here and let’s look at where your handoffs are actually breaking down.
