Belinda Block

You became a leader because you were good at getting things done. And that’s exactly what makes delegating tasks so hard.

When you can do something faster, better, or exactly the way it needs to be done, the rational move feels like doing it yourself. But here’s the problem: the higher you go, the more that logic works against you. The work expands. The stakes grow. And the team you’re supposed to be leading ends up waiting on you instead of moving because of you.

Delegating as a leader isn’t about offloading work you don’t want to do. It’s one of the most consequential decisions you make, and most leaders are getting it wrong, not because they don’t know better, but because they haven’t addressed what’s actually in the way.

Why Leaders Resist Delegation (Even When They Know Better)

Ask most leaders whether they should delegate more, and they’ll say yes. Ask them why they don’t, and the answer usually isn’t honest.

The real reasons tend to be quieter than we admit. No one else does it the way I do. It’s faster if I just handle it. I don’t want to deal with it coming back wrong. If I let go of this, what does that say about my value here?

That last one is worth sitting with. A surprising number of leaders hold onto tasks because those tasks make them feel necessary. Delegation requires trusting someone else to carry something you’ve been carrying yourself, and that’s not just a logistical shift. It’s a psychological one.

There’s also a real skill gap. Many leaders were promoted without ever being taught how to delegate. They weren’t shown how to hand off clearly, how to calibrate oversight, or how to develop someone through an assignment. So they default to either doing it themselves or dumping without direction and getting burned by the outcome.

Neither works. And both are avoidable.

The 4 Levels of Delegation

Not every task should be handed off the same way. One of the most common mistakes leaders make is treating delegation as a binary, either you own it or you don’t. In reality, what is delegating done well looks like a spectrum.

Level 1: Do it and report back. You hand the task to someone and ask them to complete it and let you know when it’s done. You want the outcome. You don’t need updates along the way.

Level 2: Do it, but check in at key points. The task has some complexity or risk. You want progress touchpoints built in, not because you don’t trust the person, but because the work warrants it.

Level 3: Develop a recommendation and bring it to me. You’re delegating the thinking, not just the doing. The person does the analysis, weighs the options, and comes back with a proposal you can review and approve.

Level 4: Handle it completely. Full ownership. The person makes the decisions, manages the execution, and keeps you informed only if something significant shifts.

The level you choose should reflect the complexity of the task, the person’s experience with that type of work, and how much risk you’re carrying if it goes sideways. Getting that calibration right is the work. Most leaders default to Level 1 or 2 for everything, which quietly signals distrust and keeps the team dependent.

What to Delegate First (and What Never to Delegate)

A good place to start when identifying what to delegate: make a list of everything you did last week. Then ask yourself two questions: Does this require my specific expertise or authority? and what would happen if someone else did this?

Anything that’s recurring, process-driven, or doesn’t require a decision only you can make is a candidate. Administrative tasks, routine reporting, project coordination, research, first drafts, scheduling, these are all tasks that can and should move to someone else.

What doesn’t belong on the delegation list is different. Performance conversations with your direct reports stay with you. Strategic decisions that set direction for the organization stay with you. Situations that require your specific trust, authority, or accountability stay with you. Delivery of difficult news that is yours to deliver, that’s yours.

The key distinction isn’t whether the work is hard. It’s whether the work requires you specifically, your position, your relationships, your judgment in a way no one else can substitute. If the answer is no, the question isn’t whether to delegate. It’s to whom and how.

The Hand-Off Conversation: A Script

Most delegation fails not in the follow-up, but in the handoff. Leaders either under-explain and assume understanding, or they over-explain and accidentally undermine the person by walking through every step of how to do it their way.

Here’s a framework for a clear hand-off conversation:

What you’re handing off: “I’m asking you to take ownership of X.”

Why it matters: “This is important because it affects Y, and the outcome needs to be Z.”

What success looks like: “When this is done well, here’s what I expect to see…”

The level of authority: “I want you to handle this at your discretion / I want you to bring a recommendation / I want a check-in when you hit [specific milestone].”

What I need from you: “If you run into [this type of situation], loop me in. Otherwise, I trust you to move forward.”

Any constraints: “Budget is X. Timeline is X. These are the non-negotiables.”

That’s it. It doesn’t need to be a long conversation. It needs to be a clear one. If you can’t articulate what success looks like before you hand something off, you’re not ready to delegate it yet.

How to Check In Without Micromanaging

Once you’ve delegated, the relationship you have with that work changes. You’re no longer the doer. You’re the person who made a decision and needs to let it play out.

That doesn’t mean disappearing. It means being intentional about how you stay involved.

The best check-ins are built into the hand-off itself. You’re not dropping in randomly to see how things are going,  you’ve agreed in advance on what warrants an update. That removes the ambiguity that makes people feel watched.

When you do check in, ask forward-facing questions. “What do you need from me to keep this moving?” does a different thing than “Where are you on this?” The first positions you as a resource. The second positions you as an auditor.

Watch your own reactions too. If you’re checking in more than you agreed because you’re anxious, that’s information about you, not about the work. The solution isn’t to reclaim the task. It’s to figure out what’s driving the anxiety and address that directly, whether it’s a gap in the brief, uncertainty about the person’s skills, or your own difficulty letting go.

What to Do When Delegated Work Comes Back Wrong

It will happen. And how you handle it will determine whether your team learns from it or just hands work back to you as soon as it gets hard.

First, resist the urge to just fix it. That impulse is natural, you can see exactly what’s wrong and you know how to make it right. But if you silently correct the work and move on, you’ve taught the person nothing and trained yourself to keep doing it.

Before you assess the work, assess the brief. Ask yourself honestly: Did the person have what they needed? Were the expectations genuinely clear, or were they clear to you and assumed for them? A lot of what looks like underperformance on a delegated task is actually under-briefing by the leader.

If the brief was solid and the execution missed, that’s a development conversation, not a failure. Be specific. “Here’s what I was expecting and here’s the gap I see. Walk me through your thinking.” You’re not delivering a verdict. You’re opening a dialogue that builds judgment over time.

The only exception is if the mistake involves something that affects the organization, a client, or another person significantly. In those cases, fix what needs to be fixed quickly. Then have the conversation.

Delegation as Leadership Development for Your Team

Here’s what gets missed most often when leaders think about delegating tasks: every assignment is an opportunity.

When you give someone a stretch task, something at the edge of their current capability, with the right support around it, you’re not just freeing up your own time. You’re building organizational capacity. You’re creating leaders who can function independently. You’re showing people that you trust them enough to let them grow.

The leaders who hold on to everything don’t just burn themselves out. They inadvertently tell their teams that growth isn’t available here. People disengage. The good ones leave. And the leader who “can’t find good people” is often the leader who never gave good people a real chance.

Think about what each person on your team is ready to stretch toward, not what they’re already capable of handling, but what they could grow into with the right assignment. Delegate toward that. Be honest about your support. Let them work.

That’s not losing control. That’s what leadership is actually for.

Ready to Stop Carrying What Your Team Should Be Holding?

Delegation isn’t a time management tactic. It’s a leadership muscle,  and for most leaders, it’s underdeveloped not because they’re incapable, but because no one ever helped them build it deliberately.

If you’re consistently overloaded, stepping into execution instead of strategy, or unsure how to build the kind of team that moves without you, that’s worth looking at together.

Book a coaching call to map your delegation gaps.

#LeadershipDevelopment #ExecutiveCoaching #Delegation #ManagementSkills #LeadershipStrategy



Continue Reading

Executive Coaching in NYC
Learn about our coaching services
Organizational Consulting
Consulting for teams and organizations
Business Management Training
Leadership workshops and training
How Great Leaders Trust the ProcessIt's not about them...it's about youSpring Is a Natural Reset Point. Are You Using It?How Awareness Will Change Your Leadership This Year