How to Delegate Effectively: A Manager's Playbook

Why is delegation so hard for managers?

Most managers were promoted because they were good at doing the work. Doing the work gives quick, visible satisfaction. Explaining context to someone else, waiting for the result and tolerating a slightly different approach gives slower and less certain rewards.

That imbalance is the root of most under-delegation.

A 2025 summary by MIT Sloan Executive Education of an article by Elsbeth Johnson in Harvard Business Review lists several causes. Completing a task yourself feels more rewarding than delegating it. Team members keep pulling leaders back in with questions.

Senior leaders sometimes ask for more detail than is needed. And leaders who rose through hands-on expertise, such as lawyers, surgeons, researchers and salespeople, may believe that real work means doing the task themselves. The same summary points to the costs: higher-paid managers end up doing lower-level work, micromanagement drains team productivity and growth, and managers have less time for strategy, people and development.

Gallup's research on founders gives a sense of how widespread the difficulty is. In a 2015 Gallup Business Journal article by Sangeeta Bharadwaj Badal and Bryant Ott, based on a survey of 1,446 U.S. employer entrepreneurs, only one in four had high Delegator talent, and about 75% had limited to low levels. The sample is entrepreneurs, not salaried managers, so do not read it as a statistic about managers in general.

It does show that letting go is a minority skill even among people who built companies.

What should you delegate, and what should you keep?

Start with Johnson's test, as summarized by MIT Sloan: ask whether you are the best and cheapest person to get this done. If someone else can do it well enough at lower cost, or can grow by doing it, it is a candidate for delegation. Good candidates are recurring tasks you have already figured out, work that sits in someone else's area of expertise, and projects that would stretch a person you want to develop.

Keep what only you can do. That usually means decisions with significant legal, financial or people consequences, confidential matters such as performance management and pay, conversations that set the team's direction and anything where your authority or relationships are the reason the work needs to happen. Also keep tasks where there is no time to explain and no tolerance for error, but only occasionally.

If every task falls into that category, the problem is how the team works, not the task.

Check the match as well. Gallup's 2015 article on entrepreneurs notes that delegation involves learning what each team member does best and assigning tasks accordingly. A task that fits a person's strengths will come back better than the same task given to whoever happens to be free.

How do you write a delegation brief?

Most failed delegation comes down to a vague handoff. The person did not know why the task mattered, what good looked like, what they could decide alone or when you wanted to see it. The MIT Sloan summary frames the manager's role as setting context (purpose, who to work with, expected results and deadlines) while the team decides how to do the work.

A written brief makes that context explicit and gives both of you something to refer back to.

Use the template below. It fits on one page and takes ten minutes to fill in. Share it in writing and then discuss it in a short conversation, so the person can ask questions and say what they think of the plan.

• The outcome: What needs to exist or be true when this is done? Describe the result, not the steps.
• Why it matters: How does this connect to the team's goals, a customer or a deadline outside your control?
• What good looks like: Quality standards, must-haves and what is explicitly out of scope. Include an example if you have one.
• Decision rights: What the person may decide alone, what they should check with you first and what you want to be told about afterward.
• Resources and people: Budget, tools, access, who to ask for help and who needs to be kept informed.
• Deadline and milestones: The final date, plus one or two earlier points where you will look at progress together.
• How you will stay in touch: The format and rhythm of check-ins, and how the person can reach you if they are stuck.
• What the person gets out of it: The skill they will build, the visibility they will have or the credit they will receive.

End the conversation by asking the person to say the task back to you in their own words. A two-minute summary shows you what they understood, and it is far cheaper than finding out at the deadline.

How much freedom should you give?

Not every task should be handed over in the same way. Think of a ladder with five levels. At the first, the person researches and reports, and you decide.

At the second, they recommend an action and you approve it. At the third, they decide and tell you before acting. At the fourth, they act and tell you afterward.

At the fifth, they act and you only hear about it if something unusual happens.

Pick the level for each task and each person, and say it out loud. Someone doing a task for the first time may start at level two, and the same person may be at level four on a task they have done five times. Seniority is a poor guide: a senior engineer new to budgeting needs more structure on budgets than a junior analyst who has done them for a year.

Move people up the ladder as they show they can handle it, and tell them that this is the plan so they know how to earn more autonomy.

Gallup's 2015 article on delegation points the same direction. Setting clear expectations for timing, budget and deliverables, tracking results rather than dictating every step and allowing people room to choose their own approaches are the practices it highlights.

How do you check in without micromanaging?

Micromanagement is usually a symptom of unclear delegation. If you do not know what is happening, you ask more often, and the person feels watched. The remedy is to agree on check-ins before the work starts.

A milestone date on the brief and a short written update at each one is usually enough. Ask for an early look at the approach, because it is easier to correct direction in the first 10% of a task than in the last 10%.

Questions from the team will keep pulling you back in unless you plan for them. The MIT Sloan summary suggests setting boundaries: restate the purpose of the task, hand the question back to the person, share relevant experience without solving the problem for them, and stay available. In practice that sounds like: what do you think the options are, and which would you pick?

You are coaching a decision, not giving it away.

Use your regular one-on-one meetings for this, with delegated work as a standing agenda item. A 2015 Gallup analysis found that employees whose managers hold regular meetings with them are almost three times as likely to be engaged, which supports the idea that regular contact is part of good management and should not be read as hovering. The difference between a check-in and micromanagement is whether the person set the agenda and whether you are asking about outcomes or about method.

What if the work comes back wrong?

Start by checking the brief. Was the outcome clear? Did the person have the information and access they needed?

Did they know what they could decide? In many cases the gap was in the handoff, and you can fix it by improving the brief next time. If the brief was good, ask what happened and listen.

The person may have hit an obstacle you did not know about, or they may have used a method you would not have chosen that still produced an acceptable result.

Decide what needs to change: the result, the method or only your preference. If the result is not acceptable, say so specifically, and agree what will be corrected and by when. If the method is different from yours but the result is fine, let it go.

Taking a task back, or quietly redoing it, teaches the person that delegation is conditional and teaches you that you cannot rely on the team. Do it only when the cost of the error is high and there is no time to coach.

Use the conversation to build skill. The guide on how to give feedback covers a script for the corrective conversation, and the guide on psychological safety at work explains why people need to feel able to report problems early. If people hide trouble because they fear your reaction, you will hear about it too late.

How do you delegate to people at different experience levels?

A new hire needs context and a safe first task. Give a task with a clear shape and a low cost of error, pair them with someone who can answer questions (an onboarding buddy program helps here) and check in more often at the start. As they succeed, widen the scope in steps they can see.

An experienced person needs the outcome, the boundaries and room. Over-explaining method to an expert feels insulting and wastes their time. Ask them what they need from you and then get out of the way, staying available for questions about priorities and trade-offs.

Someone stretching into a new area needs a sponsor. Make it explicit that this is a development assignment, say what you expect to be difficult and set aside time to talk about what they are learning. Gallup's 2015 article on manager behavior reports that managers who help employees grow through strengths are more than twice as likely to engage their team members, which is a good reason to match delegated stretch work to what someone already does well and wants to build on.

How do you delegate when your team is remote or hybrid?

In a distributed team, the brief matters even more because the person cannot lean over to ask what you meant. Write it down, put it in a shared space and agree on where progress will be reported. Because remote people lose the informal updates of an office, schedule the check-ins you would otherwise skip.

The guide on how to manage a hybrid team covers the wider rhythm.

Be careful about whom you pick. Managers tend to hand important work to the people they see most often. If your team is split across locations, review your delegations regularly to see whether stretch work is going to the same two or three people.

Spreading it is better for development and reduces your dependence on a small group.

For managers who find that their work is still overflowing, the question may not be skill but design: the number of people reporting to you, unclear priorities or a role that has too much in it. The guide on preventing team burnout covers workload checks that apply to you as much as to your team.

How do you build a delegating habit?

Start small and make it routine. Each Friday, list the tasks you did that week and mark those that someone else could have done. Pick one and write a brief for it on Monday.

The MIT Sloan summary recommends checklists for context-setting and routine check-ins as a way to build the habit, and the template above can serve as that checklist.

Tell your own manager what you are doing. The same summary notes that senior leaders can create pressure by asking for more detail than needed, so start by sharing small updates, focus on outcomes over process and bring team members into relevant meetings so that the person who owns the work can speak for it.

Review once a quarter. Which tasks did you hand over, which came back well, and which are still on your plate for no good reason? Use that review to decide what to delegate next and who could use a stretch.

If you want a way to capture goals and development plans across the team, a performance management platform can help, and a learning management system can support the training behind new responsibilities. The tool is secondary. What counts is that the brief, the check-in and the follow-up conversation happen every time.

Frequently asked questions

What is the difference between delegating and assigning a task?

Assigning tells someone to do a step. Delegating hands over an outcome along with the context and authority to reach it, and the person decides how. You remain accountable for the result.

If you specify every step and approve every decision, you have assigned a task and kept the ownership, which is why it often feels like micromanagement.

What tasks should a manager never delegate?

Keep decisions with major legal, financial or people consequences, confidential matters such as pay and performance management, and conversations that set the team's direction. Everything else is worth considering. A useful test from a 2025 Harvard Business Review article, as summarized by MIT Sloan, is whether you are the best and cheapest person to get the task done.

How do I delegate without losing control of quality?

Define what good looks like in the brief, agree on one or two milestones where you review progress and ask for an early look at the approach. Track results instead of dictating steps. Quality problems are usually caught cheaply at an early milestone, and rarely by inspecting every detail of the work.

How do I stop team members from asking me everything?

Restate the purpose of the task, hand the question back by asking what options they see and which they would choose, share relevant experience without solving the problem for them, and stay available. Set decision rights in the brief so the person knows what they can settle alone. Over time the questions shift from how to what trade-offs.

What should I do when someone fails at a delegated task?

Check the handoff first: was the outcome clear, did the person have access and information, and did they know what they could decide? Then talk about what happened, agree on a fix and capture what to change in the brief or the support. Taking the task back should be rare, because it teaches people that delegation is conditional.

How often should I check in on delegated work?

Agree on this before the work starts. For a new task or a new person, a check-in at the end of the first stage and a milestone in the middle is a good start. For experienced people on familiar work, a brief written update at one or two milestones is enough.

Use your regular one-on-ones for conversation about the work.

Sources and further reading

• The Delegation Dilemma: Why Leaders Struggle to Let Go (September 2025, summarizing Elsbeth Johnson in Harvard Business Review), MIT Sloan Executive Education
• Delegating: A Huge Management Challenge for Entrepreneurs (Badal and Ott, April 2015), Gallup Business Journal
• Employees Want a Lot More from Their Managers (2015), Gallup