06 · Empowering Others (Delegation Basics)¶
Delegation is the most visible mechanism servant leaders use to grow the people they lead — but delegation done badly is either abdication ("figure it out yourself, good luck") or fake delegation ("do it, but exactly the way I would"). Real empowerment means handing over enough real ownership that the person can grow from the work, while staying available as a resource, not a rescuer. This module covers a concrete model for calibrating how much to hand over, and how to hand it over well.
1. Why leaders under-delegate¶
Before the "how," it's worth naming why delegation is hard, because the reasons matter for fixing them:
- "It's faster if I just do it myself" — true for this one task, false as a strategy, since it guarantees the leader remains the bottleneck forever and the other person never builds the skill.
- Fear of a worse outcome — the work might come back not exactly as the leader would have done it, which feels like a risk, but is often actually fine (or even better) and is nearly always the price of someone else learning to do it.
- Identity attachment — some leaders' sense of value is tied to being the one who does the hard technical work, which delegation directly threatens.
- Not having built enough trust (Module 5) to believe the other person will actually deliver — in which case, the fix is building trust through small delegated tasks first, not avoiding delegation altogether.
2. The delegation levels model¶
Not all delegation should hand over the same amount of authority. A useful ladder, adapted from situational leadership models:
| Level | What the leader says | When to use it |
|---|---|---|
| 1. Do exactly this | "Do X, this way, by this time" | New task, high stakes, or someone brand-new to the work |
| 2. Research and report | "Look into this and tell me what you find; I'll decide" | Person can gather information but the decision still needs the leader's judgment or authority |
| 3. Recommend and check | "Decide what you'd do, tell me, and I'll say go/no-go" | Growing confidence — person's judgment is usually right, but not yet fully trusted alone |
| 4. Decide and inform | "Make the call, then let me know what you did" | High trust — leader wants visibility but isn't gating the decision |
| 5. Full ownership | "This is yours — I don't need to be looped in" | Full trust and competence established |
Most delegation mistakes come from picking the wrong level: handing Level 4 or 5 to someone who needed Level 2 support (they flounder and the outcome suffers, quietly confirming the leader's fear that delegation doesn't work) or staying at Level 1 or 2 with someone who's ready for Level 3 or 4 (which is functionally not delegating at all, and blocks their growth).
3. The delegation conversation¶
A short structure for actually handing something off:
- State the outcome, not just the task. "I need the onboarding doc updated so new hires stop asking the same three questions" gives more useful context than "update the onboarding doc."
- State the delegation level explicitly. "This is a Level 3 for you — come to me with your plan before you start building it" removes ambiguity about how much checking-in is expected.
- Name the boundaries, not the method. Constraints (deadline, budget, who else needs to be consulted) should be explicit; how to do the work within those boundaries should be the other person's call whenever the delegation level allows it.
- Confirm understanding by asking them to restate it, the same reflecting technique from Module 3 — not "does that make sense?" (which invites a reflexive "yes"), but "what's your plan for the first step?"
4. A worked example¶
A team lead, Yusuf, needs a recurring weekly report automated instead of built by hand every Friday. Two approaches:
- Fake delegation: Yusuf hands it off but specifies the exact spreadsheet layout, tool, and steps to use — the person executes his plan rather than building their own, learns little beyond following instructions, and any future report request still routes back through Yusuf's specific method.
- Real delegation (Level 3): Yusuf states the outcome ("the report needs to exist every Friday morning without anyone manually pulling it"), the boundary (needs to use existing data-access permissions, budget for any new tooling is $0), and the level ("show me your plan before you build it, then it's yours to run"). The person proposes an approach Yusuf wouldn't have picked, which turns out to work well and which they now own end-to-end — freeing Yusuf's time permanently, not just this week.
How It Actually Works¶
Delegation is often described loosely as "handing off a task," but what is actually being transferred is two distinct, separable things: decision rights (who gets to choose between options) and accountability (who bears the consequences of the choice). Under-delegating leaders usually transfer the work — they let someone execute steps — while quietly retaining both the decision rights (they specify exactly how) and, in their own mind, the accountability (they'll take the blame or credit either way). That's not delegation; it's supervised labor. Real delegation at the higher levels of the delegation-levels model requires transferring decision rights to the other person, which is precisely why it produces anxiety in the delegating leader: they are now exposed to outcomes decided by someone else's judgment, not their own.
Why leaders under-delegate even when they know intellectually that they should. This is well explained by a mechanism from prospect theory: losses loom larger than equivalent gains. Delegating a decision has an asymmetric payoff structure for the leader — if it goes well, the credit is diffuse (the team did fine, unremarkable); if it goes badly, the leader owns a vivid, attributable failure ("I let them decide and it went wrong"). Since the downside is emotionally weighted roughly twice as heavily as the upside (per the loss-aversion research also underlying the trust module), a purely rational-feeling calculation still tilts leaders toward retaining control, even when the expected value of delegating is positive. Naming this bias explicitly is often what breaks it — leaders can consciously correct for a bias they can't feel their way past.
Why unclear delegation ("just take ownership of this") fails predictably. Decision rights only transfer meaningfully when the scope of the transferred authority is specified — otherwise both parties default to their own guess about what was actually handed over, and the gap surfaces later as either the leader overriding a decision they thought was still theirs, or the report making a call they thought was authorized and getting corrected after the fact. This is the same information-asymmetry problem that shows up in principal-agent theory in economics: an agent acting on incomplete knowledge of the principal's true preferences will systematically make choices the principal didn't want, not from incompetence but from a genuine gap in shared information about the boundaries of the delegated authority.
Exercise¶
Pick one task currently on your own plate that you're doing purely out of habit, not because it strictly requires you. Using the delegation levels table, decide which level is realistic for who you'd hand it to today (be honest — it might be Level 1 or 2 if they're new to it, and that's fine). Write out the actual delegation conversation you'd have, using the four-step structure above: the outcome, the level, the boundaries, and the question you'd ask to confirm understanding. Then have that conversation for real this week.