How Do I Help a New Manager Stop Trying to Do Everything Themselves?

The first problem is often identity

The new manager still thinks:

“My value comes from what I personally produce.”

That made sense in the old role. Now it can become a trap. The new question is:

“What can the team produce because I manage them well?”

That is a different source of value.

Do not simply tell them to delegate more

That advice is too vague. They need to understand: what to delegate; to whom; with what authority; to what standard; and with what review point. Delegation is a management discipline. Not an instruction to throw work away.

Ask what they are still doing from their old job

Start there. List it. Which tasks are genuinely still appropriate? Which are habit? Which should now sit elsewhere? Which could be used to develop someone? This often reveals why the manager has no time.

Promotion should involve subtraction

Businesses are very good at adding responsibilities. New title. New team. New meetings. New targets. New people problems. But what was removed? If the answer is nothing, you may have designed overload into the role.

Decide what should leave the manager's plate

Be specific. Not:

“Delegate more.”

But:

“By the end of this month, these three responsibilities need to be owned by other people.”

That creates movement.

Keep some technical work deliberately

A new manager does not necessarily need to stop all technical work. Some may help them: stay connected; maintain expertise; support customers; understand the operation. Fine. But choose it consciously. Do not let the old job remain by default.

Distinguish high-value technical work from comfort work

This is important. Managers often keep doing work because they enjoy it. They are good at it. It feels satisfying. Managing people can feel slower and messier. So when pressure rises, they retreat to the work they know. Ask:

“Are you doing this because the business genuinely needs you to, or because it feels easier than managing?”

Watch for the “it’s quicker if I do it” trap

Of course it is. Today. You have done it 500 times. The employee has done it five. If you use today's speed as the only measure, you will always take the work back. The real question is:

“What happens in six months if I keep doing this myself?”

Speed today can create dependency tomorrow

That is the trade-off. Do it yourself: fast now; same dependency later. Teach and delegate: slower now; greater capability later. Managers need to understand this.

Help them choose work to delegate

Good early delegation candidates are tasks that: repeat; matter enough to be useful; are not catastrophically risky; give somebody a genuine opportunity to grow. Do not start with the most dangerous issue in the business. But do not only delegate photocopying either.

Delegate responsibility, not rubbish

If managers keep every meaningful task and distribute only the boring parts, the team will not develop. People grow through real ownership.

Define the outcome

Before handing work over, ask:

“What does good look like?”

The manager needs to articulate the destination. Not simply:

“Just sort it.”

Clarify the standard

What matters? Quality? Timing? Customer impact? Margin? Compliance? Make the important things explicit.

Clarify authority

What can the employee decide? What needs consultation? What must be escalated? Without this, delegation often creates either paralysis or surprise.

Agree the review point

When will you come back to it? This reduces the new manager's urge to check every twenty minutes. If both people know: “We review Thursday at 2pm,” the manager can let go.

Follow-up is not failure to delegate

Some managers think delegation means:

“I handed it over, so I must never look at it again.”

No. Good delegation includes follow-up. The difference is that the employee owns the work.

Teach the manager to check progress, not control every movement

Ask: What has happened? What is at risk? What support is needed? Do not: rewrite every sentence; direct every tiny action; insist on exact methods where they do not matter.

Outcomes and methods are different

Some methods matter. Safety. Legal. Quality. Critical process. Fine. But where multiple sensible routes exist, give room.

Different does not mean wrong

This is one of the hardest lessons for a strong technical performer. They think:

“That is not how I would do it.”

Good. Does it meet the standard? If yes, leave it alone.

Stop them from redoing perfectly acceptable work

Nothing kills ownership faster. Employee completes task. Manager tweaks. Reformats. Rewrites. Changes. Eventually the employee thinks:

“Just do it yourself.”

And the manager wonders why nobody takes ownership.

Ask what genuinely needed changing

Was the work below standard? Or merely different? That distinction matters.

Teach them to tolerate the learning curve

A developing employee will not perform like the experienced manager immediately. That is normal. If perfection is required from the first attempt, delegation becomes impossible.

Let people make recoverable mistakes

This is part of development. Mistake. Review. Learn. Try again. Do not take the work back permanently after one wobble. But do not allow repeated errors without management Development is not endless tolerance. If the same gap keeps repeating: clarify; coach; follow up; address performance if necessary. Do not swing from micromanaging to ignoring.

Ask more questions

When the employee comes back:

“What should I do?”

the new manager's instinct is to answer. Instead:

“What do you think?”

That changes the dynamic.

Do not answer after three seconds

Wait. This is harder than it sounds. The manager knows the answer. Silence feels inefficient. Let the person think.

Ask for options

“What are your options?”

Then:

“Which do you recommend?”

Now delegation is also developing judgement.

Do not let delegated work boomerang automatically

Employee says:

“I’m stuck.”

Manager says:

“Fine, give it back.”

No. Ask:

“Where exactly are you stuck?”

Maybe support is enough. Keep ownership with the employee where appropriate.

Support without taking over

Perhaps the employee needs: context; access; training; a decision; a sounding board. Provide it. Then return the ball.

Ask who leaves with the next action

This is one of the best tests. After the conversation, who is doing what? If the manager repeatedly leaves carrying the work, delegation is failing.

New managers often want to be helpful

That is admirable. But helpful can accidentally become rescue. The employee asks. The manager fixes. Everyone feels good. Until the manager has twelve people and twelve sets of problems.

Teach them that saying “What do you think?” is helping

It may feel less helpful than giving the answer. In reality, it may be far more developmental.

Stop becoming the department's help desk

If every question comes to the manager, ask why. Do people lack: authority? knowledge? confidence? documentation? Some of those can be fixed structurally.

Capture repeated answers

If the manager answers the same question every week, perhaps the knowledge should become: a checklist; process; guide; decision rule. That reduces future dependency.

Do not make the manager the only person who knows

Strong individual contributors often become knowledge bottlenecks. The new management job is to spread knowledge. Not protect it. Cross-train Who else needs to know? What happens when the manager is away? The team should become more resilient.

Teach them to develop shoulders

Who beneath them can carry more? Who can solve more? Who can become a source of judgement? That is how management capacity grows.

Give each employee appropriate stretch

Not identical stretch. Who is ready for what? The manager needs to learn their people.

One-on-ones help enormously

A useful one-on-one gives space to discuss: progress; problems; development; decisions; commitments. That reduces constant reactive interruption.

Do not turn the one-on-one into a manager task list

The employee should bring thinking. They should leave carrying their responsibilities. Otherwise the manager accumulates everyone's work.

Watch who talks most

If the manager does 90% of the talking, there may be too much telling and not enough thinking.

Use “Humour me”

When someone says:

“I don't know.”

the manager may be tempted to answer. Try:

“Humour me. If you did know, what would you say?”

Often a thought appears.

New managers need to learn to hold the boundary

An employee says:

“But you’re better at it.”

Maybe. That does not mean the manager should keep doing it.

“I’ll help you learn it.”

Different answer.

Stop protecting people from stretch

Managers sometimes believe they are being kind by taking hard work away. But meaningful stretch is how people develop. Support them through it.

Do not delegate only when overwhelmed

That creates terrible delegation. Manager hits breaking point:

“Here, take all of this.”

No context. No standard. No review. Then it fails. Then manager says:

“Delegation doesn’t work.”

It does. That was dumping.

Delegate before you are desperate

Deliberately. One responsibility. Then another. Build capability progressively.

Use a delegation ladder

For important work:

Stage 1 — Watch me

Observe.

Stage 2 — Do it with me

Shared.

Stage 3 — You do it, I review closely

Practice.

Stage 4 — You do it, bring me exceptions

Greater independence.

Stage 5 — You own it

Management by exception. That makes progress visible.

Move people along the ladder

Do not leave everybody permanently at Stage 2. The goal is capability.

Tell the manager to review what they are still checking

Every week ask:

“What are you checking that no longer needs checking at this level?”

As reliability grows, oversight should reduce.

Trust should grow from evidence

This is not blind trust. If the employee repeatedly delivers well, give more room. If risk grows, adjust. That is sensible management.

Teach them to distinguish anxiety from risk

Sometimes the manager checks because the task is genuinely high risk. Fine. Sometimes they check because letting go feels uncomfortable. Those are different. Ask:

“What exactly are you worried will happen?”

Then design the right control.

Use evidence instead of hovering

If you need visibility, create: a measure; checkpoint; status; deadline. Do not sit on the employee's shoulder all day.

Manage by exception where possible

If something is on track, let it run. If it moves outside agreed parameters, raise it. That creates scale.

Stop the manager being copied into everything

New managers often want visibility. So they ask:

“CC me.”

Soon they have hundreds of emails. Ask what genuinely requires their attention.

Build better escalation rules

What should come to the manager? What should employees decide? What is urgent? What is merely information? That reduces noise.

Teach them to say “This is yours”

Not rudely. Clearly.

“I’m happy to help you think it through, but this decision is yours.”

That is a very useful management phrase.

Help them survive the discomfort of watching someone struggle

This is a big emotional shift. The manager sees the answer. Employee is thinking. The manager wants to save them. Wait. Appropriate struggle builds capability.

Do not turn every struggle into abandonment either

Support appropriately. This is not:

“Sink or swim.”

It is:

“I’m here, but I’m not going to take it away from you.”

Set explicit development goals for delegation

For the new manager, perhaps: one responsibility transferred this month; one employee developed to handle a recurring issue; one decision category moved down; one recurring question systemised. Now delegation becomes practical.

Track manager dependency

How many things still need them? Is that reducing? That can be a useful development measure.

Track upward dependency too

Does the new manager still bring every issue to their own boss? The same principle applies. They need to stop doing everything themselves and stop making their boss do all the thinking.

Bring recommendations upward

New manager says:

“I’m stuck.”

Their manager asks:

“What do you recommend?”

The leadership pattern should repeat at every level.

Do not compensate by escalating everything

Some new managers stop doing the work themselves but simply send every difficult issue upward. That is not management development. Ownership has only moved one direction.

The goal is distributed capability

Employees carry more. Manager carries higher-level responsibility. Senior manager works higher again. That is organisational growth.

Protect management time

If the manager has no time to: coach; delegate; review; develop, they will return to doing. Make room.

Review workload design

Sometimes the manager genuinely has too much technical work. No coaching technique will fix a badly designed job. Remove something.

Review staffing too

If the team is chronically understaffed, the manager may have no realistic option but to work operationally. Understand the environment. But do not let temporary pressure become permanent identity Busy period? Fine. Manager steps in. Afterwards: step back out. Otherwise the emergency operating model becomes normal.