Describe the result and why it matters
Explain the desired outcome, the deadline and how the result will be checked. Share necessary context rather than just forwarding a message. Let the colleague confirm their understanding in their own words. If the work is unfamiliar, agree on an initial small milestone before handing over the entire job.
Make decision authority visible
State which choices the person can make independently and which require approval. Include budget, customer commitments and policy boundaries where relevant. A vague instruction to 'use your judgment' is not enough if the owner later rejects every decision. Keep approvals proportionate to the consequence and the colleague's experience.
- Expected outcome and acceptance conditions.
- Available inputs, tools and capacity.
- Decisions allowed without asking.
- Conditions that require escalation.
- Check-in point and final handoff.
Worked example: supplier comparison
A hypothetical business owner delegates comparison of three suppliers. The colleague can gather quotes and assess delivery constraints but cannot sign a contract. The agreed output is a comparison with evidence, risks and a recommendation. A midpoint check focuses on missing requirements, not on rewriting every sentence of the eventual report.
Check at decision points
Agree on updates when important uncertainty can still be corrected. Constant interruption removes ownership; waiting until the final deadline can hide a preventable issue. Ask what changed and what decision is needed. If you take the task back, identify why and how the delegation brief should improve next time.
Review the result without erasing ownership
Compare the work with the agreed conditions, not an unstated personal preference. Recognize sound decisions even when they differ from your method. Discuss errors as specific learning points and update the process. Delegation becomes easier when the team can predict how authority and accountability work, rather than guessing what the owner will accept today.