New Manager Doing All the Work Yourself? How to Delegate

Why do I keep doing everything myself as a manager?

Usually there are several causes, and they stack.

The habit of being a strong performer. You were promoted because you did the work well. Solving things quickly, doing them right, fixing the tough mistake: that became your signature. As a manager, the same skill keeps firing automatically. It's easier to do it than to explain it.

A fuzzy role. Nobody told you what's now your job and what isn't. Old tasks stayed, new ones arrived, and together they add up to two jobs.

Too few people or too little authority. The team is short-handed, people are new, system access hasn't been set up, or decisions need sign-off from above. Then "I do it myself" isn't weakness. It's how the setup works.

Fear of consequences. An employee's mistake will cost your reputation, not theirs. That's a real risk, and it calls for a sensible review process, not self-blame.

The pleasure of being needed. It feels good to be the person without whom everything stops. That's understandable, and I write about it in why irreplaceable people don't get promoted: being indispensable often keeps you in place.

Occupational health guidance commonly lists role clarity, workload, support, and having a say in how work gets done as key features of a healthy workplace. That keeps the scale in view: a manager needs more than personal skills. She needs a working system where responsibilities, resources, and authority line up. If the system doesn't line up, no amount of "I'll learn to delegate" will work.

What counts as my job now?

A strong specialist is used to proving competence through her own output. In a leadership role, part of the output comes through other people. You explain the goal, distribute the work, align priorities, give feedback, and spot constraints in time. These actions feel less tangible, especially if your earlier professional work was satisfying.

Picture a manager who rewrites every report her employee turns in. The report gets better for the next deadline, but the employee has no idea what to change next time. The manager gets the same level of work again and grows more convinced that nothing works without her. Here it helps to check not just the quality of the work but whether she passed on criteria, time to learn, and a chance to fix the result independently.

To see the real picture, run a small audit. For one week, keep a simple table and note at the end of each day where your time went:

1. My own professional tasks left over from my previous role.
2. Work I took back from employees because it was faster.
3. Management: assigning tasks, meetings, feedback, planning.
4. Supporting the team: answering questions, removing obstacles.
5. Everything else: reports upward, approvals, urgent surprises.

After a week, look at the proportions. If management takes a sliver and "took back from employees" takes a big share, that's a signal. If most of your time goes to "my own tasks from the old role," it's a conversation to have with your boss, because you're effectively doing two jobs.

What stops me from handing a task off? Four reasons

When you take a task back, pause and ask what's actually going on. Usually it's one of four things.

1. The quality standard exists only in your head. You say, "Do a good analysis," but don't say which decision it supports, what data is required, or how much is enough. The employee brings something different, and you read it as proof they can't do it. Redoing it feels faster than talking, though next time it all repeats.

2. The person lacks authority. They understand the task but don't have the access, time, or right to make necessary decisions. On paper, the work was delegated; in reality, every step needs your approval. Delegation turns into extra email. Check in advance which actions the person can take alone and where your decision is truly needed.

3. The risk is justified. The task is risky, a mistake would be expensive, and the person has little experience. You don't have to choose between total control and blind trust. You can hand off a limited part, build in a checkpoint, or arrange training first.

4. It's hard for you to tolerate a different way. The employee does it differently from how you would, though the result is acceptable. This calls for a talk with yourself: what's the difference between "wrong" and "unfamiliar"?

To identify yours, take the last task you took back and answer in writing: What quality standard did I state? What could the employee decide alone? How costly would a mistake have been? What stopped me? Your answers show what to change: instructions, permissions, the review process, or your own expectations.

Control as a way of coping with anxiety is a close cousin of what I describe in why control feels safe but drains you.

How do I hand off the outcome, not just the task?

Pick one recurring task that someone else can realistically learn. Not the hardest or riskiest, but one that repeats and eats your time. Prepare a short assignment in six parts:

1. Why. What the work is for and who will use the result.
2. Outcome. What should come out, and in what form.
3. Deadline. When it's due and when to do a midpoint check.
4. Definition of done. How you'll both know it's finished.
5. Resources. Access, materials, people they can go to.
6. Decision limits. What they can decide on their own and what to flag or run by you.

You don't need a long manual. Sometimes a brief agreement and a good example are enough: "Here's what it looked like last time and why it worked."

Then ask the employee to describe the plan in their own words. This checks shared understanding; it's not an obedience test. Questions at this stage let you spot differences in expectations before hours are spent. Try: "How do you see this work? What will you do first?"

Also agree on when to flag a problem: "If you haven't made progress in a day, tell me and we'll look together." That way the person doesn't hide trouble until the last minute or ask permission for every small thing.

If you notice you habitually speed up at work instead of stopping to pick what matters most, take a look at why women speed up instead of choosing what matters. Rushing often hides a lack of priorities.

What do I say when the work comes back wrong?

The most tempting move is to redo it quietly. It saves time today and costs a lot tomorrow: the employee never learns what to change, and you get proof that "it won't work without me." Instead, give feedback. It takes ten minutes and pays off later.

A simple four-step pattern:

1. Acknowledge what worked. "The structure is clear, and you covered every section."
2. Name the gap against the standard. "The director needs the conclusion on page one, and here it's on page five."
3. Ask about the cause. "What got in the way? Was it unclear who the report was for, or did you run short on time?"
4. Agree on the next step. "Please revise it by tomorrow. If questions come up, message me."

Notice there's no "you always" or "why do you never." The feedback is about the result and the standard, not the person. It leaves the employee room to fix it, and gives you a chance to see what was missing: instructions, access, time, or experience.

If the gap is serious and the deadline is close, it's fine to help within limits, like working together on the hardest section. But then talk about what to change in how the task is set up. Otherwise the help quietly becomes taking the whole role back.

Sometimes the cause of the mistake is your own clarity: you didn't explain enough. Admitting that isn't weakness, it's a valuable signal. "I wasn't clear, let's sort it out" creates an atmosphere where people aren't afraid to ask questions.

How much oversight is enough?

Control isn't bad in itself. The problem is when it's the same depth for every task and every person. It should match two things: the cost of a mistake and the person's experience.

A simple frame:

• Low risk, experienced person. Hand off the whole task and review the result. No midpoint checks needed.
• Low risk, newer person. Let them make and fix mistakes, but check their approach at the start.
• High risk, experienced person. Agree on the plan and one checkpoint; trust the rest.
• High risk, newer person. Hand off a limited part, work through it together, coach, and check more often.

Tie checkpoints to the content. For instance, first agree on the approach, then look at a working draft. If you check every move, it's hard for the person to become independent. If you vanish until the end, the risk of a surprise goes up. The right rhythm depends on the task and the person's experience, and you can adjust it based on results.

Factor in your own state, too. When you're tired and anxious, control grows on its own. Then the issue is less delegation technique than getting back to an even keel. For more on staying steady under pressure, see self-regulation: how to get your footing back.

What if the team truly has no capacity?

Delegation doesn't create hours out of thin air. If everyone's overloaded, handing off a task just moves the problem. Then you need a conversation about priorities: which results are mandatory, what can be postponed, shrunk, or stopped, and which resources are missing.

It helps to go to your boss with a concrete picture, not only a message that you're tired. Use the results of your weekly audit:

"Over the past two weeks, my time broke down like this: X hours on tasks from my previous role, Y on managing the team. To do the new role, I need one of three things: hand off some of my old tasks, add capacity to the team, or change priorities. Which is realistic?"

If the new role was added on top of the old one with no reset of expectations, say so explicitly. Which of your old tasks stay? Which should go to others? What are you personally responsible for, and what through how you organize the work? The answers can be uncomfortable, but clarity lets you discuss real conditions instead of endlessly trying to fit several incompatible roles.

If you don't have the authority at your level to change anything, that's important information too. Part of your load then isn't a result of your weakness, but of how the organization is built. I touch on it in why all the invisible work in the office lands on you: workload is rarely distributed at random.

If reorganizing isn't possible and the load exceeds reasonable limits, it's worth weighing bigger options: changing the terms, the shape of the role, or the workplace. That decision doesn't have to be fast, but you also shouldn't put it off for years.

What can I do this week, and when should I get support?

Start with one task and one point where you usually take it back. Then:

1. Prepare the assignment in six parts: why, outcome, deadline, definition of done, resources, decision limits.
2. Agree on a midpoint check.
3. When you feel the urge to redo it, stop and give feedback instead.
4. After a week, assess: what can this person now do without you? Which standards did you have to clarify? Where was your involvement truly needed, and where was it habit?

If the cause is missing people or authority, direct your effort at discussing those conditions. Leadership gets steadier when results rest on well-organized work, not on your constant readiness to quietly cover every gap.

Pay attention to how you feel, too. If you notice constant exhaustion, insomnia, irritability, a sense that your work is meaningless, or physical signs of tension, don't write it off as a "transition period." Talk with your doctor or a licensed therapist. Chronic overload affects health, and support isn't a luxury.

You don't have to become a perfect manager right away. One step is enough: hand off one outcome, give one calm piece of feedback, and say out loud once what you need to do the job.