Why do managers struggle to delegate?

Why is delegating so hard for managers?

Because doing the work yourself feels faster, safer and more rewarding, at least today. Handing it over costs you time now and pays you back later, and later is easy to ignore.

Even experienced leaders find this. A summary of Elsbeth Johnson’s work from MIT Sloan Executive Education notes that sharing work and giving up control “can be astoundingly difficult.” It isn’t a character flaw. It’s a pull that most managers feel, and new managers feel it most, because doing the work is what got them promoted.

Writing in Harvard Business Review, Jesse Sostrin calls the move “the shift from doing to leading” one of the hardest transitions a leader makes. He also points out that as a new manager “you can get away with holding on to work.” For a while, nobody stops you. If that identity shift is the part you’re wrestling with, read going from individual contributor to manager first.

Here’s the thing most advice misses. Very few managers refuse to delegate outright. They hand the task over and then keep a grip on part of it. In our experience that grip usually takes one of four shapes:

• Taking work back when it’s quicker to do it yourself.
• Approving everything, so work waits for your sign-off.
• Holding the context, so the why lives in your head.
• Rescuing, stepping in before people have had a go.

Each one feels reasonable on the day. Together they mean the work is technically delegated but still runs through you.

Why do you keep taking work back?

Because finishing something feels good, and finishing it yourself is quicker this week. The cost shows up next month, when the same task comes back to you again.

The MIT Sloan piece describes the brain chemistry behind it: when we accomplish something, “small hits of dopamine are released.” Ticking off a task gives you that reward straight away. Setting direction, coaching and waiting for someone else to finish give you very little in the moment. So under pressure, you reach for the task.

Taking work back has two common forms. The obvious one is “Give it here, I’ll do it.” The quieter one is redoing parts of the work before it goes out: rewording the slides, tidying the analysis, rewriting the email. Both teach the same lesson. Your version is the real one, so there’s no point the team trying too hard.

Johnson’s test helps here. Before you pick something up, ask: “Am I the best and cheapest person to get this done?” Not the best person in absolute terms, but the best use of your hour. If someone on your team can do it to a good enough standard, the answer is usually no.

A small move: pick one task you took back this month and hand it over again, this time describing the outcome you want rather than the steps.

Why does everything wait for your sign-off?

Because nobody has been told which decisions they can make without you. So they play it safe and ask, and every question joins a queue with your name on it.

This leak is easy to miss because it looks like being responsible. You ask to see things before they go out. You ask to be copied in. You like to know what’s happening. Each request is small. But if your team of five each waits half a day a week for you to reply, that’s two and a half days of work standing still, every week.

We call the build-up of this waiting Decision Debt. It grows quietly, and it’s usually the manager who notices last, because from your seat everything seems to be moving.

The fix is to be explicit. Write down three decisions your team can make without you, each with a limit. For example:

• “You can agree deadline changes of up to a week with the client. Tell me after.”
• “You can approve spend under £500 from the team budget.”
• “You can choose the format for internal updates. I don’t need to see them first.”

Share the list. Then, and this is the hard part, don’t override the first decision someone makes under it, even if you’d have chosen differently.

Why do people keep coming back to you with questions?

Because the context lives with you. You know why the project matters, what the stakeholder really cares about and which corners you can cut. If that never gets written down or said out loud, people have to keep coming back to ask.

Johnson’s framing is useful here: “context-setting is the leader’s responsibility when delegating,” according to the MIT Sloan summary. The team owns the activity. You own the why, the expected result and the deadline. When you skip the context and only hand over the task, you’ve delegated the work but kept the judgement, so every judgement call comes back to you.

Holding the context often feels like efficiency. Explaining the background takes ten minutes, and you’re busy. But those ten minutes save you the five follow-up questions, the wrong first draft and the meeting to fix it.

Before your next hand-over, write three lines:

1. The goal: what this is for and who it’s for.
2. What good looks like: how you’ll both know it’s done well.
3. What not to worry about: the parts that don’t need polish.

That third line matters more than it looks. It gives people permission to move quickly on the parts you don’t care about, instead of guessing.

Why do you step in before people have had a go?

Because watching someone struggle is uncomfortable, and you can see the answer. Stepping in feels kind. It also takes away the bit of the task where they would have learned something.

Rescuing has a cousin: checking in on delegated work more often than you agreed. You say “Take it from here” and then ask how it’s going every morning. The MIT Sloan piece is blunt: “Micromanagement saps employee productivity and growth.” Even friendly check-ins tell people you’re still holding the task, and they start waiting for your input rather than moving on their own.

Rescuing is closely linked to answering too fast, which we’ve written about in why new managers give answers too fast. The short version: next time someone is stuck, ask “What have you tried?” and wait ten seconds before you say anything else. It will feel long. Wait anyway.

What does a delegation leak look like in a real week?

Here’s a hypothetical example. A new team lead in a marketing team manages four people. On Monday she delegates the monthly performance report to one of them, an analyst who has helped with it before.

• Monday: she hands it over in a two-line message: “Can you own the monthly report this time? Same as usual.” She doesn’t mention that the director has started caring much more about one channel. (Holding the context.)
• Tuesday: the analyst asks whether to include a new campaign. The lead is in back-to-back meetings and replies the next afternoon. (Approving everything.)
• Wednesday: she asks for an update in the morning stand-up, then again by message after lunch. (Rescuing, through checking in.)
• Thursday: the draft arrives. It’s solid, but it doesn’t lead with the channel the director cares about. She stays late and rewrites the first two pages. (Taking work back.)
• Friday: the director praises the report. The analyst knows she didn’t write the part that got praised.

Nothing here is dramatic. She did delegate the report. But all four leaks showed up in one week, and next month the analyst will wait for instructions instead of owning it.

The fix wasn’t to delegate more. It was to delegate the same task better: three lines of context on Monday, one clear decision she could make on Tuesday, one agreed check-in, and feedback on Thursday instead of a rewrite.

Does failing to delegate really cost that much?

It can. The clearest numbers come from founders rather than new managers, but the pattern is worth knowing. The cost is mostly time: yours, and your team’s while they wait.

In a Gallup study of 143 Inc. 500 CEOs, those with high delegator talent “generated 33% greater revenue in 2013” than those with limited or low delegator talent. The same article notes that “75% of the employer entrepreneurs Gallup studied have limited-to-low levels of Delegator talent.” That’s an association in one group of business owners, not proof that delegating causes growth, and it doesn’t tell you what happens in a five-person team inside a large company.

What’s more useful for a manager is how Gallup describes good delegators. Among the traits it lists: they “know that they can’t accomplish everything themselves,” and they “focus on outcomes, not processes.” Those two lines are a decent summary of all four leaks. Taking work back and rescuing come from believing you have to do it. Approving everything and holding the context come from managing the process instead of the outcome.

What should you not delegate?

Some things should stay with you: feedback on someone’s performance, decisions about pay and promotion, confidential people issues, and setting the direction for the team. These carry your authority, and handing them over would be unfair to the person who received them.

Almost everything else is open to discussion, including the work you enjoy. That last part is where most managers draw the line too early. The tasks you love doing are often the ones you do best, which makes them the best learning opportunity for someone else. Keeping a small piece of hands-on work is fine. Keeping it because it’s the fun bit is a leak.

If you’re not sure where the line sits for a task, ask two questions. Does this need my authority, or just my skill? And if someone else did it to 80% of my standard, what would actually go wrong?

Which of your habits is leaking the most?

Most managers have one or two leaks that matter far more than the rest. Knowing which ones they are tells you where to start, so you don’t try to fix everything at once and give up by Thursday.

Delegation Detox is a free self-test built for this. It takes about 4 minutes, needs no sign-up, and your answers stay in your browser. You answer 12 questions about the last month, covering taking work back, approving everything, holding the context and rescuing. You get a delegation score out of 100, your top three delegation leaks, and one thing to try on Monday for each. A low score isn’t a diagnosis. Holding on can be the right trade-off in a crisis or with a brand new hire. The score shows you where that trade is costing your team the most.

For a wider read on how you lead, including how often you end up owning the next step when someone brings you a problem, try The 42 Test. You’ll find the other tests and posts for this career moment on the new managers page.

Delegating isn’t one big decision to let go. It’s a handful of small moments each week where you choose not to take the work back. Pick the moment you lose most often, and win that one first.