Delegate to Elevate: The Leadership Lesson That Forced Me to Let Go
Competence is what got you here. It is also what can keep you here.
By Eric J. Dalton · · 9 min read
There is a specific trap waiting for capable leaders, and the cruel part is that you walk into it by being good at your job.
You know how to do the work. You have done it for years. You know exactly what "correct" looks like, and you can produce it reliably, and you are aware (with a certainty that feels like realism rather than ego) that if you hand it to someone else the outcome will probably be worse, at least at first.
So you keep it.
You keep it through the promotion. You keep it as the organization grows. You keep it while your calendar fills with things only you can do, and you keep doing it late at night because it still has to get done.
Eventually your competence becomes your cage.
The work I would not release
For me the clearest example was compliance.
I held significant compliance responsibility and I was heavily involved in the day-to-day of it. Not supervising it, doing it.
There were good reasons, or at least reasons that sounded good. Compliance matters enormously in our field. The consequences of getting it wrong are not abstract; they affect patients, staff, licensure, and the organization's ability to operate at all. I understood it deeply. I was capable of handling it personally. And I cared about the quality of it in a way that made the idea of someone else owning it genuinely uncomfortable.
What I did not fully see at the time was the cost.
Every hour I spent inside compliance detail was an hour I did not spend on growth, innovation, strategy, or organizational development. Not because I was disorganized, because there are only so many hours, and I was spending them on work that was important but that did not require my particular level of contribution.
I was not protecting quality. I was capping the organization at the size of my personal capacity.
Eventually your competence becomes your cage.
The coaching that would not let it go
The person who forced this into the open was my business coach. He is an excellent homecare leader and innovator in his own right, which mattered. He was not offering generic executive advice. He understood the specific work I was clinging to and why I thought I needed to.
We were working through EOS principles, and my coach pushed me hard on the concept of Delegate and Elevate. That framework belongs to EOS, the Entrepreneurial Operating System, and I want to attribute it plainly rather than absorb it as my own.
The tool itself is straightforward: sort what you spend time on by whether you love it and are great at it, and by whether it actually requires you. Most leaders discover uncomfortable things when they do this honestly.
My coach recognized something in my results that I had been explaining away. I was holding onto too much personally, and every one of my explanations was internally consistent and collectively disastrous.
He put the actual question in front of me, which was not about compliance at all:
If you continue personally owning every important operational responsibility because you believe you can do it best, when exactly does the organization get to grow past you?
I did not have an answer. There is not one. That is the whole problem: a leader who is the quality control mechanism for everything important has built a system that cannot exceed one person's throughput, no matter how many people are employed.
What control looks like from the inside
Here is what I want to be honest about, because I think it is the least discussed part of this.
Control does not feel like control. It feels like responsibility.
It presents itself as quality assurance. As caring more. As having standards. As protecting the organization from risk. Every one of those framings is flattering, and every one of them can be true while the underlying behavior is still doing damage.
Perfectionism does something similar. It disguises itself as leadership, when frequently it is a leader's discomfort with the fact that someone else's competent work will look different from their own.
And the sentence at the center of all of it, if I want it done right, I have to do it myself, sounds like accountability. Said once about a genuinely critical thing, it is fine. Said as an operating philosophy over years, it is a description of a bottleneck.
"If I want it done right, I have to do it myself" sounds responsible. Repeated long enough, it is a description of a bottleneck.
What delegation is not
I want to draw a firm line here, because the word gets used to describe two completely different behaviors.
Delegation is not dumping work on someone. Handing a responsibility to an unprepared person, without context, standards, or support, and then being disappointed when the result is poor is not delegation. It is abdication, and it produces exactly the outcome the leader feared, which then gets used as evidence that delegation does not work.
Real delegation requires investment, and the list is not short: training, mentoring, clearly articulated standards, explicit expectations, ongoing support, real accountability, and patience while someone climbs a learning curve you climbed years ago.
The leader's responsibility is to develop another person until the quality of the delegated work holds without them.
That is a substantially larger commitment than doing the task yourself in the short run. It is the only version that changes anything in the long run.
Two elevations
This is the reframe that finally moved me.
The goal of delegation is not to get something off your desk. Framed that way, it is a selfish act with an obvious loser, and the person receiving the work can feel it.
The goal is to create capability in another human being.
When you do it properly, two people rise.
The employee elevates, into greater skill, greater confidence, and genuine ownership of something that matters. This is not a soft benefit. For most people, the experience of being trusted with something significant, supported through it, and then held accountable for it is the single most developmental thing that happens in a career.
The leader elevates, into work that requires a higher level of judgment, strategy, innovation, and leadership. The capacity you free up is not for rest. It is for the work only you can do, which almost certainly is not getting done right now.
The goal is not to get the task off your desk. The goal is to create capability in another human being.
The nuance
Not everything should be delegated, and I do not want this to read as though it should.
Some responsibilities require executive ownership. Certain decisions demand your authority. Certain relationships cannot be transferred. Certain risks sit with you regardless of what an org chart says. In regulated environments in particular, there are accountabilities that are legally and ethically yours and stay yours.
Delegation has to match competence, authority, risk, and readiness. Moving something to a person who is not ready is not brave; it is negligent.
But the question worth asking regularly is a harder one than "should this be delegated." It is:
Am I doing this because only I can do it, or because I have never invested in teaching anyone else?
The second answer is far more common than leaders like to admit, and it is entirely within your control to change.
The progression that works
When I do this deliberately now, it follows a sequence. Skipping steps is what makes delegation fail.
Identify. What am I doing that no longer requires my highest-level contribution? Be specific, and use your actual calendar rather than your impression of it.
Select. Who could grow into this? Look for capacity to develop, not for someone who can already do it. If they can already do it, you should have transferred it a year ago.
Train. Transfer context, not just instructions. Instructions tell someone what to do; context tells them what to do when the situation does not match the instructions. Most delegation fails at exactly that gap.
Shadow. Let them observe, then let them practice with support. This phase feels slow. It is the phase that determines everything.
Transfer. Move genuine ownership. Not a version where every decision comes back to you for approval, which is theater. It costs the employee autonomy and costs you the time anyway, while producing none of the benefits of either arrangement.
Coach. Review outcomes, improve capability, correct drift. Ownership does not mean absence.
Elevate. Deliberately use the created capacity on work only you can do. If you skip this step, the space fills with something else and you have gained nothing.
The valley in the middle
Nobody warns you about the middle part, so I will.
There is a period after you transfer something and before the other person is fully proficient in which the quality genuinely does dip. Not catastrophically, if you selected and trained well, but noticeably. Things take longer. Decisions you would have made instantly get considered. Something gets handled in a way you would not have handled it.
This is the exact moment where most delegation collapses, because the dip appears to confirm everything the leader feared. And taking it back feels justified. It feels like protecting the organization. It is even framed that way internally: I gave it a fair shot and it was not working.
What actually happened is that the leader encountered the normal cost of development and interpreted it as failure.
Two things help here. The first is deciding in advance what level of variance is acceptable and what is genuinely unacceptable, because those are different and the distinction gets very blurry in the moment. Some outcomes have a hard floor: in regulated work, particularly, there are things that simply cannot be gotten wrong while someone learns, and those need supervision structured around them rather than blind trust. But a great deal of what leaders reclaim is not a floor issue. It is a preference issue wearing a floor issue's clothing.
The second is being honest that reclaiming the work is a decision with its own cost. When you take something back, you have not returned to neutral. You have taught that person that ownership is conditional and temporary, and you have made the next transfer harder, for them and for everyone watching.
The valley is the price. There is no version that skips it.
What I would say to a leader holding on
Your next level probably does not require you to do more.
It more likely requires someone else becoming capable of doing what you have not been willing to release, and it requires you to invest in making that true, which will cost you time before it gives any back.
The work I was best at was the work I most needed to stop doing personally. That is not a paradox. It is just what happens when a leader's job changes and their habits do not.
