Delegation
Most delegation fails before anyone does any work. The task is handed over without a definition of the result, without authority to make decisions, and without a review point. This hub is about making handovers precise enough that the work stops coming back.
Reviewed by a qualified professional
James Whitfield — FCCA, Chartered Certified Accountant — 18 years advising UK SMEs on employment costs, payroll and business finance. Reviewed 5 August 2026.
Last updated 2 August 2026
Where are you stuck?
Overview
Why handovers fail before the work starts
Delegation rarely fails because of a skills gap. It fails at the moment of handover, when the task is described but the outcome, the authority and the review point are not. The person receiving the work is left guessing what 'good' looks like, so they either under-deliver or check in constantly.
This means most delegation problems are fixable with a better brief, not a better hire. Before assuming someone cannot do the work, check whether they were actually given enough to succeed: a clear outcome, boundaries and permission to make ordinary decisions.
Treat the first few handovers to any person as a test of your own clarity, not just their competence. If work keeps returning to you, read the brief again before you draw conclusions about the person.
The order to work through it
Start by sorting your own workload by frequency and risk: frequent, low-risk tasks are the easiest and safest things to hand over first, because mistakes are cheap and you get many repetitions to refine the brief.
Next, write outcome definitions before you write instructions. Describing the destination, in the language you would use to check the work, prevents the trap of writing a rigid step-by-step process for something that needs judgement.
Only after outcomes are clear should you set authority: what the person can decide alone, what they should decide and then tell you, and what must come to you first. Skipping straight to authority without a defined outcome tends to produce vague permission that nobody actually uses.
Common failure modes
In Kayley's experience, the most common failure is delegating a task while quietly keeping the decision rights, so everything still funnels back for approval. This is not delegation, it is instruction with extra steps, and it exhausts both people.
A second failure is rewriting the finished work to match how you would have done it, rather than checking it against the outcome you defined. If you did not write down what 'good enough' meant, you cannot fairly judge the result — you can only compare it to your own style.
A third is treating every handover as permanent and total from day one. Early handovers usually need a shorter leash and a closer review point, loosening only once a pattern of reliable delivery is visible.
What to write down
A one-page delegation brief is enough for almost any task: the outcome, any hard constraints (budget, deadline, tone, legal requirements), the decisions the person owns outright, the decisions that need a heads-up, and a fixed date to review the result together.
Keep this document short enough to read in under a minute. A long document signals uncertainty about what actually matters and invites the reader to focus on the wrong details.
Reuse the same structure for every handover so the person learns the pattern, not just the content. Consistency in how you delegate is often more valuable than the perfection of any single brief.
What "done" looks like
Delegation is working when a reasonable decision gets made on an ordinary Tuesday afternoon without a message to you, and when the review point is a scheduled conversation rather than an anxious check-in triggered by silence.
You should be able to point to a written outcome and a written authority boundary for anything that has been meaningfully handed over. If you cannot, the task has probably been assigned rather than delegated.
When something does go wrong, you should be able to diagnose whether the brief, the authority, the person's capability, or the fit of the task was at fault — rather than defaulting to 'they're not good enough' as the only explanation.
The five-minute action
Subtopic map
What this hub covers
What to delegate
Sorting work by frequency, risk, judgement required and how easily it can be described.
What Should a Founder Delegate First? (9 min read)Defining outcomes
Writing down what a good result looks like, in the words you would use when checking it.
How to Write Outcome Definitions Before You Delegate (9 min read)Authority and decision rights
What they can decide alone, decide and tell you, or must ask about first.
Setting Authority and Decision Rights When You Delegate (10 min read)Delegation briefs
A one-page handover: outcome, constraints, budget, deadline, authority, review point.
How to Write a Delegation Brief That Actually Works (10 min read)Review and feedback
Scheduled checkpoints instead of anxious interruptions.
How to Run a Review Point That Improves Delegated Work (9 min read)Micromanagement
Why it appears, what it costs, and how to replace it with visibility.
How to Delegate Without Micromanaging (11 min read)Failed delegation
Diagnosing whether the brief, the authority, the capability or the fit was wrong.
Why Delegation Fails and How to Diagnose It (10 min read)Subtopic map
Guides in this hub
Each guide answers one question in full and ends with something you can write down today.
What Should a Founder Delegate First?
Delegate first the tasks that are frequent, well defined, and low-risk if done imperfectly, such as routine admin, scheduling and repeatable process work, before moving on to judge…
Read (9 min read)How to Delegate Without Micromanaging
You stop micromanaging by changing what you hand over, not by forcing yourself to interfere less. Give people a written brief with a clear outcome, a stated level of authority to a…
Read (11 min read)How to Write Outcome Definitions Before You Delegate
Write the outcome as the end state you're paying for, not the steps to get there: a sentence describing what a good result looks like, specific enough that someone else could check…
Read (9 min read)Setting Authority and Decision Rights When You Delegate
For every task you delegate, decide explicitly what the person can decide alone, what they can decide and simply tell you about afterwards, and what they must check with you before…
Read (10 min read)How to Write a Delegation Brief That Actually Works
A working delegation brief fits on one page and answers five questions: what does 'done' look like, what constraints apply, what can they decide without asking, when is it due, and…
Read (10 min read)How to Run a Review Point That Improves Delegated Work
A good review point is a scheduled, agreed-in-advance conversation about a piece of delegated work, structured around what worked, what needs adjusting, and what happens next — not…
Read (9 min read)Why Delegation Fails and How to Diagnose It
When delegated work goes wrong, work back through the handover before concluding it's a problem with the person: check whether the outcome was clearly defined, whether the authorit…
Read (10 min read)Featured tool
What Should I Delegate? Tool
List the work that fills your week, rate each item, and get a ranked delegation order with a suggested handover route for each task.
Use the What Should I Delegate? ToolTemplate
One-page Delegation Brief template
Outcome, definition of done, constraints, budget authority, decision rights, deadline, review point and escalation route.
Use the template online or print a copy for your team. No email address is required.
Founder stories
Delegation stories are the most useful thing founders can share. If you have a handover that went wrong and what you changed, send it in.
Contribute your storyFrequently asked questions
What should I delegate first?
Work that happens often, has a low cost of error, and can be described in a checklist. That combination gives fast relief and safe practice at handing over.
How much authority should I give?
Enough to complete the job without asking you, and no more than the role needs. Set a spend threshold, a list of decisions they own, and a short list of decisions that must come to you.
Is delegation the same as abdication?
No. Delegation keeps accountability with you and moves execution and defined decisions to someone else, with a review point. Abdication is handing something over and finding out how it went by accident.