6 min read
How to delegate without it coming back to you
Offloading tasks while keeping every decision is not delegation. It is just typing less.
Every founder has handed something off and watched it come straight back — half-done, slightly wrong, or with a question that only they can answer. The usual conclusion is that no one can do it as well, so it is faster to keep it. That conclusion is the trap. The problem is rarely the person. It is what was handed over.
Tasks versus results
Most failed delegation is the handoff of a task while the decision stays with you. You ask someone to draft the proposal, but you decide the price, the scope, and the framing. They are not running the work; they are typing it. Every real choice still routes back, so your load barely changes and the work feels like it never left.
Delegating a result is different. You hand over the whole outcome — the proposal, priced and sent — with the authority to decide inside clear boundaries. The boundaries are the point: here is the outcome, here is the standard, here is the budget, here is when to escalate. Inside them, the owner decides. That is what actually removes you.
The handover that sticks
A clean handover names four things:
- The outcome. What done looks like, in the world, not the steps to get there.
- The standard. How you tell a good result from a poor one, concretely enough that the owner can judge their own work.
- The boundaries. The decisions they own outright, and the few that genuinely need you.
- The checkpoints. When you will look — at the result, not over their shoulder.
Coach the gap, do not reclaim
The first attempts will be rougher than yours. This is not evidence the handover failed; it is the cost of it succeeding. The instinct to take the task back the moment it is imperfect is what keeps founders trapped. Correct the gap instead — show what good looks like, point at the difference, let them try again. Within a few cycles the standard rises to yours and stays there, and the work is genuinely gone from your desk.
Why it is worth the discomfort
Reclaiming feels efficient in the moment and is expensive forever: the work never leaves. A handover that holds costs more this month and pays back every month after. Done across enough areas, it is the difference between a founder who is the system and a business that runs on one.
Questions
Why does delegated work keep coming back to me?
Usually because what was handed over was a task, not a result, and the decisions still sit with you. If the owner has to check with you to proceed, you have not delegated the work — you have added a step. Hand over the whole outcome with the authority to decide inside clear boundaries, and the return trips stop.
How do I delegate when quality matters?
Define the standard of done explicitly, then coach to it. Most founders hold work back because the first attempts will not match their bar — which is true, and temporary. Describe what good looks like, let the owner attempt it, and correct the gap rather than reclaiming the task. Within a few cycles the standard transfers and holds.
Find your first handover
A three-minute diagnostic that surfaces where work keeps routing back to you — and the cleanest place to start delegating.
Find your first handover