Delegation rarely fails during the work itself. It fails at the handoff — and in the follow-up that never gets designed.
It fails at the handoff, not the execution
Most failed delegation starts with an unclear definition of done. The task is described, but the standard is not: what a good result looks like, what the deadline actually means, what is fixed and what the person is free to decide. The person delivers something reasonable, the manager expected something else, and both leave the exchange more cautious than before.
Before handing anything over, answer three questions in writing if needed: what does finished look like, what are the constraints, and what decisions belong to the person doing the work.
Delegation without follow-up becomes one of two bad things
Without an agreed follow-up point, delegation drifts into abdication — the manager disappears until the deadline and is surprised by the result — or into micromanagement, checking in whenever anxiety strikes. Both teach the team the same lesson: handing work to this manager is unpredictable.
The fix is boring and effective: agree the checkpoint at the moment of handoff. One midpoint review for a two-week task. A weekly look for anything longer. The person knows when they will be asked; the manager knows when they will see progress. Nobody has to chase or hover.
Delegate outcomes with constraints, not methods
Handing over your own method invites two problems: the person executes a script they do not fully understand, and every deviation feels like a mistake. Delegating the outcome — with clear constraints on budget, tone, deadline, or risk — leaves room for a method that fits the person doing the work.
This is also how capability grows. Someone who has only ever executed your instructions can follow. Someone who has owned an outcome inside clear boundaries can eventually be trusted with bigger ones.
Some things should not be delegated
Performance conversations, final hiring decisions, and anything the team would reasonably expect to hear from you directly stay with the manager. Delegating those does not free time; it erodes trust.
A practical test for everything else: if the task recurs, document it once and delegate it with the documentation. If it is a one-off judgment call with real consequences, keep it — and let the team watch how you make it.
