Managers avoid delegating less out of laziness than out of exposure: handing over a task hands over control of a result they still answer for. Research on delegation practice points somewhere less comfortable — what shapes the outcome is how well the person handing over understands the receiving person’s role and scope.
Quick Overview
What you’ll learn:
- What really blocks a handover when the manager already knows it should happen
- Why delegation behaves as a level rather than as an on-off state
- How to match that level to task maturity instead of to seniority
- What decides whether a delegated task reports back in time
Who this article is for:
- Line managers working above their own capacity
- Specialists moving into a managerial role for whom delegation is new
- Anyone running leadership development inside an organisation
Reading time: 7 minutes
The Blocker Is Not Trust, It Is an Undefined Scope
Ask a manager why a task has not moved and the answer is usually “it is faster if I do it myself”. That answer is true about the single task and misleading about the queue behind it. The real blocker shows up only when the question gets specific: what exactly is the person receiving this task allowed to decide, and where does their mandate stop?
The integrative review of delegation practice indexed on pubmed.ncbi.nlm.nih.gov lands in the same place. It describes delegation as a complex but critical leadership skill, and reports that its effectiveness is shaped by whether the delegating professional understands the receiving person’s role, scope of practice and job description. The same review notes that newly qualified staff lacked the leadership skills needed to delegate, and that education on delegation is required both before entering the role and during a career.
For a line manager the usable conclusion is unglamorous. Delegation does not start with a motivational conversation; it starts with checking whether the scope on the other side is written down anywhere. Where it is not, every handover is negotiated from zero — which is exactly why it feels cheaper to keep the task.
Delegation Is a Level, Not a Switch
The conversation goes wrong the moment a task is sorted into “mine” and “theirs”. Handovers happen in stages: execution in an agreed way, then the choice of method, then the right to settle between options, and finally accountability for a whole area with the result reported after the fact. Those are levels of delegation, and they differ in a single property — what comes back to the manager, and when.
Naming the level resolves two routine misunderstandings at once. In the first, the manager believes a decision was handed over while the employee believes only the execution was, so they arrive asking for an approval nobody planned to give. The second runs the other way: the employee settles the matter, the manager hears about it too late and reads it as a bypass, even though no checkpoint was ever reserved.
Write the level down where the task is written down, together with the name of the task owner — the person accountable for getting it finished and for flagging when it cannot be. An agreement made in a corridor lasts exactly as long as both memories agree, and after the first difficult case they stop agreeing.
Match the Level to Task Maturity, Not to Seniority
Situational leadership holds that the leadership style is selected against a person’s maturity in a specific task rather than against their tenure or their relationship with the manager. The scoping review of that theory in nursing management, available on pubmed.ncbi.nlm.nih.gov, describes it as a follower-centred skill: the leader adapts style to the follower’s maturity in order to support organisational goals and the follower’s own satisfaction and growth. The same review is careful — it flags low transparency in how the underlying studies were reported and a need for further validation of the measurement instruments, so treating the model as a finished recipe would misrepresent the source.
Task maturity is a property of a pairing, not of a person. An experienced administrator can be mature in keeping a system running and immature in negotiating contract terms with a supplier. A manager who matches the delegation level to the person rather than to the task gets it wrong in both directions: overloading where context is missing, and micromanaging where the competence is already higher than their own.
The practical consequence is a review cadence. Revisit the delegation level when the task changes, not at the annual appraisal, because a change of task is the moment task maturity actually moves.
Psychological Safety Decides Whether a Handover Reports Back
A delegated task is only as safe as the team’s willingness to say “this will not land in time”. That willingness has a name in the research literature — psychological safety — and it has been studied as a property of teams and organisations, not only of individuals. The systematic review of its enablers indexed on pubmed.ncbi.nlm.nih.gov synthesises enablers across organisational, team and individual levels, and groups them under themes: priority for patient safety, improvement or learning orientation, support, familiarity with colleagues, status, hierarchy and inclusiveness, and individual differences.
The themes that bear most directly on a manager handing work over are familiarity with colleagues, and status and hierarchy. Familiarity argues for keeping a handover inside a stable working pair rather than routing it through whoever happens to be free. Status and hierarchy argues for saying out loud that escalating early is part of the mandate — because where it is not said, the hierarchy fills the silence with its own interpretation.
The review itself frames this list as a first step towards observational measures and interventions, not as a validated programme. Read that way, it is still the most useful part for delegation: it names what to arrange around the handover so a problem surfaces while a manager can still act on it.
Read Also
- The art of delegation: levels of delegation and a checklist — a working checklist for the handover conversation
- The leadership paradox: delegation, micromanagement and overtrusting — both extremes of the same decision
- Difficult conversations with employees: how to handle them — how to hold the conversation in which someone admits the deadline is slipping
Build Your Skills
This topic is developed in the Production Leader Academy and Active Leadership for IT Professionals courses. The first works on the craft of leading an operational team; the second on leadership inside a technical one. Contact us to match the scope to your area of accountability.
Frequently Asked Questions (FAQ)
Why do managers avoid delegating tasks?
Because they give up control of a result they still answer for, while the scope the receiving person may act inside is not described anywhere. The integrative review on pubmed.ncbi.nlm.nih.gov ties delegation effectiveness to understanding the other side’s role, scope of practice and job description — something that can be prepared in advance, rather than a trait of the manager.
How do you delegate without losing control of the outcome?
By naming the delegation level and a checkpoint, instead of supervising the work in progress. The level says what the person settles alone and what comes back; the checkpoint says when it comes back. Control moves from the running work to the outcome and the mandate boundary, where it stays with the manager without blocking anyone.
How is situational leadership different from having a leadership style?
A leadership style describes how a manager runs a team in general. Situational leadership assumes the style is selected against a person’s maturity in a specific task, so the same manager uses different styles with the same person across different tasks. The scoping review on pubmed.ncbi.nlm.nih.gov frames it as a follower-centred approach, with the caveat that the measurement instruments used in studies of the theory still need validation.
What should never be delegated?
Accountability for appraising people, for splitting work between team members, and for settling a dispute in which the manager is a party. Those can be consulted on, but handing them over transfers a conflict to someone without the mandate to resolve it. Most other work can be handed over at some level of delegation — the open question is the level, not the permission.