How to delegate effectively: what to hand off, to whom and how much

To delegate effectively, hand over an outcome with the authority to achieve it. Choose work someone else can do or learn to do; choose the person for their strengths or their development; set the level of autonomy by their readiness and the cost of a mistake; brief the result, limits and deadline; agree check-ins in advance; then step back and review results rather than methods. Keeping these agreements in your performance management software, next to goals and one-on-one notes, makes it easy to see what you have handed off and how it is going.

Most managers have room to do more of it. In a McKinsey survey of middle managers, respondents said nearly half of their time goes to nonmanagerial work, and less than a third to talent and people management. Delegation is how that balance shifts.

The case for delegating is usually made in hours saved. The stronger case is what it does for the people who receive the work and for results.

• Growth. In a Gallup study of 143 CEOs of fast-growing private companies, those with high delegator talent generated 33% greater revenue than those with low or limited delegator talent ($8 million versus $6 million). Their average three-year growth rate was 112 percentage points higher. The talent is not common: only one in four employer entrepreneurs Gallup studied had high levels of it.
• Motivation. A meta-analysis of 72 studies found that leaders who support their people's autonomy have employees with stronger self-driven motivation. The same review linked autonomy support with higher well-being and lower distress.
• Satisfaction. Across 259 studies, motivational job characteristics, autonomy among them, explained 34% of the variance in job satisfaction.
• Team performance. In a study of 62 retail teams, leadership related to team performance partly through how empowered the team felt.

Gallup's description of the difference is practical: strong delegators focus on outcomes, not processes, and set clear expectations on timing, budget and deliverables, while weak delegators micromanage and leave people confused and frustrated.

Start by listing everything you did last week. Then sort it:

A useful test is to ask, for each task: "If I were away for a month, who would do this?" If the answer is a name, start the handoff now, while you are around to help. If the answer is "nobody could," that is a development gap worth closing; our guide on how to develop leaders shows how to use stretch assignments on purpose.

Pick for one of two reasons, and know which one it is:

• Strength. The person already does this kind of work well, so delegating gets a good result and frees your time.
• Development. The person wants or needs to learn this, so delegating builds a skill. Expect it to take longer at first, and plan more support.

Spread the work. Managers tend to hand everything to their most reliable person, who then becomes overloaded while others wait for a chance to grow. Before you assign, check the person's current load and ask what they would move or drop to make room. Overloading the same few people is one of the most common routes to burnout; how to prevent burnout in the workplace includes a weekly load check.

The most common delegation problem is giving everyone the same amount of freedom on every task. Two questions set the right level:

• How ready is this person for this task? Not in general, but for this specific work: have they done something similar, and how did it go?
• What would a mistake cost? Money, customers, safety, legal exposure, reputation, and how hard it would be to undo.

The figure below turns the two questions into four approaches. A new analyst preparing a board report sits top left: they draft, you review before it goes out. The same analyst updating an internal dashboard sits bottom left: let them try and debrief afterward. An experienced lead negotiating a renewal sits top right: they decide, with check-ins before the key meeting. The same lead ordering team supplies sits bottom right: hand it over fully.

As readiness grows, move people right. The goal over a year is that most of each person's work sits in the right-hand column.

Autonomy is easier to agree when it has names. Say the level out loud when you hand the work over:

Naming the level prevents the two classic disappointments: the person who acts when you expected a recommendation, and the person who waits for approval when you expected them to act. It also gives you a way to grant autonomy step by step: move someone from level 3 to level 4 after a few good decisions, and tell them why.

A good brief takes ten minutes and saves days of rework. Cover five things:

1. The outcome. What does done look like, and why does it matter? "A one-page summary the leadership team can decide from on Monday" is a result; "do some research" is not.
2. The limits. Budget, deadline, quality bar, people who must be consulted, and anything that must not change.
3. The level. Which of the five levels applies, in plain words.
4. Authority and resources. What they can approve, spend or request, and who else will be told they own this now. Delegating responsibility without authority sets people up to fail.
5. Check-ins. When you will look at progress, set now rather than improvised later.

Then ask the person to play it back: "Tell me how you plan to approach it and what you'll need." The playback catches misunderstandings in minutes, while they are cheap. If the work affects other people, announce the change of owner where they will see it, so requests stop coming back to you.

Micromanagement is mostly a check-in problem: too frequent, unplanned, or about the method instead of the result. Agree the schedule with the level:

• Do it together / level 1–2: frequent, short check-ins (every day or two), plus a review before anything goes out.
• Delegate with checkpoints / level 3: two or three check-ins placed before the decisions that matter, such as before a contract is signed or a launch date is announced.
• Delegate to teach: one check-in early, help on request, and a debrief after.
• Hand it over fully / levels 4–5: a line in your regular one-on-one, and an agreed signal for raising problems early.

In check-ins, ask about progress, risks and what they need; avoid redoing the work or prescribing the method. If you catch yourself rewriting their draft, ask whether the outcome or only the style differs from yours. If only the style, let it go. A standing one-on-one template with a "delegated work" line keeps check-ins regular without extra meetings.

Mistakes on delegated work are part of the cost of building capability. How you respond decides whether people accept stretch work again.

1. Fix the immediate problem together. Focus first on the customer, the deadline or whoever is affected.
2. Review the handoff before the person. Was the outcome clear? Was the level right? Did they have the authority and information? Most failures trace back to the brief.
3. Debrief, without blame. "What did you expect, what happened, and what would you do differently?" Then share what you would do differently in your brief.
4. Adjust the level, not the relationship. Move one level down for the next similar task if needed, and say how they can move back up.

Do not take the work back silently. It teaches the person, and everyone watching, that delegated work is never really theirs. Delegation and trust grow together; how to build trust in the workplace covers the other side of that relationship.

The same tools work upward. Most micromanagement comes from a manager's anxiety about results, so reduce the anxiety:

• Ask for the level. "For this project, would you like me to recommend, or decide and keep you posted?"
• Offer the check-ins first. "I'll send you a short update every Tuesday and flag any risk the same day." A predictable update often replaces unannounced questions.
• Show your plan early. Share the approach before you start, so your manager can raise concerns once rather than throughout.
• Earn the next level. After a few results delivered as agreed, ask to move up a level for similar work.

• Handing over: "I'd like you to own the vendor renewal. What I need is a signed contract by the 30th within the current budget. You decide the terms; tell me before you sign. Let's check in on the 15th and the 25th."
• Explaining why you chose them: "I'm asking you because you've wanted more client work, and this is a good first one. I'll be around if you get stuck."
• Checking understanding: "Before you start, walk me through how you'd approach it and what you'll need from me."
• Resisting the urge to step in: "That's not how I'd have done it, and it works. Go ahead."
• Raising the level: "Your last three calls were sound. From now on, you can decide these and tell me afterward."
• When it went wrong: "Let's fix this first. Then I want to look at my brief, because I don't think I gave you what you needed."

• Delegating tasks instead of outcomes. Step-by-step instructions get compliance, not ownership.
• Responsibility without authority. If people must ask permission for every step, the work was not really delegated.
• The same level for everyone. Too little freedom frustrates experienced people; too much overwhelms new ones.
• Delegating only what you dislike. People notice when they only receive unwanted work. Hand off some interesting work too.
• Overloading your most reliable person. Spread stretch work so more people grow.
• Unplanned checking. Surprise inspections feel like distrust. Agree check-ins at the start.
• Taking work back. Unless the stakes demand it, coach instead.

Software makes delegation visible. Performance management tools keep one-on-one notes, goals and agreed check-ins together, so you can see what each person owns and how it is going. OKR tools let you delegate an objective with measurable key results and follow progress without asking for daily updates. Internal communication tools announce who now owns a decision so requests stop routing back to you.

No tool can decide how much autonomy someone is ready for, or stop you from taking work back. Those choices are the skill. If your team's work is stuck because too many decisions wait for you, decision making in leadership shows how to sort decisions by stakes and reversibility so more of them can be delegated.