Delegation: How to Hand Over Work So It Actually Holds
How to Delegate Outcomes, Not Just Tasks
By Andrew Lee Ward 3 min read Updated 27 Jun 2026
To delegate an outcome rather than a task, hand over four things together: the outcome the person owns, the standard it must meet, the constraints they must respect, and the check-ins you'll use. Task-handing tells people what to do; outcome-handing makes them responsible for whether it actually works.
Most delegation fails quietly. You hand someone a task, they complete the task, and the outcome still lands back on your desk — because the thing you actually needed was never theirs to own. They touched the task; they were never carrying the result.
The fix is to delegate outcomes, not tasks. The distinction sounds small and changes everything.
Task-handing vs outcome-handing
Task-handing and outcome-handing differ in what the person is left holding: an action versus a result. The gap shows up the moment something goes wrong.
- Task-handing: "Send the status report to the client." The person is responsible for the action. If the client is still confused, that's your problem.
- Outcome-handing: "Make sure the client has what they need to make their decision by Friday." The person is responsible for the result. If the client is confused, fixing that is part of the job they own.
Outcome-handing is how a team's capacity actually grows, because it transfers judgement, not just hands.
What to hand over
A clean outcome handover transfers four things at once — the outcome, the standard, the constraints and the check-ins. Effective delegation has long been described as handing over a whole result with the authority and information to own it, not just the next action.1
Delegation holds when you hand over four things at once:
- The outcome — the result the person now owns, stated plainly.
- The standard — what "good" looks like, so they can judge their own work.
- The constraints — the budget, deadline, and non-negotiables they must respect.
- The check-ins — how and when you'll stay informed, agreed up front so it feels like support, not surveillance.
Hand over the outcome without the standard and you'll get work that misses the mark. Hand over the standard without check-ins and you'll discover the miss too late. The four travel together.
"Delegate the outcome and the standard, not the keystrokes. The day you start correcting how, you've taken the what back." — The Control Standard
Step in or step back?
The step-in-or-step-back decision is the live question once an outcome is delegated: when do you intervene, and when do you let the person run? A simple lens is to weigh the risk of the work against the capability of the person. High risk and low capability means step in and stay close; low risk and high capability means step back and let them run. This echoes the situational-leadership idea, set out by Paul Hersey and Ken Blanchard, that the right amount of direction depends on the follower's readiness for the task at hand. Most over-management comes from applying "step in" to people who have earned "step back" — and from letting the work quietly bounce back up, the "upward delegation" William Oncken and Donald Wass warned about when they asked who ends up holding the monkey.2
This is the surface of a deeper practice. The Control Standard works through the levels of delegation, how to set a standard that travels, and how to judge each step-in moment without becoming the bottleneck — which is the failure mode the next guide tackles directly.
- Jenny Blake, "To Be a Great Leader, You Have to Learn How to Delegate Well," Harvard Business Review (2017).
- William Oncken Jr. & Donald L. Wass, "Management Time: Who's Got the Monkey?" Harvard Business Review (1974, reissued 1999).
Frequently asked
What's the difference between delegating a task and delegating an outcome?
What should I hand over when I delegate?
How do I delegate an outcome without losing control of it?
What if the person does it differently from how I would?
When should I step in versus let them run?
Can you delegate an outcome to someone junior?
Keep reading
How to Stop Being the Bottleneck Your Team Waits On
You become the bottleneck when too many decisions and too much context route through you alone. The way out is to make your expectations predictable, push decision rights down with clear guardrails, and let people act from their remit rather than waiting for instruction — so work moves when you're not in the room.
TermAccountability vs Responsibility
Responsibility is for doing the work; accountability is for the outcome. Several people can be responsible for the tasks, but one person is accountable for whether the result actually lands. Responsibility can be shared and handed around; accountability cannot be divided without disappearing — which is why every important outcome needs a single accountable owner.
TermBus Factor
The bus factor is the number of people who would have to be lost — "hit by a bus" — before a project stalls because critical knowledge or access went with them. A bus factor of one means a single person is a single point of failure. Raising it is a core goal of good ownership and delegation.
TopicDelegation: How to Hand Over Work So It Actually Holds
Effective delegation means handing over an outcome — not just a task — with a clear standard, sensible constraints and the right check-ins, so the work comes back finished rather than bouncing back to you. Done well, it raises a team's capacity and lowers the manager's role as bottleneck.
TermRouting vs Leading
Routing vs leading is the distinction between processing your team's work one item at a time — answering questions, making small decisions, unblocking people — and acting on the system that produces that work: its standards, decision rights, and handoffs. Routing feels productive; only leading compounds.