Delegation for managers means handing a task, along with the authority to finish it, to someone else on the team while the manager stays accountable for the result. Done well, it frees time and builds skills.
The wider question of how senior support roles absorb this kind of work is covered in the guide to the chief of staff role.
Why managers find it hard to let go
Most managers were promoted because they were good at doing the work. That history makes handing work over feel risky. Ohio State’s fact sheet on delegation lists the usual reasons: it seems faster to do things personally, someone else may not meet the manager’s standards, and the task can feel beneath the person receiving it. The same fact sheet argues that these barriers come from a misunderstanding of the job, because management is about getting things done with and through people rather than being the best technician on the team.
The University of Sussex learning and development team names a similar set of worries for new managers: low confidence in directing others, a belief that explaining a task takes longer than doing it, and guilt about adding to someone else’s list. Its effective delegation guide also warns that trying to accomplish or micromanage too many tasks may lead to burnout, poor quality of work or missed deadlines.
Understanding these habits matters because they decide what gets delegated. A manager who holds on to everything ends up with little time for planning, coaching and review, which is the work only a manager can do.
What to hand off and what to keep
A simple filter is to sort tasks by urgency and importance, the same approach used in the Eisenhower matrix. The Ohio State fact sheet applies it to delegation in four moves:
- Urgent and important: the manager usually handles these directly, such as crises and looming deadlines.
- Important but not urgent: strategic planning, relationship building and developing new systems. The fact sheet calls these ideal for delegation because they promote long-term growth and give people room to develop.
- Urgent but not important: routine emails, logistics and standard approvals, which can often be delegated or automated.
- Neither urgent nor important: candidates for elimination rather than delegation.
The Sussex guide adds a skills check. If a task is high in importance and urgency and nobody on the team has the skills for it, the guide says not to delegate. If a skilled person is available, it may be safe to delegate the task, but the manager should monitor the work. Tasks of low importance and urgency are described as ideal for a skilled and willing team member, and when the right skills are missing the manager can still delegate but needs to monitor.
In practice, this suggests a few categories that are commonly worth handing off: recurring reporting, scheduling and logistics, first drafts, research, and well-bounded projects with a clear finish line. Work that depends on confidential personnel matters, final accountability to senior leaders, or judgment calls that only the manager has the context for usually stays put.
How to hand it off: a step-by-step brief
The Sussex guide breaks delegation into a sequence that works as a checklist for any hand-off. Condensed, it runs as follows.
- Define the task. Confirm in your own mind that it is suitable to delegate.
- Choose the person. Consider what they will get out of it and what you will get out of it.
- Check ability and training needs. The guide asks whether the person or team is capable of doing the task and whether they understand what needs to be done.
- Explain the reasons. The guide says you must explain why the job or responsibility is being delegated, and why to that person.
- State the required results. Clarify understanding by getting feedback from the other person, and say how success will be measured.
- Agree resources, deadlines and feedback. Settle what is needed, when it is due, and how often you will check in.
- Support and communicate. Tell anyone else who needs to know what is going on.
- Give feedback on results. Review what went well and what did not.
Ohio State’s guidance frames the same idea more briefly. A manager should communicate expectations clearly but resist the urge to dictate how the work gets done, and should spell out the objective, what success looks like, and the constraints such as budget, deadlines and resources. Specifying the outcome while leaving the method open is often what separates delegation from simply passing along instructions.
Matching the person and the level of freedom
Picking the right person is not the same as picking the most reliable one. The Ohio State fact sheet notes that good managers distribute opportunities broadly to keep the whole team engaged, and that some will give stretch assignments to up-and-coming employees while coaching them through the task.
The fact sheet also describes situational leadership theory, developed by Hersey and Blanchard, which holds that effective delegation depends on matching the amount of direction and support to an employee’s readiness. Its four styles are directing, coaching, supporting and delegating. A person new to a task needs clear, closely monitored instructions. As they gain confidence, the manager moves to coaching and supporting. Once an employee is competent and committed, the manager can move into the delegating style, offering minimal guidance and full autonomy.
The practical lesson is that a single task can be handed over at different levels of freedom. A manager might ask for a recommendation first, then for a decision with a report afterward, and eventually for full ownership with only exceptions escalated.
Staying in the loop without micromanaging
Handing work over does not end the manager’s responsibility. The Sussex guide states plainly that the outcome of delegation is still your responsibility, so the manager needs to provide the right level of support for the task. It also says the manager must absorb the consequences of failure and pass on the credit for success.
Checkpoints are the usual way to balance trust and oversight. Agreeing review dates up front, rather than hovering, keeps the hand-off from feeling like surveillance. A short written project status update on a fixed rhythm is one lightweight way to see progress without interrupting the person doing the work. For teams spread across locations, remote team meetings and written check-ins can serve the same purpose when the manager and the delegate rarely overlap in the same hours.
Ohio State’s fact sheet also recommends supporting delegated work with documentation. It describes process maps that show the steps, decisions and flow of a task, which help employees see how their work connects to wider team goals. A short written description of how a recurring task is done gives the next person a head start and reduces the number of questions that come back to the manager.
Common mistakes to avoid
- Delegating the chore but not the authority. If the person must ask permission at every step, the manager has only added a middleman.
- Vague outcomes. Without a stated result and a deadline, both sides guess. The brief above exists to remove that guessing.
- Always choosing the same person. Reliable people become overloaded while others never get to grow.
- Taking the work back at the first stumble. A mistake is better handled with feedback, as the Sussex guide suggests, than by quietly redoing the task.
- Skipping the explanation of why. People handle a task better when they know where it fits in the bigger picture.
Sussex also lists benefits that follow when delegation works: it frees the manager’s time for planning and organising, helps the manager learn how to develop employees, and shows team members that they are trusted.
Frequently asked questions
What is the difference between delegating and assigning?
What is the difference between delegating and assigning?
What is the difference between delegating and assigning?
Show answer
Assigning gives someone a task. Delegating also passes along the decisions and context needed to finish it, with the expected result agreed in advance. The manager remains accountable either way, as the Sussex guide notes.
Which tasks should a manager never delegate?
Which tasks should a manager never delegate?
Which tasks should a manager never delegate?
Show answer
Guidance from Ohio State suggests the manager handles urgent and important matters directly, such as crises. Sussex adds that high-stakes work should not be delegated when the team lacks the skills for it. Confidential personnel matters are another common exception in practice.
How much should a manager check in after delegating?
How much should a manager check in after delegating?
How much should a manager check in after delegating?
Show answer
It depends on the person’s readiness. Newer team members need closer direction, while experienced and committed ones can work with minimal guidance. Agree review dates in the original brief so check-ins are expected rather than a sign of distrust.
Can routine work be delegated to software?
Can routine work be delegated to software?
Can routine work be delegated to software?
Show answer
The Ohio State fact sheet says it is worth investigating whether urgent but unimportant tasks, such as routine emails and logistics, can be delegated to an artificial intelligence agent. Anything handed to a tool still needs a person responsible for checking the output.
