top of page

Delegation in Leadership: Why “It’s Faster If I Do It Myself” Costs More Than Time

  • Writer: Barbara Ormsby
    Barbara Ormsby
  • Jan 26
  • 5 min read

Updated: 6 days ago

Most experienced leaders know this sentence well.

It usually shows up late in the day.

Or in the middle of a packed week.

Or right after yet another small thing has come back onto their desk.



You notice it almost casually.

You don’t make a big deal out of it.


You just do it yourself.


Because it is faster.

Because explaining it would take longer.

Because you don’t want to correct it later.

Because right now, there isn’t the time for learning curves.


And yet, this sentence is one of the most expensive habits in leadership.


Not because it’s wrong.

But because of what it quietly creates over time.


Why delegation doesn’t fail where we think it does


Most conversations about delegation focus on techniques.


How to explain tasks more clearly.

to set expectations.

How to follow up without micromanaging.

How to give feedback.


All of that matters.


But in practice, delegation rarely fails because leaders don’t know how to delegate.


It fails because delegation collides with pressure.


And pressure changes behavior.


When the workload increases, when stakes rise, when deadlines tighten, leaders don’t revert to best practice.

They revert to what feels safe.


And for many leaders, what feels safest under pressure is stepping in.


Not because they don’t trust their team.

But because they trust themselves more in that moment.


They know they can get it done.

They know what “good” looks like.

They know how to avoid mistakes.


So they take it back.


Quietly. Repeatedly. Automatically.


The hidden deal leaders make with themselves


Here’s the unspoken deal many leaders make:


“I’ll just do this one thing myself.

Just this once.

Just to get us through this phase.”


It sounds reasonable.

It often is reasonable.


But the cost is rarely visible immediately.


What accumulates instead is something else:

  • Work keeps flowing upward

  • Decisions concentrate at the top

  • Teams wait rather than decide

  • Leaders become the bottleneck without noticing


And over time, leadership capacity shrinks.


Not because the leader isn’t capable.

But because they are carrying too much of what no longer needs to sit with them.


Delegation isn’t all-or-nothing, but we often treat it that way


One of the reasons delegation feels so uncomfortable is that it’s often framed as a binary choice:


Either“I do it myself”

or

“I fully hand it over and hope for the best.”


Most leaders intuitively know this is a false choice.

And yet, in practice, this is how delegation often shows up.


Especially under pressure.


The missing piece is differentiation.


Delegation isn’t a single act.

It’s a spectrum of responsibility.


From very tight guidance

to shared thinking

to independent decision-making.


Problems arise not because leaders delegate too little or too much, but because the level of delegation is unclear, mismatched, or implicit.


So leaders step back in.

Teams hesitate.

And everyone feels a bit frustrated, even though no one is doing anything “wrong.”


Why “doing it yourself” feels so compelling


There’s another layer that rarely gets named.

Stepping in doesn’t just solve the task.

It regulates the leader.


When things feel messy or uncertain, doing something concrete restores a sense of control.


You move from ambiguity to action.

From coordination to execution.

From leadership into doing.


It feels grounding, efficient, productive.


And in the short term, it works.


Which is exactly why it’s so hard to stop.


A small pause: noticing your own patterns


Instead of asking, “Why can’t I delegate better?”

a more useful question might be:


“Where do I consistently step in ; and under what conditions?”


Try this as a brief reflection, not as a performance review:


Look back at the last four weeks.


Where did work land back on your desk that, technically, didn’t belong there anymore?


Not because your team failed.

Not because someone messed up.

But because you chose to take it on.


Maybe because it felt faster.

Maybe because the stakes were high

.Maybe because you didn’t want to explain it again.


Just notice.


Then ask yourself:

  • What made delegation feel uncomfortable in those moments?

  • What were you worried might happen if you didn’t step in?

  • What did you gain by doing it yourself?


There are no right answers here.

Only patterns.


The cost we rarely calculate


Most leaders underestimate the cost of non-delegation.


They calculate time saved today.

But they don’t calculate time lost tomorrow.


Every task you take back does more than fill your calendar.


It teaches the system something.


It teaches people when decisions really matter, they should wait.

It teaches them that accountability ultimately sits higher up.

It teaches them that initiative has limits.


Again, not intentionally.

Not maliciously.


But systems learn from behavior, not from intention.


And over time, this learning shapes how leadership actually functions, regardless of what’s written in role descriptions.


Delegation as leadership design, not task transfer


At its core, delegation is not about offloading work.

It’s about designing decision-making.


Who decides what?

With how much autonomy?

With which feedback loops?

At what level of risk?


These are leadership design questions, not productivity hacks.


When delegation is treated as task transfer, leaders oscillate between control and withdrawal.


When it’s treated as leadership design, delegation becomes more precise, more intentional, and paradoxically more comfortable.


Because clarity reduces risk.


Why this gets harder as leaders become more senior


Ironically, delegation often gets harder the more senior a leader becomes.


The tasks are less visible.

The decisions are more consequential.

The margin for error feels smaller.


And because senior leaders are usually competent, experienced, and reliable, stepping in continues to work.


Until it doesn’t.


At some point, the issue isn’t execution anymore.

It’s capacity.


The organization has outgrown the leader’s personal bandwidth.


And no amount of working harder will solve that.


A different way to think about delegation


Instead of asking:


“What can I give away?”


Try asking:


“What decisions still require me, and which ones don’t anymore?”


This subtle shift changes the conversation.


It moves delegation away from tasks and toward responsibility, judgment, and trust.


It also makes visible where leaders are still needed, and where they’re not.


Which is often the more uncomfortable realization.


The quiet risk of staying “useful”


Many leaders hold on longer than necessary because being needed feels reassuring.


Being the one who fixes things.

Who sees the whole picture.

Who catches what others miss.


Letting go of that role can feel like losing relevance.


But leadership isn’t about being indispensable.


It’s about building systems that function without constant intervention.


And that requires a different kind of confidence.


Closing thought


Delegation doesn’t fail because leaders don’t care.

It fails because leadership under pressure defaults to familiarity.


If “it’s faster if I do it myself” shows up regularly in your inner dialogue, it’s not a character flaw.


It’s a signal.


A signal that your role may have outgrown the way you’re currently working.


And that delegation, approached thoughtfully, isn’t about giving things away, but about creating the conditions for good decisions to happen without you.


That’s not less leadership.

That’s leadership at scale.

bottom of page