Delegation usually fails at the handover, not at the work. The task left your desk with a sentence and a deadline. It came back in a shape you did not expect, you redid it yourself, and you concluded that it is faster to do everything alone. That conclusion is expensive and almost always wrong, because the handover was never designed.

Delegate outcomes, not steps

Telling someone to update the spreadsheet produces a spreadsheet. Telling them the stock report needs to be accurate enough for the buying decision on Thursday produces a person who checks the numbers. The second version gives them a reason to make judgement calls, which is the point of delegating.

Describe the result, the deadline, and the standard. Let them choose the method, unless the method is the thing that matters.

Write the definition of done

A definition of done is three or four observable conditions. The report is sent to the supplier by Thursday noon, includes last month's variance, and flags anything below the reorder point. Anyone can check whether that happened.

Without it, quality becomes a matter of taste, and taste is hard to give feedback on. With it, feedback becomes a short comparison against a list.

Hand over context, not just the task

Explain why the task exists, who uses the output, and what happens if it is late. People make better decisions when they know the consequence. They also ask better questions, which is a sign the handover is working.

Point them to the last good version of the output. One example does more than three paragraphs of explanation, because it shows the standard in the form it will be judged.

If the only person who can tell whether the work is right is you, the work is not delegated yet.

Agree the checkpoints in advance

For a task that takes more than a day, agree one midpoint. Not a status update, a real checkpoint where a wrong direction can still be corrected cheaply. For a task that takes an hour, no checkpoint is needed.

More checkpoints feel safer and teach nothing. The person learns to wait for approval rather than to make decisions, and you become the bottleneck you were trying to remove.

Review the output, and expect a learning curve

When the work comes back, check it against the definition of done. Resist rewriting sentences that are merely different from how you would write them. Style differences are not quality failures, and correcting them teaches the wrong lesson.

Fix things that are wrong, note things that are borderline, and leave the rest. Then say explicitly what was good, using a specific example rather than a general compliment.

Give access before you need it. Permissions requests, two-factor codes, and shared folder invitations always take longer than expected, and a first day spent waiting for login details teaches the new owner that the process is chaotic. Test the access yourself the day before the handover.

The first delegation takes longer than doing it yourself. That is the cost of the second, third, and tenth time, which take minutes instead of hours. Most people quit during the first attempt, which is why they never get the later benefit.

Budget for the learning curve out loud. Tell the person the first version will need edits, and that this is normal rather than a failure.

Build a one-page guide for recurring tasks

Once a task has been done twice, write the steps down. Keep it to one page: the outcome, the inputs, the steps, the checkpoints, and the definition of done. The next person to do it starts from the page rather than from a conversation.

Update the page when the process changes. A stale guide is worse than no guide, because it teaches the old method with confidence.

Delegation checklist

  • Outcome described in one sentence, with a deadline.
  • Definition of done written as observable conditions.
  • One example of good previous work attached.
  • Named checkpoints agreed, no more than one for short tasks.
  • Access and permissions confirmed before the start date.
  • Review against the criteria, not against personal style.
  • One-page guide created after the second run.

Delegation is a design task. Spend twenty minutes on the handover and you save the hour you would have spent redoing the work.