You hand over a task and ask a colleague to take ownership. An hour later, they are asking permission for every small choice. That may be a confidence issue, but it may also mean the handover never explained what they were free to decide.
Useful delegation gives someone enough context to exercise judgement. It also makes the limits visible. A clear outcome with agreed boundaries usually creates a better starting point than either a vague instruction or a script for every movement.
Describe what finished work must achieve
Begin with the purpose and the evidence that would show the task is complete. For a fictional internal workshop, the outcome might be a confirmed agenda, accessible joining instructions and named facilitators by an agreed date. “Sort out the workshop” leaves too many interpretations open.
Ask the colleague to explain the outcome in their own words. This is a check on the handover, not an examination of the person. If you discover a different understanding, resolve it before discussing small formatting preferences.
Make the decision boundaries explicit
Write down which choices the colleague can make independently, which need consultation and which require approval. Include any budget, safety, privacy or contractual boundaries that apply. Do not assume that “use your judgement” overrides existing policies.
The Atlassian roles-and-responsibilities exercise encourages teams to compare what people believe they own and identify gaps or overlaps. A handover benefits from that same conversation: ownership should be understood on both sides, not merely assigned in a message.
Hand over the resources as well as the task
Identify the files, contacts, permissions and background decisions the person will need. Check access rather than sending a folder link and assuming it works. Explain which version of a document is authoritative and who can answer a specialist question.
Ask about capacity. A colleague may have the skill but not the available time. If the new task is a priority, discuss what should move or stop. Delegation that quietly adds another urgent item leaves the recipient to negotiate conflicting expectations alone.
Agree when to check in and when to escalate
Choose checkpoints around decisions that are expensive to reverse, not an arbitrary stream of status messages. In the workshop example, a review before invitations go out is more useful than correcting the wording after participants have already received it.
Agree what should prompt an earlier conversation: a supplier delay, missing approval, a risk outside the person’s authority or a change in scope. Make it clear that bringing an emerging problem forward is part of responsible ownership.
Review the handover after the work
Discuss where the instructions helped and where the colleague had to guess. Review the outcome against the agreed criteria, and distinguish a different working method from an actual problem. A task can be done well without reproducing your preferred sequence.
Use what you learn to improve the next handover. Over time, the goal is fewer avoidable surprises and more informed decisions by the person doing the work, rather than a manager who has to approve every detail.
Related reading: The Meeting Ended. Can Anyone Explain What Was Decided?.