Delegation
delegating · handing off work
Transferring responsibility for an outcome, not just the task. Real delegation includes the authority to decide, which is why most attempts fail — the work moves and the decisions do not.
In practice
'Handle onboarding' is a word. The outcome, the limits, the decisions they can make without asking, and what finished looks like is a handover.
The common mistake
Delegating the doing and keeping the deciding. The work leaves your calendar and the judgment stays, so your capacity is unchanged and you have added a coordination cost.
Delegation is transferring responsibility for an outcome to someone else. It differs from assigning tasks, which is what most people do when they believe they are delegating.
Tasks and outcomes
Handing over a task means specifying the steps and retaining the judgment. You still decide what good looks like, when it is finished, and what to do when something unexpected happens. The work moves and the load does not.
Handing over an outcome means the other person owns the result, including the decisions inside it. That is the only version that returns capacity, and it is the version that requires accepting a different standard of execution than your own.
Why it fails
Three reliable causes.
It is slower at first. Explaining takes longer than doing, and the first attempts are worse. This cost is real, arrives immediately, and the benefit arrives later, which is why the decision keeps being deferred on rational grounds.
The standard was never stated. "Handle the onboarding" transfers a word. What gets handed over usefully is the outcome, the constraints, the decisions they can make alone, and what a finished version looks like.
The work comes back. Someone brings you a problem, you solve it, and responsibility has silently returned. The habit that prevents this is asking what they recommend before answering, every time, including when you already know the answer and it would be faster to say it.
What to hand over first
Work that is frequent, documented and low-variance — the things where your judgment adds least. Recurring reporting, first-draft anything, scheduling, qualification.
What to keep is a shorter list than most owners assume: the decisions that set direction, the relationships that carry real risk, and the work only you can do. Everything else is a candidate, and the barrier is usually the discomfort of watching it done differently rather than any real constraint. See owner dependency and leverage.
There is a stronger argument for all of this than the one usually given. The usual argument is that you cannot do everything, which is about capacity and invites the reply that you will work harder. Comparative advantage says something else: even with unlimited capacity, doing the work yourself is the wrong allocation, because the hour has a higher use elsewhere. The condition is that the freed hour actually goes to that higher use. An owner who delegates without a better use lined up has bought nothing but cost.
Concept web
Open the full webQuestions
What is the difference between delegating a task and delegating an outcome?
Delegating a task moves the work while you retain the judgment about what good looks like. Delegating an outcome moves the decisions too, which is the only version that returns your capacity.
Why does delegation feel slower?
Because it is, at first. Explaining takes longer than doing and early attempts are worse. The cost is immediate and the benefit is delayed, which is why the decision gets postponed indefinitely.
How do you stop delegated work coming back?
Ask what they recommend before you answer, every time. Solving the problem they bring you transfers responsibility back, even when you were only trying to help.