7 Delegation Mistakes Busy Managers Make (And the Fix for Each One)

You cannot lead strategically if everything still lands on you

It is 6:40 on a Tuesday evening. Your calendar was blocked with meetings from nine to five, and the actual work started after everyone else logged off. You open your task list and notice that four of the items on it are things you handed to someone else last week. A review that came back with no decisions made. A vendor email forwarded to your inbox with a question mark. A draft that needs "a quick look" before it can go out.

So you do it yourself. Again. And you tell yourself that next time you will delegate properly, once things calm down.

Here is what I want you to hear clearly: delegation is not a personality trait you either have or lack. It is a set of mechanics. When those mechanics are missing, work comes back to you, and the usual explanation people give themselves ("I am just faster at it") hides the actual cause. In my work with busy professionals, the same handful of delegation mistakes show up again and again, and every one of them has a concrete correction. This article walks through seven of them, what each looks like in practice, and exactly what to change.

Mistake 1: Handing over tasks instead of outcomes

This is the most common delegation mistake and the root of most of the others.

What it sounds like: "Can you put together a slide deck for the Thursday review?" That is a task. It has a shape but no purpose. The person receiving it has no idea what the deck needs to accomplish, who it is for, or what a good version looks like.

Why it fails: When you delegate the task, you keep the thinking. The person builds a deck that answers the wrong question, you rebuild it, and you conclude that delegating takes longer than doing. You have trained yourself to stop delegating based on a test that was rigged from the start.

The fix: Delegate the outcome and the constraints, not the steps. A workable version of the same request sounds like this:

"We need the steering group to approve the phased rollout on Thursday. Build the deck around one decision: do they agree to phase one starting in March, or do they want a different sequence? Assume they have eight minutes with you and two objections: cost in Q1 and support capacity. Bring me the deck Wednesday at noon so I can pressure test it, not so I can rewrite it."

Notice what changed. There is a decision, an audience, a time constraint, a known objection, and a checkpoint. The person now owns the thinking, which is the entire point.

A quick test before you hand anything over

Before you send the message, ask yourself: could this person explain back to me what success looks like, and what they are allowed to decide on their own? If not, you have delegated a task, not an outcome.

Mistake 2: Delegating a task but not the authority to complete it

You have probably experienced this from the receiving end. Someone asks you to "take the lead on the supplier negotiation" and then, in the next meeting, makes every decision in front of you. You learn quickly that your authority is decorative.

Now you are doing it to someone else.

What it looks like: You hand over a project but require sign off on every email. You ask someone to manage a budget but reserve any spend above 200. You ask your team lead to run the client call, then answer every question yourself while they sit there holding a pen.

Why it fails: People do not develop judgment by watching you use yours. They develop it by making calls, including some imperfect ones, and seeing the consequences. If every decision routes back to you, you have added a project to your workload and removed growth from theirs.

The fix: Write down the decision rights in the handover, in one or two lines. For example: "You decide scope, sequencing, and the two contractors. I decide anything that changes the total budget or the client's committed delivery date. If something sits on that line, message me the same day rather than waiting for our next check in."

That single sentence prevents most of the friction. It tells the person what they own, tells them when to escalate, and removes the quiet ambiguity that makes people check in on everything.

The measure of a good handover is not whether you feel comfortable. It is whether the other person can name what they decide, what they bring to you, and what good looks like.

Mistake 3: Delegating at the wrong altitude

Not every piece of work needs the same level of instruction. One of the most useful delegation mistakes to fix is treating all tasks identically, which usually means over briefing simple work and under briefing complex work.

A practical way to think about it is four levels of handover, and you choose the level based on the stakes and the person's experience with that kind of work.

The mistake is defaulting to the first level with everyone, forever, because it feels safe. The correction is to state the level out loud and then move the person up a level after a couple of successful cycles. If you never say which level you are operating at, the other person assumes the lowest one and checks in constantly, which you then read as neediness rather than as a sane response to unclear instructions.

Mistake 4: Delegating the work but keeping the visibility

This one is subtle and it damages trust quietly.

What it looks like: Your team member delivers solid work. In the leadership meeting, you present it. Someone praises it. You say thank you. The person who did the work is not in the room, was not copied on the thread, and finds out at the next team meeting that the thing they built is now referred to as your initiative.

Why it fails: Delegation requires a fair exchange. People give you their effort and their judgment, and in return they expect to grow, to be seen, and to have their name attached to good work. When you keep the credit as well as the accountability, delegation starts to feel like extraction. People will still take the work, but they will stop bringing their best thinking to it.

The fix: Decide at handover where the visibility goes. Two questions settle it: whose name is on this, and who is in the room when it is discussed? If the answer is "me" for both, ask whether it needs to be. Sometimes yes, for client reasons or political ones. But when you can hand over the visibility too, do it, and tell the person in advance that you will be putting their name forward and why.

Mistake 5: No checkpoint design, so you end up on the critical path

You want to be available. So you say: "Any questions, just shout." This feels supportive. In practice it creates a permanent open channel where every small uncertainty comes to you immediately, and your day gets shredded by interruptions.

What it looks like: Your phone buzzes with "quick one" messages all afternoon. Each takes 90 seconds to answer, each costs you four minutes of refocusing, and by the end of the day you have answered 14 questions and finished nothing.

Why it fails: Without a planned rhythm of checkpoints, the default rhythm becomes whenever the other person feels uncertain. That is not a fair system for either of you. It makes them dependent and makes you unavailable for the work only you can do.

The fix: Design the checkpoints at handover and be specific about the channel for each type of question. Something like:

• Two short scheduled check ins, Tuesday and Thursday, 15 minutes each.
• Blocking issues only: message me any time, but include the decision you need and your recommendation.
• Everything else: write it down and bring it to the next check in.

That last line does more work than it appears to. Most questions resolve themselves the moment someone has to write them down and propose an answer. The ones that survive are genuinely worth your time.

Mistake 6: Delegating upward without noticing

Sometimes the delegation mistake is happening to you, and you are accepting it.

What it looks like: A colleague or your own manager sends you a half-formed idea with "could you take a look?" A peer asks you to "just sense check" a document they have not yet thought through. Your director forwards a client complaint and asks what you think should happen, without telling you what they think should happen.

Each one looks small. Together they can consume a significant slice of your week, and they are all someone else's thinking being outsourced to you.

Why it fails: You absorb work that belongs elsewhere, and you teach the people around you that you will absorb it. It also keeps you in a reactive position, which is the opposite of the executive presence and strategic leadership you are trying to build.

The fix: Have a standard sentence ready that returns the thinking without being rude. For example: "Happy to react once I can see your recommendation. What would you do?" Or: "Send me the two options you are weighing and which one you lean toward, and I will tell you where I land."

You are not refusing. You are asking for the thinking before the answer, which is a reasonable expectation between adults at work. It also gets faster and better work back to you, because people prepare before they ask.

Mistake 7: Treating delegation as a one-time event

The most expensive delegation mistake is doing it once and moving on.

What it looks like: You hand over a project, it goes reasonably well, and you never discuss it again. Three months later the same person is making the same predictable missteps, and you conclude they are not ready for more. Nothing was ever named, so nothing changed.

Why it fails: Delegation is a loop, not an event. Hand over, check in, debrief, adjust the level of authority, repeat. Skipping the debrief means the learning stays inside your head, and your assessment of who is ready and who is not never updates.

The fix: Book a 15 minute debrief two weeks after the handover, while the work is still fresh. Three questions, in this order:

1. What was harder than you expected, and why?
2. What did you decide that you were not sure about?
3. What should I have been clearer about at the start?

That third question is the one that will change how you delegate. It tells you, from the other person's side, exactly where your briefing was thin. And asking it signals that the handover is something you are jointly improving, not something you are handing down.

What to do this week: three concrete steps

You do not need to fix all seven at once. Pick the smallest set of changes that will produce a visible difference in your week.

Step 1: Pick three things off your plate (20 minutes)

Open your task list and mark anything that meets two criteria: someone else could do it with a reasonable briefing, and you are on it mainly out of habit. Choose three. Not ten. If nothing qualifies, look harder at the small recurring items, such as the weekly report you rewrite every Friday because you have never explained what good looks like.

Step 2: Write a one-page handover for each (30 minutes total)

For each item, write six lines: the outcome, the decision the work informs, the person's decision rights, the checkpoint schedule, the channel for blocking questions, and whose name goes on it. Six lines. If it takes more than a page, you are describing steps again.

Step 3: Hand over in a conversation, not a document (15 minutes each)

Send the one pager, then talk it through. End by asking the person to say back what they will do and what they will decide on their own. If their summary matches your page, you have delegated something. If it does not, you have found the gap before it costs you a rebuild.

That is under two hours of work to hand over three recurring items, and you can spread it across the week rather than blocking a morning. If 15 minute conversations feel impossible, shorten them to 10 and reduce the number of items to two. Two well delegated items beat five vague ones.

What shifts when you get the mechanics right

Delegation is not a way to offload work so you can relax. It is how you build a team that can operate without you in the room, which is the actual precondition for strategic leadership.

When the mechanics are in place, three things tend to change. Your week stops being a series of small fires and starts having blocks of thinking time. People around you stop waiting for approval and start bringing you proposals. And your own judgment gets sharper, because you are spending it on the decisions that are genuinely yours rather than on a hundred small ones that drifted upward.

If you want to go further than one week, the version I would aim for is a rhythm: every Friday, spend 20 minutes reviewing what you did this week that someone else could have done with a clear brief, and hand over one of those things the following week. Twenty minutes, one item, repeat. Over a couple of months that is a different job.

And if you notice that most of your work comes back to you because you have never written down what good looks like for the roles around you, that is worth a deeper conversation. One clear hub of expectations, shared and revisited, removes most of the chaos that makes people believe delegating is not worth the trouble. It is. It just needs a brief.

Start with one item this week. Write the six lines. Have the ten minute conversation. Then notice how much of your Thursday you get back.