Leadership & Communication · Leading teams · lesson 2 of 21 · 13 min

Delegating effectively

Why delegation matters

Delegation is how leaders multiply their impact and how people grow. Leaders who do not delegate become bottlenecks, burn out and leave their teams underdeveloped. Yet many new managers struggle to delegate, because they can do the work faster themselves, fear losing control, or worry about being seen as lazy.

What to delegate

Delegate tasks that:

Others can do well enough now or with some support.
Would develop someone's skills.
Recur regularly (so the time invested in teaching pays back).
Are not the core of your own role (e.g., setting direction, sensitive people issues).

Keep tasks that require your authority or confidentiality, such as performance ratings or sensitive negotiations, unless they are part of a deliberate development plan.

Levels of delegation

Delegation is not all-or-nothing. Be explicit about the level:

| Level | What you say | Example | |---|---|---| | 1 | "Look into it and report back; I will decide." | Gather supplier options | | 2 | "Recommend a course of action; I will decide." | Propose a supplier with reasons | | 3 | "Decide, but tell me before you act." | Select supplier, inform me before signing | | 4 | "Decide and act; tell me afterwards." | Select and contract supplier within budget | | 5 | "Decide and act; no need to report back." | Routine purchasing under a threshold |

Confusion about the level causes frustration: you expected a recommendation and got a decision, or they expected authority and got overruled.

A delegation conversation: step by step

Explain the task and why it matters. Context helps people make good judgments.
Define the outcome and quality standard. What does "done" look like?
Agree the level of authority (from the table).
Clarify resources and constraints: budget, people, deadlines, policies.
Agree check-in points proportionate to experience and risk.
Ask them to summarise the task in their own words.
Follow up as agreed, and resist taking the task back at the first difficulty.

Delegation template

Task: Prepare the quarterly client satisfaction report
Why it matters: Leadership uses it to decide where to invest in service
Outcome: 4-page report with trends, top 3 issues, recommendations, by 15th
Authority level: 3 – decide content and format; show me before sending
Resources: survey data, last quarter's report, 1 hour with the analytics team
Check-ins: outline review on 5th; draft review on 12th
Development goal: build data storytelling skills

Monkey management

A classic idea in management writing is the "monkey on the back": a problem that someone brings to you and leaves with you ("I'll look into it"). Soon the leader carries everyone's monkeys. Instead, ask: "What do you recommend?" and "What will you do next?" Help them think; do not take the problem.

Worked example

Illustrative. Khalid, an operations manager at a fictional logistics company in Riyadh, worked late every night reviewing all route plans himself. He delegated route planning for two regions to experienced supervisors at level 4 (decide and act, tell me afterwards) with weekly reviews of on-time performance. For a newer supervisor, he used level 2 (recommend, I decide) for a month before moving to level 3. Khalid regained time for strategic work with major clients, and the supervisors reported feeling more trusted.

Delegation across cultures and hierarchies

In highly hierarchical settings, team members may hesitate to make decisions even when authorised, or may expect frequent approval. Be explicit and patient: state the authority level clearly, praise good independent decisions, and avoid reversing decisions publicly. In flatter cultures, people may expect more autonomy from the start.

Hands-on: a delegation brief and tracker

Use this brief for any task you hand over for more than a day. Send it in writing after the conversation so both of you have the same record.

DELEGATION BRIEF
Task:              
Why it matters:    (who uses the result, what decision it feeds)
Done looks like:   (format, quality bar, deadline)
Authority level:   1 look into it | 2 recommend | 3 decide, tell me first | 4 decide, tell me after | 5 own it
Resources:         (budget, people, tools, data access, AI tools approved for this task)
Constraints:       (policies, client rules, confidential data that must not go into AI tools)
Check-ins:         (dates, proportionate to experience and risk)
Development goal:  (what skill this builds)
Summarised back by the delegate: yes / no

Keep a simple tracker (a shared sheet or your task tool) so nothing is forgotten:

| Task | Owner | Level | Next check-in | Status | What I will NOT do | |---|---|---|---|---|---| | Q3 client survey | Hina | 3 | 12 Sep | Draft in progress | Rewrite her questions | | Supplier shortlist | Dan | 2 | 9 Sep | Recommendation due | Pick for him |

The last column is deliberate: write down the rescue behaviour you will resist.

Delegating to people who use AI tools. State which tools are approved, what data may not be pasted in, and that the delegate remains accountable for checking AI output before it goes anywhere.

Common mistakes

Delegating only boring tasks, never developmental ones.
"Dumping": delegating without context, resources or authority.
Micromanaging after delegating.
Taking tasks back when they get difficult.
Delegating responsibility without authority.
Forgetting that you remain accountable for the outcome.

Quick self-check

List everything you did last week. Mark each task: only I can do this; someone could do it now; someone could do it with training. Pick two tasks from the last two categories and delegate them this month using the template.

Video lecture: Delegating effectively

Lecture coming soon · 13 chapters · about 9 minutes. Read the full transcript below.

Delegation
Why it matters
The head chef
What to delegate
Five levels of authority
The delegation conversation
Worked example 1: Jess and Leo (illustrative)
Worked example 2: Faisal in Riyadh (illustrative)
Monkey management
Watch me: the delegation brief
Common mistakes
Is it working?
Recap and try this now

Lecture transcript

Delegation

Here's a question worth being honest about. How many things on your to-do list right now could someone else on your team do, perhaps not exactly the way you would, but well enough? If the answer is more than two, you've found your biggest leadership opportunity. In this lecture you'll learn what to delegate, how to be explicit about levels of authority, how to run a delegation conversation step by step, and how to stop tasks bouncing back onto your desk. By the end, you'll have a delegation brief you can use tomorrow.

Why it matters

Why does this matter? Because leaders who don't delegate become bottlenecks. Decisions queue up waiting for them, they work late, and their teams stop growing, because every stretching task stays with the boss. It's also a fairness issue. When you keep the interesting work, you deny people the experience they need to progress. So why do capable managers hold on? Usually three reasons. It's faster to do it myself. I'll lose control. And, quietly, I'll look lazy. Each of those feels true in the short term and is costly in the long term.

The head chef

Here's an analogy. Think of a head chef in a busy restaurant. If the head chef insists on cooking every dish personally, the kitchen serves twelve covers a night and everyone else peels potatoes. A great head chef designs the menu, sets the standard, trains each station, and tastes as plates go out. Their impact multiplies through the brigade. Notice what the chef doesn't give away: the menu, the standard and the final check. Delegation isn't abdication. You hand over the task, but you still own the outcome and the standard.

What to delegate

So what should you delegate? Tasks others can do well enough now, or with some support. Tasks that would develop someone's skills. Tasks that recur, because the time you invest in teaching pays back every month. And tasks that aren't the core of your role. What should you usually keep? Setting direction, performance ratings, sensitive people issues and anything that needs your authority or confidentiality, unless handing it over is a deliberate development step. Here's a quick test. If this task went slightly wrong, could it be fixed? If yes, it's probably delegable.

Five levels of authority

Here's the key idea of this lecture. Delegation isn't all or nothing. There are levels, and most frustration comes from not saying which one you mean. Level one: look into it and report back, I'll decide. Level two: recommend a course of action, I'll decide. Level three: decide, but tell me before you act. Level four: decide and act, then tell me. Level five: it's yours, no need to report back. If you expected a recommendation and got a signed contract, or they expected authority and got overruled, the problem wasn't the person. It was the missing level.

The delegation conversation

Now the conversation itself, step by step. First, explain the task and why it matters, because context helps people make good judgements. Second, define what done looks like, including quality and deadline. Third, agree the authority level. Fourth, clarify resources and constraints: budget, people, data, and which AI tools are approved. Fifth, agree check-ins proportionate to experience and risk. Sixth, ask them to summarise it back in their own words. That one step catches most misunderstandings. And seventh, follow up as agreed, and resist taking the task back at the first wobble.

Worked example 1: Jess and Leo (illustrative)

A simple worked example. Jess runs a small design studio in Manchester. Every month she spends a day compiling client invoices from timesheets. She delegates it to Leo, a junior who's organised and keen. She explains why it matters: cash flow depends on it. Done looks like: invoices drafted by the third working day, matching timesheets. Level three: Leo prepares them, Jess approves before they're sent. Two check-ins in month one. Leo summarises it back and spots that two clients need purchase order numbers. By month three, Jess moves him to level four. She's got a day a month back.

Worked example 2: Faisal in Riyadh (illustrative)

Now a realistic business scenario, illustrative. Faisal is operations manager at a logistics firm in Riyadh, managing eight team leads. He's become the bottleneck for supplier approvals: every purchase over an illustrative five thousand riyals comes to him, and the queue is two weeks long. He sets clear levels. Under twenty thousand riyals with an approved supplier, team leads decide at level four and log it. New suppliers: level two, recommend with three quotes. Above the threshold: level three. He also writes down what he won't do: re-open decisions made within the rules. Within a quarter, the approval queue drops to two days.

Monkey management

Let's talk about the bounce-back. There's a classic idea, sometimes called monkey management. A team member walks in with a problem, the monkey, and walks out without it, because you said, leave it with me, I'll have a think. Now it's on your back. Do that five times a day and you're carrying the whole zoo. Instead, ask: what do you recommend? What options have you considered? Then agree the next step, and who owns it. The monkey stays with them, and you stay available to help, not to rescue.

Watch me: the delegation brief

Watch me do it. I'm delegating the quarterly client survey to an illustrative colleague called Hina. I open the delegation brief. Task: run the survey and summarise results. Why: leadership uses it to decide where to invest in service. Done: a four-page summary by the fifteenth. Level three: she decides the questions, shows me before sending. Resources: last quarter's survey and our survey tool. Constraint: no client names pasted into public AI tools. Check-ins on the fifth and twelfth. Then I add a row to my tracker, and in the last column I write, what I won't do: rewrite her questions.

Common mistakes

Common mistakes. Delegating only boring tasks, so people never grow. Dumping a task without context, then being disappointed. Leaving the authority level vague. Hovering and micromanaging, or the opposite: disappearing until the deadline. Taking the task back at the first difficulty. Forgetting that you remain accountable, so blaming the person publicly when it goes wrong. And a new one: delegating to someone who'll rely on an AI tool, without saying what data can't go into it or reminding them that they own the checking. Delegate the task, never the judgement about quality.

Is it working?

How do you know your delegation is working? Look for four signals. First, your calendar: are you spending more of your week on direction, coaching and the few decisions only you can make? Second, cycle time: are decisions and approvals moving faster? Third, growth: are people handling tasks at higher authority levels than three months ago? And fourth, bounce-backs: how many tasks came back to you this month? Keep a simple tally for a few weeks. If the tally isn't falling, look at your own behaviour first. Are you really leaving the monkey where it belongs?

Recap and try this now

Let's recap. Delegation multiplies your impact and develops your people. Choose tasks that others can do, that build skills and that recur. Always name the authority level. Run the seven-step conversation, including the summary back. Keep the monkey with its owner. And remember you're still accountable for the outcome. Your try this now: pick one recurring task you do every week, fill in the delegation brief from the lesson, and have the conversation within the next five working days. Next, we'll look at motivating and developing the people you've just delegated to.

Key takeaways

Delegation multiplies impact and develops people; not delegating makes leaders bottlenecks.
Be explicit about the level of authority, from 'look into it' to 'decide and act'.
Explain why, define outcomes, agree resources and check-ins, and resist taking tasks back.
You remain accountable for outcomes you delegate.

Try it

Use the delegation template to hand over one task this week, including an explicit authority level and check-in points.