A VP I coached last year described his relationship with delegation this way: “I know I’m supposed to delegate more. Everyone tells me that. But when I hand something off and it comes back at 70% of what I would have done, I fix it myself. And then I’m working until 8 PM again and my team isn’t growing, and I know that’s the cycle but I can’t figure out how to break it.”

He was treating delegation as a workload management problem. Something goes from his plate to someone else’s plate. If the result is good enough, delegation worked. If it isn’t, delegation failed and the work comes back. Under that framing, delegation will always feel like a gamble — and for a leader whose identity is tied to the quality of the output, the gamble will usually feel like it isn’t worth taking.

The reframe that changed his approach — and that I’ve used with dozens of leaders facing the same pattern — is simple: delegation isn’t primarily about your workload. It’s primarily about their development. Every task you hand off is either a task transfer (you needed it off your plate and someone else executed it) or a development opportunity (you chose this task specifically because completing it will build a capability your direct report needs). The first kind manages your time. The second kind builds your team. And most leaders are so focused on the first that they never access the second.

Why “Just Delegate More” Is Useless Advice

The standard delegation advice treats it as a binary: either you’re doing the work or someone else is. The only variable is whether you hand it off. This misses everything that matters.

Delegation without context is task-dumping. The direct report gets an assignment with no understanding of why it matters, what good looks like, or how it connects to their development. They execute it as a chore. If they do it well, they’ve demonstrated competence. If they struggle, they’ve been set up to fail. In neither case have they grown — because nobody framed the work as a growth opportunity.

Delegation without support is abandonment. The leader hands off a stretch assignment and disappears — either because they’re too busy to check in or because they equate support with micromanagement. The direct report flounders, makes avoidable mistakes, and either produces something the leader has to redo or develops a fear of stretch assignments that makes them less likely to take risks in the future.

Delegation without debrief is a missed investment. The work is done, the outcome is acceptable, and everyone moves on to the next thing. Nobody pauses to ask: what did you learn? What would you do differently? What capability did this build that you didn’t have before? Without the debrief, the experience is just activity. With it, the experience becomes data in a development arc — the 70% of the 70-20-10 model that most organizations talk about but rarely operationalize.

The Four-Step Delegation Framework

Delegation as development isn’t harder than task-based delegation. It’s more intentional. The framework adds about 15 minutes of preparation and 10 minutes of debrief to each delegation event — and the return on that 25 minutes is a direct report who’s measurably more capable after every cycle.

Step 1: Choose the task for the person, not the person for the task. Standard delegation asks: who can do this? Developmental delegation asks: who needs to learn this? The task you delegate should stretch a specific capability your direct report is building. If they’re developing their stakeholder management skills, the right delegation isn’t the analysis that plays to their strengths — it’s the cross-functional presentation that challenges their growth edge. This means you need to know what each direct report is developing, which requires actual development conversations (not just performance reviews). If you don’t know what your people are working on developmentally, you can’t delegate developmentally.

Step 2: Frame the assignment as development, not just delivery. Tell them why you chose them for this, what capability it’s designed to build, and what the stretch is. “I’m asking you to lead the quarterly business review presentation because we’ve talked about your goal of building executive communication skills. This is a real opportunity to practice that in a high-stakes setting. I’ll be there, I’ll support you in the prep, and we’ll debrief afterward on what worked and what to adjust.” Compare that to: “Can you handle the QBR next week? I’m double-booked.” Same task. Completely different experience. The first version tells the person they’re being invested in. The second tells them they’re covering for someone’s scheduling conflict.

Step 3: Define the guardrails, not the process. The biggest mistake leaders make in delegation is specifying how the work should be done rather than what the outcome should be. When you dictate the process, you’ve removed the cognitive work that produces learning. The person is executing your plan, not developing their own judgment. Instead, define the outcome clearly (“The board needs a recommendation on the vendor selection with a clear rationale and a risk assessment”), the constraints (“Budget cap is $200K, and the decision needs to be made by March 15”), and the decision points where you want to be consulted (“Check in with me before you narrow to the final two candidates”). Everything between those guardrails is theirs to figure out. That’s where the development happens.

Step 4: Debrief the learning, not just the outcome. After the work is complete, spend 10 minutes on three questions: What did you learn about yourself in this process? What would you do differently if you had to do it again? What capability do you feel stronger in now than before you started? These questions transform the delegation from a completed task into a processed experience. The debrief is where the 70% of on-the-job development actually gets captured — without it, the experience is something that happened. With it, it’s something that developed.

The 80% Rule

One of the hardest adjustments for high-performing leaders is accepting that a delegated task will not be done as well as they would have done it — at least not the first time. The VP I mentioned earlier had an implicit standard: if it’s not at 100% of my quality, delegation failed.

That standard guarantees two outcomes: the leader never delegates anything that matters, and the team never develops the capability to operate at the leader’s level. The practical alternative is the 80% rule: if a direct report can do the task at 80% of your quality, delegate it. The 20% quality gap is the tuition you’re paying for their development. And with the debrief loop, that gap closes with each iteration.

The math is straightforward. A leader who does everything at 100% quality is one person operating at capacity. A leader who develops five people to operate at 80%—90% quality has a team with five times the capacity and the judgment to operate independently. The second leader’s team produces more total value, scales better, and doesn’t collapse when the leader takes a vacation or gets promoted.

The exception is narrow: when the stakes are high enough that the 20% quality gap would produce material harm — a board presentation, a regulatory filing, a key client deliverable — the leader may need to stay close. But those situations are rarer than most leaders claim. The vast majority of tasks that leaders hold onto aren’t held because the stakes are genuinely high. They’re held because letting go feels uncomfortable.

What to Delegate and What to Keep

Not everything should be delegated, and not everything should be kept. The filter is developmental value crossed with strategic necessity:

Delegate: Tasks that build capabilities your direct reports need, decisions that should be made at their level (not escalated to yours), and recurring work that someone else can own permanently. Also delegate the tasks you’re best at — yes, especially those. If you’re the best person at something, you’re the best person to teach it, which means you’re the worst person to keep doing it.

Keep: Work that requires your specific authority, relationships, or strategic perspective and can’t be replicated by someone else. The CEO relationship you manage personally. The board presentation that requires your organizational context. The crisis situation where the speed of your judgment matters more than someone else’s development. Keep the things only you can do. Delegate everything else.

Phase out: Work you’re still doing because you’ve always done it, not because it requires your level. The operational report you’ve produced every month for three years. The meeting you chair because nobody else has been given the chance. The vendor relationship you manage because you started it. These are the highest-opportunity delegation targets, because they’re well-defined enough to hand off cleanly and developmental for the person who takes them on.

Three Things You Can Do This Week

1. Audit your calendar for tasks you’re still doing that someone on your team could learn to do. Block 20 minutes and review your last two weeks. Highlight everything you did that a direct report could have done at 80% quality or better. Count the hours. That total represents your delegation opportunity — the time you could reclaim and the development you could create.

2. Choose one task to delegate this week using the development frame. Pick a specific task, pick the person whose development it would serve, and have the framing conversation: why them, what capability it builds, what the guardrails are, and when you’ll debrief. One task, fully framed. Not task-dumping — developmental delegation.

3. After any delegated task is complete, ask: “What did you learn?” Just that one question. Don’t evaluate the work first. Don’t jump to feedback. Ask them to reflect on what the experience taught them. If the answer is substantive, the delegation worked developmentally. If the answer is blank, the experience was a task, not a growth opportunity — and the framing needs to be stronger next time.

Delegation as development is one of the most powerful leadership practices available — and one of the least taught. It’s the mechanism that makes the 70-20-10 model operational: every delegated task, properly framed and debriefed, is a 70% development experience for the person who does it. Over six months of intentional delegation, a leader can measurably increase their team’s capability, judgment, and independence.

In coaching, we work on delegation patterns with the same rigor we bring to any leadership capability: identify the pattern (what you’re holding and why), design experiments (one developmental delegation per week), and debrief the results. Assessment data often reveals why the pattern exists — the Hogan Diligent scale that drives perfectionism, the EQ-i Independence that resists involving others, or the identity belief that value equals personal output. Learn about our coaching approach →

Struggling with delegation and not sure where the block is? A discovery call can help you figure out what’s driving the pattern and what would help. Schedule a discovery call →