You hand off a project to someone on your team. You explain what needs to happen, answer their questions, and send them on their way.
Three days later, they come back with something that misses the mark completely. Wrong format. Wrong approach. Not even close to what you had in mind.
Your first thought: "I should have just done it myself."
Your second thought: "Why can't they figure this out?"
Here's the real problem: You didn't delegate. You dumped.
Delegation means giving someone the context, authority, and support to succeed. Dumping means handing off a task and hoping they figure it out. Most leaders think they're delegating when they're actually just offloading work and then wondering why it doesn't go well.
THE BIG INSIGHT
Delegation without context is just abdication with extra steps.
Dumping vs Delegating
Under pressure, delegation gets rushed.
When leaders are overloaded and trying to move fast, they skip the hardest part of delegation: setting someone up to succeed. Context gets compressed. Standards stay in their head. Checkpoints disappear.
What’s left isn’t delegation. It’s dumping.
Here’s what dumping looks like.
You say, “Can you handle the Q2 board deck?” and walk away.
No explanation of what the board cares about.
No guidance on which metrics matter.
No clarity on what success looks like.
Just “handle it.”
The person spends ten hours building something. You look at it and immediately know it’s wrong. Now you’re frustrated, they’re deflated, and you end up rebuilding it yourself.
That wasn’t a capability problem. It was a setup problem.
Real delegation looks different.
You say, “I need you to build the Q2 board deck and then follow it with:
Here’s why it matters: the board is nervous about cash burn, so they’ll focus on runway and unit economics.
Success means they leave confident we have 18 months of runway and a clear path to profitability.
I’d lead with our strongest metrics, then address their concerns directly.
Here’s last quarter’s deck for reference.
Build a draft by Friday and we’ll review it together before you finalize.
Same task. Completely different outcome.
What Real Delegation Requires
Delegation fails when the setup is incomplete. You don’t need a long checklist. Real delegation consistently comes down to three things:
Context. Why the work matters, who it affects, and what outcome you care about.
Standards. What “good” looks like in practice. Examples, references, or a clear bar.
A checkpoint. A review point early enough to correct course without taking the work back.
When these are in place, delegation stops feeling risky. You’re no longer hoping it works. You’re setting it up to work. From there, your role shifts. You stop being the answer and start developing judgment. If they come to you with a question, ask how they’re thinking about it before you weigh in. That’s how people learn to own work instead of waiting for approval.
QUESTIONS
Q: Doesn’t all this context take more time than just doing it myself?
The first time, yes. The second time, less. By the third time, you’re out of the loop entirely. That’s the return. Delegation isn’t about saving time today. It’s about not being required tomorrow.
Q: What if they still mess it up after I’ve set them up properly?
Then you have real information. Either they need coaching, clearer standards, or it’s not the right role fit. But you’re no longer guessing whether the failure was yours or theirs.
Q: How do I know when to step in versus step back?
Match your involvement to their competence on that specific task. Less experience means more structure. More experience means more space. The goal is independence, not permanent support.
If you hand off work without context, clarity, or support, you’re not developing your team. You’re setting them up to fail and then blaming them when they do.
Delegation done right takes more time upfront. But it’s the only way to build a team that can operate without you.
Chad Todd
chadtodd.com
