The Belief That Keeps You Doing It Yourself
There is one sentence that keeps more leaders stuck than any bad system ever could: By the time I show you how to do it, I could have done it myself.
I know that sentence well. I have a task I have known for a long time should belong to someone else, someone with real bookkeeping skill who can reconcile accounts every month the way they need to be reconciled. I have not hired that person yet. Instead I keep holding onto the task the way you might hold onto a life jacket, even while standing on solid ground.
That sentence sounds practical. It even sounds responsible. In reality, it is a belief that quietly blocks delegation before delegation ever gets a fair chance. The math behind it is almost always wrong. Training someone does take time up front. It does not take forever. Most leaders stop the calculation at the hardest, most expensive week of training and never run it forward to what six months of delegation would actually save. A leader who only measures the cost of teaching, and never measures the cost of continuing to do the task herself indefinitely, will always land on the same wrong answer.
✦ ✦ ✦
Subscribe to the Weekly Roundup
Every Friday, one email with the week's Leadership Behind the Scenes articles. A headline and a one-line synopsis for each, so you choose what to read and skip the rest. No daily inbox clutter. Just the stories worth your time, once a week.
✦ ✦ ✦
The deeper issue is rarely about time at all. It is about control. Handing off a task means handing off some amount of how it gets done, and for a leader who built something with her own hands, that handoff can feel like a small loss of ownership, even when the outcome improves. There is a real difference between a task done exactly the way you would do it and a task done well by someone else's method. Many leaders have never separated those two ideas, so any difference in method registers as a mistake, even when the result is fine.
This shows up constantly in growing organizations. A founder who built every process alone eventually reaches a size where personal capacity is the actual ceiling on growth, not market demand, not talent, not funding. The organization could take on more work, serve more people, or expand into new areas, except that the one person capable of doing certain tasks the way they have always been done is already fully booked. The ceiling is not the business. The ceiling is one person's calendar.
Every hour spent on a task that belongs to someone else is an hour not spent on the decisions only you can make. Multiplied across months, that hour becomes a real reason growth stalls, not because the organization lacks capacity, but because the leader's own hands stay full of the wrong work. Strategy gets postponed. Relationship building gets postponed. The work that actually requires the leader's unique judgment gets pushed to whatever time is left over after the task that never should have stayed on her desk in the first place.
There is also an emotional cost that rarely gets named. Holding onto a task past the point it should be released often comes with quiet resentment, a sense of being the only one who can be trusted, or the only one willing to do things right. That feeling is uncomfortable to sit with, and it is also usually inaccurate. Most tasks held onto this long are not actually irreplaceable. They are simply undocumented, which makes them feel irreplaceable, even when a clear set of instructions would let almost anyone competent step in.
The shift starts with naming the belief out loud. Not, this task takes too long to teach. Instead, I am afraid of what it will look like when someone else does it their way instead of mine. Once the real reason is on the table, it becomes a decision you can actually work with, instead of a hidden rule running your calendar without your permission. From there, the practical step is small. Write down exactly how the task gets done today, in plain language, the way you would explain it to someone brand new. That single document usually does more to make delegation possible than any amount of willpower.
There is a common excuse that deserves special attention because it sounds so reasonable. No one else can do this the way I need it done. That statement is almost never fully true. What is usually true is that no one else has been shown how it needs to be done, which is a completely different problem with a completely different fix. Confusing the two keeps a leader convinced that a training gap is actually a talent gap, and that mistaken belief can keep a task stuck for years.
It also helps to notice how this pattern tends to travel. A leader who cannot release one task rarely stops there. The same reasoning that keeps a bookkeeping task on her desk often keeps a dozen smaller tasks there as well, each one justified with a slightly different version of the same sentence. Reviewing the calendar honestly, and counting how many of those small tasks add up across a single week, is often the moment a leader finally sees the real scale of what she has been carrying alone.
There is also a difference between delegating a task and abandoning a standard. Many leaders resist delegation because they fear the second one is inevitable once they stop doing something personally. In practice, a clearly written standard travels with the task far better than an undocumented habit ever could. A written standard can be handed to someone new. An unwritten habit that only lives in one person's head cannot be handed to anyone, which is exactly why it stays stuck with that one person indefinitely.
The return on releasing a task well documented is rarely instant, and that delay is part of why leaders underestimate it. The first attempt by someone new is almost always a little slower and a little different than the leader's own version. Leaders who judge delegation by that first attempt often conclude it failed, when in fact it simply has not had time to succeed yet. Judging delegation over a full quarter, rather than a single week, gives a far more accurate picture of whether it is actually working.
There is a specific moment worth watching for, because it tends to decide whether delegation actually succeeds. It is the moment the newly trained person does the task differently than the leader would have, and the result is still acceptable. What a leader does in that exact moment matters enormously. Stepping back in to correct the small difference teaches the new person that her own judgment does not count, and it quietly retrains the leader to keep reaching for the task herself the next time a difference appears. Letting the acceptable result stand, even when it does not match the leader's original method exactly, is what actually completes the handoff.
It is also worth naming the quiet cost this pattern has on the people around a leader who cannot release control. Team members who watch every piece of meaningful work funnel back to one person eventually stop offering to help with it at all. Not because they lack the ability, but because they have learned that offering rarely leads anywhere. A leader who wants a team that steps up has to first prove, through real handoffs that are allowed to stick, that stepping up will actually be honored rather than quietly undone.
Think of one task right now that you know does not require you specifically. Ask yourself honestly whether you are holding it because it truly needs you, or because letting go feels like more work than holding on. Most leaders already know the answer. The harder part is acting on it before another year passes with the same task still sitting in the same place on the same desk.
-- Dr. Rhonda
If a task like this has been sitting on your desk longer than it should, the Decision Impact Clarity Tool can help you see clearly what it is actually costing you to keep it. It is free to use, and it takes only a few minutes.
Add comment
Comments