How to Delegate Tasks Effectively as a New Manager

Why is delegating so hard for new managers?

Most new managers were promoted because they were good at the work. The habits that earned the promotion, finishing things quickly and to a high standard, are the habits that now get in the way. Explaining a task takes forty minutes and doing it takes twenty, so you do it. Next week the same twenty minutes is back.

The stakes are higher than a long Thursday. Gallup's State of the American Manager research estimates that managers account for at least 70% of the variance in team engagement scores. In a separate Gallup study of 143 chief executives from the 2014 Inc. 500 list, those with high delegation talent led companies with 33% greater revenue than those with less. Neither figure promises anything for an individual team, but both point the same way: handing work over well is close to the centre of the manager's job.

It helps to separate two words. Responsibility for doing the work moves to the other person. Accountability for the outcome stays with you. That is not a reason to keep the task. It is the reason to brief well and to check at the right moments.

What should a manager delegate, and what should they keep?

Write down every recurring task you did last week and how long each took. Then ask two questions of each one. Does it need me, specifically: my authority, my relationships or my judgement? And what is it worth: would anyone important notice if it were done well, or if it stopped?

Julian Birkinshaw and Jordan Cohen described a similar exercise in Harvard Business Review in 2013 and reported that knowledge workers could free up as much as 20% of their working day by dropping, delegating or redesigning low-value tasks. Your own figure will differ. It is rarely nothing.

• Keep: decisions about anyone's pay, performance or job, confidential matters, and anything where you are the named accountable person.
• Hand over: recurring reports, routine approvals inside a clear rule, meeting preparation, first drafts, supplier comparisons, and much of what you simply enjoy from your old job.
• A useful rule of thumb: if someone could do it about 70% as well as you today, delegate it and coach the gap.

How do you choose the right person for a task?

The default rule on most teams is to give it to whoever is most reliable. That overloads your best person and starves everyone else of interesting work. Use four tests, each judged for this particular task.

Skill: can they do it now, with help, or not yet? Will: do they want it and feel able? Development value: would it stretch them toward where they want to go? Capacity: do they have the hours? The pairing of skill and will is a long-standing coaching idea, close to the situational leadership thinking of Paul Hersey and Ken Blanchard: someone with high will and low skill needs teaching and early checks, while someone with high skill and low will needs a conversation about why.

Then make it an offer, not an announcement. Say why you chose them, what they gain and what comes off their plate. Jobulary's explainer on the 70-20-10 model is a helpful reminder that most professional learning comes from real work with support, which is what a well-matched delegation is.

How much authority should you give?

Many delegation failures are disagreements about authority that nobody voiced. One person pays a deposit when the manager wanted a shortlist. Another asks permission for every email. Agree a level along with the task. Five levels in plain words cover most situations.

• The level belongs to the task, not the person.
• Choose it from three things: how reversible a mistake is, how experienced the person is with this task, and what company rules allow.
• Add one guardrail sentence: 'Level 4, unless it costs more than the agreed limit.'
• Move the level up as good results come in.

What goes into a good delegation brief?

Jesse Sostrin, writing in Harvard Business Review, argues that delegating well begins with being clear about why the work matters and what you expect. A six-part brief makes that concrete. It takes about ten minutes to write and fits on a page.

• Outcome: what will exist or be true when it is finished, and for whom.
• Context: why it matters, what it connects to, who cares.
• Constraints: deadline, budget, tools, rules, and what is not included.
• Authority: the level and the guardrail.
• Check-ins: when you will look, and at what.
• Done means: three to five points you could both tick.

What does a delegation brief look like in practice?

Take an illustrative example. Ahmed, a facilities manager, asks a team member to 'put together something on the cleaning contract renewal'. She spends nine hours on a twelve-page comparison of four suppliers. He wanted one page on two suppliers for a ten-minute slot with his director. Nobody was careless. The brief lived in his head.

Written in six parts, the same request reads like this. Outcome: a one-page recommendation to renew or switch, with cost and risk for each option. Context: the contract ends in ten weeks, the director has ten minutes on Thursday, and there were two complaints about weekend cover. Constraints: draft by Wednesday noon, use existing quotes, do not contact the current supplier yet. Authority: level 2, recommend. Check-ins: fifteen minutes on Tuesday, on the outline only. Done means: one page, both options costed for twelve months, weekend cover addressed, a clear recommendation.

After you have talked it through, do not ask 'is that clear?', because everyone says yes. Ask for a playback: 'What will you do first, and how will we both know it's finished?' If you cannot fill in 'done means' yourself, you are not ready to delegate the task. Delegate finding out first. If you would like the form ready-made, the Delegation Brief in Bodhih's Delegation and Workload Planner kit sets out the six parts on one fillable page.

How do you follow up without micromanaging?

Micromanaging is not the same as checking. It is checking at random, on the method instead of the result, without having agreed it. The opposite fault, disappearing until the deadline, does as much damage. One rule fixes both: set the rhythm from the risk of the task and agree it in the brief.

Score the impact of a miss from 1 to 3 and how new the task is to this person from 1 to 3, then multiply. A score of 1 or 2 needs a look at the end. A score of 3 or 4 needs an early look, a midpoint and the end. A score of 6 to 9 needs an early look within the first tenth of the time, then weekly or twice weekly. That early look at the first slice of real work is the cheapest check there is.

Run each check-in on four questions: what is done, what is next, what is in the way, and what do you need from me? And watch for tasks coming back. William Oncken and Donald Wass described the pattern in a much-reprinted Harvard Business Review article: a team member raises a problem, the manager says 'leave it with me', and the next move now sits with the manager. Help, but ask for their options and their pick first, so the task stays theirs.

What should you do when the work comes back?

Review it against the brief, not against how you would have done it. Ask the owner first what they are pleased with and what they would change. Then give one thing to keep and one to change. The Situation-Behavior-Impact model from the Center for Creative Leadership is a simple shape for both: name the situation, describe what the person did, say what effect it had.

If it fell short, sort the cause before you react: the brief, skill, capacity or will. Look at the brief first, and remember that only the last is about attitude. Let the owner make the fixes, and tell them the level for next time.

How do you delegate without overloading your team?

Delegation without a view of capacity moves the overload from your desk to someone else's. In the CIPD's 2019 Health and Well-being at Work survey with Simplyhealth, heavy workloads were the most commonly cited cause of stress-related absence, named by 62% of the UK organisations that responded.

Plan in plannable hours: contracted hours less the share that goes on meetings, email and admin, often around a fifth. Add up what each person is already committed to for the week, divide by their available hours, and keep the result under a ceiling below 100%, because there is always a surprise. When someone is over, there are five honest moves: drop, defer, shrink, move the work, or add capacity. Put new requests through a simple log, and for every yes, write down what gives way.

The same view shows single points of failure. List the team's critical tasks, count how many people can do each alone, and cross-train wherever the answer is one. Working time and leave rules differ by country and employer, so check your HR team and company policy before changing anyone's hours.