What is the difference between delegating and just assigning tasks?

Assigning moves the work; delegating moves the ownership. When you assign, you still hold the decisions, the sequencing and the outcome. When you delegate, the other person decides how it gets done and is answerable for the result, within limits you have named out loud. If every choice still routes back to you, you have assigned, not delegated.

What should a manager never delegate?

Anything with your name and judgement inextricably attached: pay and promotion decisions, performance conversations, hiring calls, discipline, and any sign-off you would not be comfortable defending afterwards. Also keep the first instance of anything genuinely high-risk, ideally doing it alongside the person you will hand it to next time, thinking out loud as you go.

How do I delegate when I can do the job faster myself?

You almost always can, the first three times. That is arithmetic, not an argument. Doing it yourself costs you the same hour every month indefinitely; teaching it costs you roughly three hours once. If a task recurs, delegate it. If it is genuinely one-off and time-critical, do it yourself and stop feeling bad.

What are the levels of delegation?

A common ladder runs from do exactly this and report back, to research and bring options, to recommend and wait for approval, to decide and tell me first, to decide and act without telling me. The value is in naming the level explicitly at handover, so nobody has to guess how much permission they were given.

How do I delegate without micromanaging?

Agree the check-ins during the handover rather than dropping in unannounced, ask about decisions instead of status, and be specific about the two or three things you genuinely need rather than how the work should be done. The rule of thumb: define the outcome tightly and the method loosely, then hold your nerve in between.

How do you delegate to someone more experienced than you?

Say the awkward thing first: "You know this area better than I do, so I'm not going to tell you how to run it." Then be clear about the outcome, the constraints you cannot move, and what you need to know and when. Experienced people rarely resent direction on outcomes. They resent supervision of method.

How to Delegate Effectively: Scripts for Managers

Nearly every manager who says they are bad at delegating is bad at two specific moments: the handover conversation, and the first time the work comes back not quite right. Everything else is detail. So this guide is mostly words you can say out loud, in the order you say them.

First, decide what actually leaves your desk

The instinct is to delegate the things you dislike. That is a bad filter, because the things you dislike are often the things nobody else can do either. Run each recurring item on your plate through this instead.

What the task is	What to do with it
Only you can do it: pay, hiring, a performance conversation, a sign-off with your name on it	Keep it, and stop feeling guilty about keeping it
You are simply fastest at it, but it is not rare	Delegate it. Your speed is exactly why it has never been taught to anyone
Someone on the team would grow from it	Delegate it, with more support than feels necessary
You enjoy it and it is a level below you	Delegate it. This is the most common trap and the hardest one to admit to
Nobody has done it before and the downside is serious	Do the first one together, thinking out loud. Delegate the second one

The handover conversation, in order

Book fifteen minutes. Do not do this over chat, and do not squeeze it into the last two minutes of a one-to-one. The sequence matters, because each step answers a question the other person is already asking silently.

Name the outcome, not the task. Say: "I want you to own the supplier review end to end. Success is a recommendation the leadership team can act on, by the 14th."
Say why them. Say: "You're getting this because you already know the two biggest suppliers better than I do, and because I want you visible to that group before the promotion round." People work differently when the reason is not "you were free".
Hand over the authority out loud. Say: "You decide the format, who you talk to, and what goes in the recommendation. Come to me before you commit us to a new contract, or before you tell a supplier we're leaving." Two sentences: what they own, where the edges are.
Give them what is in your head. The history, the politics, the landmines. Say: "Two things that aren't in the folder. Procurement tried this two years ago and it stalled at legal. And Priya has strong views about the incumbent, so talk to her early rather than presenting to her cold."
Agree the check-ins now. Say: "Twenty minutes next Thursday, then the week before the deadline. If anything slips in between, tell me the day you know, not the day it's due."
Ask them to play it back. Say: "So I know I've explained it properly, what are you going to do first?" The gaps you hear in that answer are the same gaps that would otherwise surface in week three, when there is no time left to fix them.

Wrong way, better way

The difference between delegation that sticks and delegation that boomerangs is usually one sentence, said differently.

What managers usually say	What to say instead
"Can you take a look at the supplier review?"	"You own the supplier review end to end. I need a recommendation by the 14th."
"Let me know if you need anything."	"Thursday, twenty minutes. Bring me the two things you're stuck on."
"Just do it the way I'd do it."	"I don't mind how you get there. Three things I do need: the cost comparison, one named risk per option, and Priya consulted."
"This is urgent."	"This sits above the newsletter and below the audit. Drop the newsletter if you have to."
"Sorry to dump this on you."	"This is a step up, and I think you're ready. Here's the support that comes with it."
"Send it to me before it goes anywhere."	"Send it straight to Ravi and copy me. If I'd have done it differently, I'll tell you after, not before."

If you cannot say out loud which decisions this person can now make without you, you have not delegated the work. You have lent it out.

Set the level, not just the task

Most delegation arguments are really arguments about permission. One person thought they were being asked to decide; the other thought they were being asked to research. Fix it by naming the level explicitly, every time.

"Do exactly this and tell me when it's done." For brand-new people, or anything with a serious downside.
"Look into it and bring me the options. I'll choose."
"Look into it, tell me what you'd do, and wait for my yes."
"Decide it, then tell me before you act."
"Decide it and act. I only need to hear about it if it goes sideways."

Then say the number. "This one's a three: bring me your recommendation and wait." It sounds mechanical for about a week, then your team starts using it back at you, which is when it saves everyone time. As trust grows, move people up and say so: "Last time this was a three. This time it's a five."

What to say when they bring it back

This is where delegation usually dies. Someone arrives with a problem, you solve it in ninety seconds because you can, and you have just taught them that bringing you problems is faster than solving them. The task is now yours again and neither of you noticed.

They bring a problem with no options. Say: "Come back at four with two options and which one you'd pick. If you can't get to two, come back anyway and we'll do it together."
They bring a plan you would not have chosen, but it will work. Say: "That's not what I'd have done, and it'll work. Go." Then say nothing else, which is the hard bit.
They are genuinely stuck and fishing for you to take it. Say: "What would you do if I were on a plane for two days?" Nine times out of ten they answer their own question in the next sentence.
They bring something that is actually wrong. Be direct and specific: "Stop before this goes out. The pricing table will get us challenged, and here's why." Vagueness here is not kindness. See how to give constructive feedback for the phrasing.

When it goes wrong

They try to hand it straight back

Usually in the first week, usually dressed up as a question. Do not take it. Say: "I'm not taking it back, but I'll sit with you for half an hour while you do the first part." Then sit there and mostly keep quiet. Most hand-backs are about not knowing where to start, not about capability.

The work comes back at sixty per cent

The overnight-rewrite is tempting and it is the single most expensive habit in management. You buy one clean deliverable and one person who learns nothing. Say instead: "Two things aren't ready: the pricing table and the summary. The rest I'd sign off as it is. Take another day on those two and walk me through them on Friday." Naming what is already good is not politeness, it stops them rewriting the whole thing.

You keep getting pulled back in

Other people still route around your delegate because you are the habit. Fix it publicly, once: "From now on Sam decides this. If you come to me, I'll send you to Sam." Then do exactly that the first time someone tests it, and the problem disappears in about a fortnight.

You find out it is late on the day it is due

More check-ins will not fix this. A different instruction will. Say: "Tell me the day you know it's slipping, not the day it's due. I will never be annoyed about early bad news. I will be annoyed about late bad news." Then, the first time someone brings you early bad news, thank them visibly and fix the problem with them. That one moment is worth more than any amount of psychological safety talk.

Everything ends up with your most reliable person

Reliable people attract work until they leave. Once a quarter, look at who received the last ten interesting things you handed out. If it is the same name three times running, the next one goes to someone else, at level two or three, with real support.

Checking in without hovering

Ask about decisions, not status. "What have you decided since we spoke, and what are you stuck on?" beats "where are we with it?"
Put check-ins in the diary at handover. Unscheduled ones read as suspicion, whatever your tone.
Avoid the corridor "how's that going?". It feels casual to you and like a deadline to them.
Ask "what do you need from me?", then deliver it within a day. Nothing kills ownership faster than a manager who is the blocker.

Why reading this will not be enough

Look at what is actually on this page. It is not knowledge. Nobody has ever failed to delegate because they were unaware that delegation exists. Every item here is one small skill: saying a slightly uncomfortable sentence clearly, at the right moment, out loud, while someone is looking at you.

That only changes through rehearsal and feedback. Say the handover to someone who pushes back. Get told your authority sentence was vague. Say it again ten minutes later, better. That is what experiential learning is for, and it is why the manager who has practised these conversations twice sounds completely different from the one who has only read about them.

Tour De Force runs this as live, experiential training for teams worldwide — online and in person. Talk to us, or play Gamified learning apps The Weekly Challenge to see the method in ten minutes.

How to delegate effectively