Think about the last task you handed over to someone on your team. Now ask yourself three questions:
- Did they know why it mattered, or just what to do and by when?
- Did they have the authority to make decisions about it without you?
- When it hit a snag, did they fix it, or did it land straight back on your desk?
If the honest answers are no, no and “back on my desk”, then the truth is – that wasn’t delegation. That was offloading with a nicer name.
From where you’re sitting, the two feel identical. The task left your plate. You felt the relief. You mentally filed it under “delegated” and moved on to the next thing. The difference only shows up on their side of the handover and by the time you notice, it usually looks like a performance problem rather than what it actually is – a handover problem.
I want to talk today about why offloading masquerades as delegation so convincingly, the warning signs that you’ve been dumping rather than delegating and how to hand things over so they actually stay handed over.
Why offloading feels like delegation (to you)
Let’s be honest about the psychology here, because it’s not flattering.
When you hand over a task, your brain registers one thing – relief. The task is gone. Your to-do list is shorter. Whether you delegated it properly or lobbed it over the fence, that feeling is exactly the same. There’s no internal alarm that goes off when you’ve transferred workload without transferring ownership.
Worse, there’s a self-serving bias at work. The tasks we most want off our plates are, funnily enough, the ones we least enjoy. So we hand over the grunt work, the awkward stakeholder, the report nobody reads and we call it a “development opportunity”. Everyone on your team can tell the difference. They know when they’ve been given something because it will stretch them and when they’ve been given something because you couldn’t be bothered.
And here’s the connection to what I wrote about previously in Just Tell Me What You Need – someone who’s been dumped on can’t easily ask for help. The task arrived with an implicit message – this is yours now. So when they hit the inevitable wall (inevitable, because you never gave them the context to see it coming), asking for help feels like handing the task back. It feels like failing the test. So they struggle in silence and you get the quiet signals of a team member who’s stuck without ever connecting them to your own handover.
Real delegation transfers three things:
- The outcome.
- The authority.
- The context.
Offloading transfers one thing – the work. That’s the whole difference and it’s everything.
The warning signs you’re dumping, not delegating
The good news, as ever, is that this leaves evidence. Here are four signs to watch for in your day-to-day role:
The boomeranged task
The task keeps coming back to you for decisions. They do the doing, but every fork in the road gets escalated. If you find yourself making all the meaningful calls on something you “delegated”, then you haven’t delegated it. You’ve kept the thinking and given away the typing.
The photocopy problem
They’re not exercising judgement, they’re guessing at yours. The work comes back as an attempted impression of what you would have done, usually a slightly worse version, because they’re working from clues rather than context. This isn’t a capability gap. It’s what happens when someone has accountability without understanding.
The “development opportunity” nobody develops from
The same tedious tasks keep landing on the same people, wrapped in growth language. If you can’t articulate what someone will genuinely learn from a task beyond “how to do the task”, it’s not development. It’s distribution.
You can’t remember what you’ve delegated
This one’s genuinely uncomfortable. If you’ve truly delegated something, you know, because letting go of it costs you something. You felt the twinge. If you can’t actually recall who owns what across your team, you probably haven’t been delegating at all. You’ve been allocating.
Five ways to hand things over properly
Right, onto what to do about it.
1. Delegate outcomes, not tasks
I’m a big, big fan of this mindset and it’s served me well over the years.
The instinct is to hand over a to-do list – do this, then this, by Friday.
Resist it.
Hand over the destination instead: “By the end of the month, the client needs to feel confident enough in our plan to sign off on the next phase. How you get there is yours to work out.”
When you delegate the task list, you keep ownership of the thinking and the thinking is the part that develops people. When you delegate the outcome, the person has to engage with why, which means they can adapt when reality doesn’t match the plan. Which it won’t.
2. Name the decision rights out loud
Most delegation fails at an invisible line – what the person is actually allowed to decide without you. Nobody ever says it, so people guess and they guess conservatively, then you get the boomerang.
Say it explicitly: “You decide the format, the messaging and the timeline without me. Loop me in before anything goes to the client or if the budget moves.”
3. Transfer the context, not just the work
There’s a ten-minute conversation that managers skip constantly:
- Here’s why this matters.
- Here’s who cares about it.
- Here’s what happened last time.
- Here’s the problems to avoid.
We skip it because we’re busy and because the context is so obvious to us that we forget it isn’t obvious at all.
That ten minutes is the difference between someone exercising judgement and someone photocopying yours. If you don’t have ten minutes to hand over the context, you don’t have time to delegate. You just have time to dump.
Ironically – by trying to save ten minutes now, you’re probably costing yourself an hour later.
4. Agree the check-in structure upfront
“I’ll leave you to it” sounds like trust but often functions as abandonment. On the other hand, ad-hoc “just checking in” messages feel like surveillance, and before you know it you’ve slid into micromanagement while telling yourself you’re being supportive.
The fix is to agree on the rhythm at the point of handover: “Let’s look at it together every Tuesday. Between those, it’s yours.” Scheduled support is trust with a structure.
5. Resist the snatch-back
I won’t lie, this one is hard.
At some point, the thing you delegated will wobble. Every part of you will want to take it back, because you could fix it faster and because watching someone struggle with something you’re good at is genuinely painful.
Don’t. The moment you reclaim a task at the first sign of trouble, you teach the person (and everyone watching) that you never really meant it. Next time, they won’t take ownership, because why would they? Coach them through the wobble instead. Ask what they’re seeing, what options they’re weighing, what they’d do if you were on holiday. The wobble is where the development actually happens.
If you want to test this, pick one task you believe you’ve delegated. Go and ask the person who owns it two questions:
- What does success look like on this?
- What are you allowed to decide without me?
If they answer both crisply, congratulations, you delegated. If they hesitate on either, don’t treat it as their gap. It’s yours. You now know exactly what this week’s conversation needs to be.
The best managers don’t hand over tasks. They hand over ownership and then they do the genuinely hard part: they leave it handed over.
