How to Delegate Without Losing Control

What you'll learn

How to decide which tasks to delegate and which to keep.
The seven levels of delegation from Management 3.0, with a phrase for each level.
A five-part delegation conversation you can use word for word.
How to calculate when delegating a task pays back the time you invest in training.
How to stay informed without micromanaging, and how to stop taking problems back.

📥 Practice this lesson

List the tasks you could hand off, choose a delegation level and let the sheet calculate the break-even week and the hours you'll free up in a year.

leadership-toolkit.xlsx · sheet Delegation Matrix

Delegating means giving someone else the responsibility and the authority to complete a task or make a decision, while you stay accountable for the result. It's not dumping work, and it's not disappearing. Done well, delegation frees your time for leadership work, develops your people and makes your team less fragile. Done badly, it produces either micromanagement or nasty surprises. This lesson shows you how to do it well, including the math that proves it's worth it.

7levels of delegation, from "I decide and tell you" to "you decide, I don't need to know"

3 weeksto break even on delegating a 3-hour weekly report in this lesson's example

134 hfreed in the first year by handing off that single task

Why managers don't delegate (and why the reasons don't hold up)

What managers say	What's usually true
"It's faster if I do it myself."	Faster this week. Slower every week after that, forever.
"Nobody can do it as well as I can."	Someone can do it 80% as well now and 100% as well in a few months.
"My team is already too busy."	Maybe. Ask them, and help them drop or delay something else.
"If it goes wrong, it's on me."	True. That's why you choose the right level and check-in points.

What to delegate and what to keep

Delegate

Recurring tasks, work someone else can learn, tasks that would stretch a team member toward their goals, and decisions closer to the front line than to you.

Examples: weekly reports, scheduling drafts, vendor follow-ups, running a standup.

Keep

Performance reviews, compensation, confidential personnel issues, crisis response and setting your team's direction.

Why: these depend on your authority or on information you can't share.

Hiring interviews, budget proposals and process redesigns: involve others, but keep the final call.

How: use a "consult" or "agree" level, explained below.

The seven levels of delegation

Delegation isn't all or nothing. Jurgen Appelo, creator of the Management 3.0 approach, describes seven levels that range from the manager deciding alone to the team deciding entirely on its own. Saying the level out loud prevents the most common delegation failure: you thought you were asking for input; they thought they had the final say.

Level	Who decides	Phrase you can use
1. Tell	You decide and announce it, maybe explaining why.	"We're switching carriers on the 1st. Here's why."
2. Sell	You decide, then try to convince them it's the right call.	"I've decided on the new layout. Let me show you why I think it'll make your job easier."
3. Consult	You ask for input first, then decide.	"I'll make the call by Friday, but I want your input first."
4. Agree	You decide together, by consensus.	"Let's not leave this room until we all agree on the new rotation."
5. Advise	They decide; you offer your opinion.	"It's your call. If you want my two cents, I'd test it on one shift first."
6. Inquire	They decide; afterward you ask how it went.	"Go ahead and set it up. Walk me through what you chose next week."
7. Delegate	They decide; you don't need the details.	"This is yours. You don't need to run it by me."

Appelo's team exercise, Delegation Poker, has each person privately choose a level for a decision ("Who chooses the next team offsite?") and then compare. The differences start useful conversations about who decides what.

1. A manager says: "You pick the new label printer. Before you place the order, tell me what you chose and why, and I'll share my concerns if I have any." Which level is closest?

Level 5: Advise
Level 3: Consult
Level 7: Delegate

The employee decides, but the manager offers an opinion before the decision is final. At Consult, the manager would decide; at Delegate, the manager wouldn't need to hear about it at all.

The five-part delegation conversation

What and whyDescribe the task and its purpose"I'd like you to own the weekly carrier performance report. Our biggest client reviews it every Monday to decide how much volume to send us."
What done looks likeDefine the result, not the method"Done means the on-time and damage rates for all five carriers, with a one-line comment on anything below 95%, in my inbox by Friday at 3 p.m."
Authority levelSay the level out loud"You decide how to build it and what to flag. For the first month, I'll review it before it goes out. After that, you send it directly."
Resources and limitsName the help and the guardrails"You'll have WMS report access and two hours on Thursday afternoons. Don't contact the client directly yet."
Check-insAgree on how you'll stay in touch"Let's look at the first draft together Thursday. What questions do you have, and what would make this hard for you?"

End with teach-back: "Just so I know I explained it well, how are you planning to approach the first one?"

Don't take the monkey back

In a classic 1974 Harvard Business Review article, "Management Time: Who's Got the Monkey?", William Oncken Jr. and Donald Wass described how managers end up doing their team's work: an employee says, "We've got a problem," the manager says, "Let me think about it," and the "monkey" jumps onto the manager's back. Keep it where it belongs:

"What do you recommend?"
"What options have you considered? Which one would you pick?"
"I'm happy to help you think it through. What's your next step?"
"Bring me two options and your recommendation by Wednesday."

2. A shift lead stops you in the hallway: "The temp agency sent the wrong number of people again. What should we do?" What's the best response if you've delegated staffing to her?

"Leave it with me, I'll call the agency this afternoon."
"What do you recommend? If you need me to back you up with the agency, let me know."
"Just make do with who showed up."

The first answer takes the monkey back and teaches her to bring you every problem. The second keeps ownership with her while offering support.

Does delegating pay off? Do the math

Delegation costs time up front. Back to Dana Kowalski's Chicago warehouse: the carrier report took her 3 hours a week. Training her shift lead, Luis, took 6 hours. For the first 4 weeks she spent 1 hour a week reviewing his drafts; after that, about 15 minutes.

Net weekly savings, weeks 1–4:  3 − 1    = 2 hours
Net weekly savings, week 5 on:   3 − 0.25 = 2.75 hours
Break-even: 6 training hours ÷ 2 hours per week = week 3
First year: (4 × 2) + (48 × 2.75) − 6 = 8 + 132 − 6 = 134 hours

The dip at the start is the training investment. From week 3 on, every week is pure gain, and the slope gets steeper when reviews drop to 15 minutes.

The Delegation Matrix sheet in the toolkit does this calculation for every task on your list. It assumes higher review time in the first 4 weeks and lower review time afterward, and it handles tasks that take longer than 4 weeks to break even.

3. Building next week's schedule takes you 4 hours. Training a shift lead would take 8 hours, and you'd review her drafts for 1.5 hours a week during the first month. In which week do you break even?

Week 2
Week 4
Week 8

Net savings during the first month: 4 − 1.5 = 2.5 hours a week. 8 ÷ 2.5 = 3.2, so you pass break-even during week 4 (after 3 weeks you've recovered only 7.5 of the 8 hours).

Stay in control without micromanaging

Control comes from clear agreements, not from hovering. Match the check-in frequency to the person's experience with the task (remember Situational Leadership from Lesson 2) and agree on it up front, so check-ins feel like a plan rather than distrust.

The person can explain the purpose and what "done" looks like.
We both said the delegation level out loud (1 to 7).
Check-in dates are on both our calendars, and they get less frequent over time.
I told them what to escalate right away (safety, legal, big customer issues).
I told the people who need to know that this person now owns the task.

Delegating only boring tasks.

Mix in work that builds skills people care about. Ask: "What would you like to learn this quarter?"

Redoing the work when it's not how you'd do it.

Judge the result against the agreed "done," not against your method.

Delegating the task but not the authority.

Tell others the new owner can decide, and don't overrule them in public.

Delegating and disappearing.

Schedule check-ins that fade as confidence grows.

4. You delegated a supplier comparison at level 6 (Inquire). Your team member chose a supplier you wouldn't have picked, but it meets all the criteria you agreed on. What should you do?

Reverse the decision, since you're still accountable
Ask them to walk you through the reasoning, share any lessons, and let the decision stand
Say nothing now and choose the supplier yourself next time

At level 6, they decide and you inquire afterward. Overruling a decision that meets the agreed criteria destroys trust and teaches people that delegation is fake.

Practice exercise

Priya, the remote engineering lead in Seattle, spends 2 hours a week preparing the sprint demo. She wants to hand it to a mid-level engineer, Sam. Training will take 5 hours. During the first 4 weeks she'll review Sam's prep for 1 hour a week; after that, 30 minutes.

In which week does Priya break even?
How many net hours does she free in the first 52 weeks?
Which delegation level would you suggest at first, and which after two months?

See solution

1. During the first 4 weeks she saves 2 − 1 = 1 hour a week, so by week 4 she has recovered 4 of the 5 training hours (cumulative −1). From week 5 she saves 2 − 0.5 = 1.5 hours a week. In week 5 the cumulative balance reaches −1 + 1.5 = +0.5, so she breaks even in week 5.

2. (4 × 1) + (48 × 1.5) − 5 = 4 + 72 − 5 = 71 hours, almost two full work weeks.

3. Start at level 5 (Advise): Sam decides what to demo and how, but Priya shares her opinion before the demo, which fits the 1-hour reviews. After two months, move to level 6 (Inquire): Sam runs it and they debrief afterward. A good script: "The demo is yours. For the first month, let's do a 1-hour run-through on Wednesdays where I give you my take. After that, you run it and we'll talk about how it went."

Summary

Delegation transfers responsibility and authority; you keep accountability for the result.
Delegate recurring and developmental work; keep reviews, pay, confidential issues and direction.
Say the level out loud, using Appelo's seven levels: tell, sell, consult, agree, advise, inquire, delegate.
Use the five-part conversation: what and why, what done looks like, level, resources and limits, check-ins.
Break-even = training hours ÷ net weekly savings. Most recurring tasks pay back within weeks.

Next lesson: One-on-One Meetings That Actually Work. You'll learn how to structure a 30-minute one-on-one, what to ask and how often to meet.