Delegation
Why Delegation Fails and How to Diagnose It
10 min read · Published 3 August 2026 · Last reviewed 11 August 2026 · Written by Kayley Hart
The short answer
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 authority level matched the task, and whether the review point came soon enough to catch drift early. Most failed delegations trace back to one of these three. Only after a fair, well-briefed attempt still falls short should you treat it as a genuine skills or fit issue.
Guide action map
Illustrative frameworkWhy Delegation Fails and How to Diagnose It
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.
Author: Kayley Hart
Editorial policy & fact-checking apply.
What you will take away
- • Most failed delegations are brief failures, not people failures — check the handover before judging the person.
- • Ask what decision the person got stuck on; their answer usually points straight to the gap in the brief.
- • A pattern across multiple failed handovers to different people points to a systemic brief or process issue, not individual underperformance.
- • Genuine performance or fit issues should be addressed through a proper, documented process, not folded quietly back into your own workload.
- • Redoing someone's work yourself after a failed attempt teaches them nothing and guarantees you'll be doing it again next time.
- • Treat an early failure as a diagnostic, not a verdict — one bad attempt with a decent brief is rarely conclusive either way.
Resist the instinct to blame the person first
When delegated work comes back wrong, late, or not at all, the instinctive conclusion is often that the person wasn't up to the task. In a small business, this conclusion is usually wrong, or at least premature. Far more often, the failure traces back to the handover itself — an unclear outcome, an authority level that didn't match the task, or a review point that came too late to catch a small misunderstanding before it became a larger one.
This isn't about letting people off the hook for genuine underperformance, which does happen and needs addressing properly when it does. It's about being honest with yourself, first, that the handover might be where the failure actually started, because concluding too quickly that someone 'isn't capable' both damages the relationship unfairly and stops you from fixing the actual, more common cause, which will simply repeat with the next person you delegate to.
The three-question diagnostic
Before drawing any conclusion about the person, work back through three questions in order. First, was the outcome actually clear — could the person have described, in their own words before they started, what 'done well' looked like? Second, was the authority level realistic for their experience with the task — were they left guessing about decisions nobody had actually cleared them to make? Third, was the review point close enough together, particularly for someone new to the task, to catch a small misunderstanding while it was still small and cheap to correct?
A genuinely useful shortcut is to ask the person directly what decision they got stuck on, or where they felt unsure. If the answer is 'I didn't know whether I was allowed to do that', that's an authority gap — the fix is a clearer, more specific authority statement next time, not a conclusion about their judgement. If the answer is 'I wasn't sure what you actually wanted', that's a definition-of-done gap, and the fix lives in the brief, not the person.
- Was the outcome clearly and specifically defined before the work started?
- Was the authority level matched to the task and the person's experience with it?
- Was the review point set close enough together to catch drift while it was still small?
Reading the pattern across multiple people
If a task fails when handed to one particular person but succeeds smoothly with someone else, that points more towards an individual fit or skills issue with that task specifically. But if the same task has now failed with two or three different people in a row, despite genuinely different individuals, that's a strong signal the problem sits in the brief, the process, or the way the task itself has been described — not in the people you've delegated it to.
This distinction matters because it changes what you fix. A fit issue with one person is addressed through coaching, a different task assignment, or, if it persists, a formal performance conversation. A systemic brief issue is addressed by rewriting the outcome definition, the constraints, or the authority statement — and it will keep producing failures with every future person until that underlying document is fixed.
When it genuinely is a skills or fit issue
If you've worked back through the brief, the authority level and the review cadence, corrected anything that was genuinely unclear, given the person a fair further attempt with the improved version, and the standard is still not being met, you're now looking at a genuine performance issue rather than a handover problem. At this point it needs handling as a formal, documented process, not an informal, ongoing frustration that gets absorbed by you quietly redoing the work yourself.
Acas guidance on managing performance sets out a fair process for this: a clear, specific conversation about what isn't meeting the standard, a written record of what was discussed and agreed, a reasonable, time-limited opportunity to improve with support, and only then, if there's still no improvement, consideration of more formal steps. Skipping straight to a difficult conversation without that documented, fair process behind it creates unnecessary risk, particularly for an employee with two or more years' service where protection against unfair dismissal applies.
This part of the process carries genuine legal risk if handled informally or inconsistently, so where a performance issue looks likely to continue beyond a first informal conversation, it's worth getting specific advice — from Acas, an HR adviser, or an employment solicitor — before taking any formal step.
A single failed attempt, even a bad one, is rarely enough evidence on its own to conclude it's a fit issue. Work through the brief first — most 'they're not capable' conclusions turn out to be 'the brief wasn't clear' on closer inspection.
The trap of redoing the work yourself
A very common response to a failed delegation is to quietly redo the work yourself, either because it's faster in the moment or because you don't want to have an awkward conversation about what went wrong. This feels like the path of least resistance, but it guarantees the same failure will repeat, because the person never learns what needed to change, and you never find out whether the problem was the brief or genuinely their approach.
If work comes back short of the standard, the more useful response — even though it takes longer in the moment — is to sit down with the person, go through the outcome definition together, identify specifically where it fell short, and have them redo the relevant part themselves with that feedback. This is slower the first time and considerably faster every time after that, because it actually builds the capability you were trying to create by delegating in the first place.
Rebuilding after a failed handover
Once you've identified what actually went wrong, the next handover of the same task should visibly reflect the fix — a sharper outcome definition, a more specific authority statement, an earlier or more frequent review point, whichever applied. Say this explicitly to the person: 'last time the brief didn't say clearly enough what to do if a customer asked for X, so I've added that this time' — this signals that the fault genuinely wasn't laid at their door and rebuilds confidence on both sides for the next attempt.
Where the failure was a genuine skills gap rather than a brief issue, consider whether the person needs a smaller version of the task first, or some direct coaching alongside a first attempt, rather than jumping straight back to the full, unsupported handover that failed the first time. Rebuilding confidence, both yours and theirs, usually works better in smaller, successful steps than in one high-stakes second attempt.
Do it now, with a tool
Delegation Ladder Builder
Sets the authority level for each task, from 'do exactly this' to 'decide and act, tell me quarterly'.
Open the tool (4 minutes)Delegation Brief Generator
Produces a one-page brief: outcome, definition of done, constraints, budget authority, deadline and review point.
Open the tool (5 minutes)Founder Bottleneck Assessment
Finds where the business queues behind you across decisions, money, knowledge, customer relationships, systems and absence — and what to move first.
Open the tool (4 minutes)Frequently asked questions
How do I tell the difference between a brief problem and a genuine skills gap?
Ask the person what decision they got stuck on, or where they felt unsure. A specific answer pointing to a missing authority limit or an unclear outcome is a brief problem. A general struggle with the underlying task itself, even with a clear brief and reasonable authority, points more towards a skills or fit issue that needs a different kind of support.
How many failed attempts should I allow before treating it as a performance issue?
There's no fixed number, but a reasonable approach is: first attempt, diagnose and fix the brief if there's any doubt; second attempt with the corrected brief, watch closely; if the same standard still isn't met with a genuinely clear brief and appropriate authority, that's usually enough to move towards a formal performance conversation, following Acas guidance on process and fairness.
What if I can't tell whether it was the brief or the person?
When genuinely unclear, treat it as the brief's fault one more time and give a clearly improved version a fair run. This costs relatively little if the brief really was the issue, and it protects you from the greater cost, both human and legal, of treating a fixable handover problem as a performance issue prematurely.
Is it fair to move a task back to myself after a failed delegation?
Temporarily, yes, particularly for something time-sensitive, but treat it as a pause rather than a permanent retreat. Diagnose what went wrong, fix the brief or authority level, and try delegating it again once you've addressed the actual cause — permanently pulling every failed task back to yourself just recreates the bottleneck delegation was meant to solve.
Does a failed delegation need to go in someone's formal record?
Not usually, if it's clearly a one-off brief issue that's been fixed and hasn't recurred. If it forms part of a pattern that's moving towards a formal performance conversation, it's worth keeping a brief, factual note of what happened and what was agreed at the time, since a clear written record matters if the situation continues and needs to be addressed formally later.
Continue from here
Choose the related decision that comes next for your team.
- Continue with How to Delegate Without Micromanaging
- Continue with How to Run a Review Point That Improves Delegated Work
- Continue with How to Write a Delegation Brief That Actually Works
- Continue with How to Manage People When You Have Never Been a Manager
Sources & Citation
Cite this guide
Hart, K. (2026) "Why Delegation Fails and How to Diagnose It". The Small Team Builder. Available at: https://www.kayleyhart.co.uk/guides/why-delegation-fails-and-how-to-diagnose-it
Rates, thresholds and rules change. Confirm anything financial or legal on the source before you act on it.
