
The short answer
What to know before you act
Delegate an outcome with context, authority, constraints, resources and a review point. Ask the receiving owner to explain the plan and likely exceptions. Use support and sampling appropriate to the risk; do not silently retain approval over decisions you said were delegated.
- Define the result: activity alone rarely establishes completion.
- Agree the decision boundary: authority must match responsibility.
- Review without reclaiming: coach the judgement rather than rewriting every decision.
“Please handle this” can sound like delegation while leaving the recipient to guess the outcome, priority and permitted trade-offs. When the task returns with questions, the founder may interpret a weak brief as a weak employee.
A good delegation agreement makes judgement possible. It explains what success looks like, what the owner can choose and when the issue should return for help.
Diagnose why delegated work returns
| What you see | What to check | Next move |
|---|---|---|
| “What exactly do you want?” | Was the outcome and completion standard explicit? | Rewrite the brief with an observable result. |
| “Can I approve this?” | Were spending, scope and commercial limits agreed? | Clarify authority and escalation conditions. |
| “Which of these comes first?” | Are priorities and available capacity realistic? | Resolve the trade-off rather than adding pressure. |
| “I could not get the information” | Does the owner have access and cooperation? | Remove the information or organisational barrier. |
Delegating a customer onboarding outcome
Hypothetical example · not a client case study
Imagine a founder asking an account lead to “manage onboarding.” The lead schedules calls but still returns to the founder for priorities, scope changes and acceptance. The task has been transferred, but the operating judgement has not.
A revised agreement defines readiness for delivery, the required customer inputs, permitted schedule changes and exceptions that need escalation. The account lead proposes a plan and owns the handoff. The founder reviews a sample of completed onboardings and the exception log rather than approving every email. Repeated escalations identify a missing rule or a coaching need for the next review.
- 01BriefOutcome and business context
- 02EquipAuthority, inputs and capacity
- 03ActOwner makes bounded decisions
- 04ReviewEvidence and learning
Write a delegation agreement people can use
1. Explain the purpose and completion
State why the work matters, the expected result and the evidence that will establish completion. Make dependencies and timing visible. Ask the owner to restate the brief; this checks shared understanding without turning the conversation into a memory test.
2. Agree freedom and guardrails
Specify which choices the owner can make and which conditions require help. Include access to people, information and a realistic amount of time. Do not transfer an outcome that depends on authority the receiving role does not have.
3. Review the judgement
Choose checkpoints based on novelty and risk. Discuss the owner’s reasoning and compare the result with the agreed standard. If the standard changes, say so explicitly. Repeatedly overriding ordinary choices without explanation trains the team to return them to you.
Put it to work
Delegation agreement worksheet
Work through the four prompts using evidence from your business. These notes stay in this page, are not sent or saved, and disappear when you reload. Copy them before leaving.
Specify the outcome
Define purpose, result, deadline and evidence of completion.
Set the boundary
Agree authority, constraints and escalation conditions.
Equip the owner
Confirm information, dependencies and available capacity.
Review the handoff
Record the owner’s reasoning, outcome and remaining ambiguity.
Choose your next step
Successful delegation leaves the owner better able to make the next decision. It does not simply move activity away from the founder for a few days.


