It's 6:20 p.m. The office is quiet. Most of the team has gone home.
An engineering manager is still at their desk, rebuilding a project schedule that one of their direct reports was supposed to present the following day. Earlier that afternoon, the employee had stopped by with a "quick question." The manager opened the file, spotted three errors, and said, "let me take a look at that."
Twenty minutes later, the employee was gone and the manager was the new owner of the problem.
The manager told themselves it was faster this way, and that's probably true. They knew the project, the risks, and the history behind every decision. They knew they could correct the schedule in half the time it would take to explain what's wrong.
But they're still there at 6:20pm.
Tomorrow, the employee will return with another quick question. The manager will step in again and over time, both of them will become frustrated with each other. The manager begins to feel overloaded and unsupported. The employee feels underused, micromanaged, and unsure of what they own.
This is a common way leadership burnout starts.
Not with an impossible workload.
But with work that should have stayed with someone else.
The work changed, but the leader didn't
Technical leaders struggle with delegation for very understandable reasons. They're promoted because they were experts at doing the work.
They solved hard problems and found mistakes that no one could. They understood the system better than anyone else in the room and when something went wrong, the team trusted them to fix it.
This reputation became their identity.
Then they moved into leadership, and everything changed.
Their value no longer comes from solving technical problems, it comes from building a team that solves these problems without them.
It sounds simple, but it in practice it's not.
A senior engineer who becomes a manager may still be the most technically capable person on the team and it's normal that they'll complete tasks faster and better than anyone else.
In the short term, stepping in looks responsible - helpful even.
The issue is what happens after the tenth time.
The leader becomes the default reviewer, decision-maker, and safety net. Every difficult task finds its way back to their desk. Their calendar fills up, but the critical leadership work gets pushed off indefinitely. Coaching people, improving systems, and preparing the organization for what comes next becomes an afterthought.
To put it simply, the leader is busy all day, but never works on what's important.
Why letting go can feel like losing value
Delegation is often treated like a time-management technique but for technical leaders, it's usually more personal.
Doing the work feels useful. It provides a clear result and a sense of control. You can point to what you fixed, reviewed, or delivered.
Leadership work is less immediate. You may spend an hour helping someone think through a problem, then watch them make a decision that's not the one you would have made.
You may need to tolerate a slower process, a rougher first draft, or even a few mistakes.
This can feel inefficient... and risky.
It can also feel uncomfortable because the leader is no longer proving their competence in the same way. They're creating the conditions for someone else to become competent.
And that requires a different measure of success.
Instead of asking, "Did I solve it?" the leader needs to ask, "Did the team become more capable of solving this next time?"
Technical leaders understand this intellectually but for many, their behaviour tells a different story.
They rewrite the report instead of giving feedback.
They answer the customer instead of letting their project manager give the response.
They make the design decision because the meeting's running too long.
They tell themselves they'll delegate more once things calm down.
But they never do.
The team pays for it as well
When leaders carry work that belongs to their team, the cost spreads far beyond their own workload.
The first cost is learned helplessness.
People stop bringing recommendations and start bringing problems. They learn that the safest move is to ask the manager before acting. Initiative drops because the manager will probably redo everything anyway.
The second cost is slower decision-making.
Every important question moves upward. Small issues wait for the leader's attention. Projects stall when they're unavailable. The organization becomes dependent on a one-person bottleneck who's already overloaded.
The third cost is resentment.
The leader thinks, "Why can't anyone take ownership?"
The team thinks, "Why won't you let us?"
Both sides are right.
A manager may have employees who need clearer expectations, better judgment, or stronger technical skills. But if the manager repeatedly steps in before these skills develop, the team never gets enough experience enough to improve.
Responsibility without authority creates frustration. Authority without support creates failure.
Effective delegation requires both.
It means handing over ownership while still providing the context, boundaries, and coaching needed to succeed.
A simple test for what should leave your desk
Most leaders don't need to delegate everything. Some decisions and tasks should stay with them.
The challenge is knowing which ones to hand off.
This week, take any task you're carrying and ask yourself four questions.
1. Does this require my role, or my experience?
Some work can only be done by you. This can include strategic planning, managing sensitive performance issues, or making decisions that affect the team or organization as a whole.
Other work only feels like it requires you because you've done it before.
Experience is valuable, but it doesn't mean you should keep ownership of the task. Your experience may be better used to guide someone else.
2. Am I doing this because it is faster today?
If the main reason you're holding onto a task is speed, be careful.
Doing it yourself may save thirty minutes today and cost you fifty hours over the next year.
Teaching, reviewing, and correcting take longer at first, but it's not time wasted. It's the cost of building long-term capacity.
The question isn't, "Who can do this fastest right now?"
It's, "Who will be able to do this six months from now?"
3. What is the risk of letting someone else handle it?
Technical leaders treat discomfort as risk.
They imagine poor quality, a missed deadline, or an unhappy customer. Sometimes these risks are real. Often they can be managed.
You can delegate in stages. You can set checkpoints. You can define what requires approval and what doesn't. You can ask someone to bring you a recommendation before they act.
The choice is not between doing everything yourself and abandoning the team.
Good delegation has structure.
4. What is my team learning from my behaviour?
Every time you take back a task, you teach something.
You may be teaching that mistakes are unacceptable.
You may be teaching that your approach is the only one.
You may be teaching that difficult decisions belong to the boss.
Or you may be teaching people how to think, how to recover, and how to take responsibility.
Look beyond the outcome. Ask what pattern you're reinforcing.
Delegation is a skill, not a trait
Some leaders assume they are simply "bad at delegating", which self-limiting belief. It makes the problem sound fixed.
It's not.
Delegation is learned.
It involves setting clear expectations, matching responsibility to capability, deciding how much oversight is appropriate, and resisting the urge to take work back the moment it becomes uncomfortable.
It requires honest self-awareness.
You need to notice when quality concerns are legitimate and when they're an excuse for control. You need to see when you're protecting the business and when you're protecting your identity.
That kind of work is difficult to do alone because the behaviour often looks reasonable.
This is where 1:1 executive coaching helps.
Telling a leader to "delegate more" but not explaining how isn't helpful. Examining the situations where delegation breaks down are.
Which decisions keep coming back to you? Which people are ready for more ownership? What are you afraid will happen if you stop stepping in?
If this resonates, the fix usually isn't a new habit you can pick up on your own. It's a pattern that's easier to see with someone objectively asking the right questions and holding up the mirror of self-reflection.
That's the actual work of 1:1 executive coaching: Explore Executive Coaching →
Knowing that you should delegate is easy.
Changing the habits, systems, and assumptions that keep you chained to your desk after everyone else has gone home isn't.
Burnout isn't always a sign that you have too much to do.
Sometimes it's a sign that you're still doing the job you were promoted out of.
Dr. Will Ferry is an executive coach for engineering and technical leaders, based in North Vancouver. He holds a PhD and P.Eng. with ICF coaching credentials and over twenty years leading engineering teams at Pratt & Whitney Canada, Genesis Robotics, and Molex. If this article hits home, it's time to examine at your beliefs around delegating. Contact Will here to discuss delegating effectively: https://willferry.com/contact