Reverse Delegation: Why Work Keeps Coming Back
Reverse Delegation: Why Does Work You Handed Off Keep Coming Back?
You hired people so the work would stop running through you. For a while it helped. Then the same things started coming back to your desk: a decision you thought was made, a project that stalled at a handoff, a standard you set on Monday that had slipped by Friday. You're busy all day, and you're still the one keeping the work on track.
There's a name for this, and understanding it is the first step to stopping it. It's called reverse delegation, and it has almost nothing to do with how hard your team works.
What is reverse delegation?
Reverse delegation, sometimes called upward delegation, is when work you handed to someone on your team makes its way back up to you. You gave the task, the decision, or the project to a capable person, and a few days later it's back with you, waiting for your input, your sign-off, or your save.
The classic version is the decision that comes back "just to check." You handed it over, but the person doesn't have everything they need to make it, so they bring it back rather than get it wrong. Multiply that across a growing team and a growing workload, and you get a week where you're the person every loose end returns to.
The important part is what reverse delegation is not. It isn't a sign that your people are lazy or that you hired badly. Capable, motivated people send work back up when the way the team operates hasn't given them what they need to keep it. The pattern is about the operations, not the person.
The signs you're living with reverse delegation
Most leaders notice it in the same handful of ways:
Decisions that should be made a level below you come up to you instead.
Work that crosses team lines stalls until you step in.
Standards you set in a meeting don't survive the week.
Problems reach you late, after they've already grown.
New hires take far longer than you expected to carry real weight.
If two or three of those sound like your week, you're not disorganized and your team isn't failing. Something about how the work moves through your team hasn't kept up with how much the work has grown.
Why haven't the usual fixes worked?
Most leaders reach for the same three responses, and the work keeps returning anyway.
Hiring more people.
A stronger hire feels like the answer. But capable people join the same way of working, and within a quarter the work moves through the team the way it always did. The problem was never the people.
More meetings and updates.
Another check-in gives you more visibility into the work coming back. It doesn't change what sends the work back in the first place.
New tools and software.
A tool can organize the work, but it can't decide who owns a task or keep a standard the team hasn't built. So the work still returns.
Here's the useful part: if hiring, meetings, and tools haven't fixed it, that's the clue. The work isn't coming back because of effort or talent. It's coming back because of how the team operates, and that's a different thing to build.
The real reason work comes back to you
Your business grew. The team grew. The way the team works together didn't grow with it.
Operations are the clear standards for how your team actually works day to day: how a decision gets made, how a problem gets raised, how work moves from one person to the next. When those standards are clear and shared, the work stays where you hand it. When they aren't, it comes back to the one person the whole team can count on to catch it, and that person is you.
When the business was small, those standards traveled through proximity and conversation. Your team picked them up because they were around while you set them. As the team grew, the standards stayed where they were, in your head, and the way the team works together never got built into something the team can use without you. That's the quiet cause underneath reverse delegation.
The four gaps that send work back
When you look closely at what comes back, it comes back through four specific gaps. Each one is a standard the team doesn't have yet.
No one owns it across team lines. When work moves between teams, no single person owns it end to end, so it stalls and comes back to you.
Decisions wait for you. The team doesn't have what it needs to decide, so the decision comes up to you when it could be made closer to the work.
Standards don't hold. What you set in the meeting isn't built into how the work runs, so it slips by the end of the week.
Problems surface late. Issues reach you after they've grown, because nothing brings them up early where the work happens.
Build the standard for a gap, and the work stops coming back through it. You don't have to fix all four at once, which is exactly why the next step is to find the one that's costing you the most.
How do you stop reverse delegation this week?
You don't need a reorganization. You need one week of paying attention.
For one week, keep a short written record. Every time something you thought was handled comes back to you, write down what it was and mark which of the four gaps it came through: no owner, waited on you, standard slipped, or surfaced late. At the end of the week, the gap with the most marks is the one costing you the most time.
Then take one step: name the single standard the team is missing there, and decide who needs to be in the room to set it. That one standard is the first operation to build, and it's usually the difference between a week you spend catching work and a week you spend on the work only you can do.
Take the first step toward work that stays handed off
Reverse delegation stops when you find the gap that sends the most work back and build the one standard behind it. Our free field guide, Why the Work Keeps Coming Back to You, walks through all four gaps and includes a one-week comeback log so you can find your own pattern in a few days.
→ Download the free guide: loyaltyops.com/work-comes-back
FAQ
What is reverse delegation?
Reverse delegation, also called upward delegation, is when a task, decision, or project you handed to someone on your team comes back up to you. It usually happens because the person doesn't have what they need to finish or decide, so they return the work rather than get it wrong.
Is reverse delegation my team's fault?
No. Capable people send work back up when the standards for how the team operates haven't given them what they need to keep it. The cause is the operations, not the people, so the fix is to build the missing standard rather than to push harder on the team.
How do I stop work from coming back to me?
Track what comes back for one week and mark which of four gaps each item came through: no clear owner, a decision that waited on you, a standard that slipped, or a problem that reached you late. Build the one standard behind your most common gap first.
What's the difference between delegation and reverse delegation?
Delegation is handing work down to the person closest to it. Reverse delegation is that same work traveling back up to you afterward. Good delegation stays delegated because the team has the standards to keep it; reverse delegation is the signal that one of those standards is missing.
Why do new hires take so long to become productive?
Often because the standards for how the work runs live in your head instead of in how the team operates. A capable new hire can't absorb what was never written into the way the team works, so they check with you more and for longer than you expected.