What I mistook for leadership was actually a ceiling with my name on it.
There was a Tuesday not long ago when I sat staring at my inbox and felt something I did not expect. Not overwhelm. Resentment.
Someone on my team had asked me, again, for what felt like the third time that week, what to do about something I was certain I had already explained. And for one honest, unflattering second, I resented them for needing me that much.
I did not say that out loud. I answered the question, kindly, the way I always did. But driving home that evening, the resentment would not leave me alone. Underneath it was a harder truth than I wanted to look at directly.
They were not the problem. I was.
I had built a team that could not move without me, and some quiet, unexamined part of me had let that happen on purpose. Being needed that much felt like proof that I mattered. If everything ran through me, I was essential. Undeniable. Safe.
Admitting that took longer than I want to admit. For weeks I told myself my team simply needed more training, more clarity, more time. All of that was partly true. But underneath the training gap was a fear I had never said out loud, not even to myself. If I built something that could run without me, what would that actually say about how needed I was?
That question sat with me in a way I could not shake. I noticed how quickly I answered questions I could have redirected. I noticed the small satisfaction I felt every time someone came to me instead of figuring it out themselves. I did not like what I was noticing.
Acknowledging that I was the bottleneck was the easier part, once I finally let myself see it. Actually doing something about it was much harder, because it meant giving up the one thing that had quietly been making me feel indispensable.
For a long time, I told myself I had handed the reins to my team. I had said the words. I had assigned the roles. But nothing moved unless I was in the room to unstick it. Every decision, every approval, every next step still ran through me, no matter how clearly I thought I had delegated it.
I had to face something uncomfortable. Verbally handing over the reins is not the same as actually releasing them. I had never taken the time to document my own processes. I had never built anything my team could follow without me standing beside them explaining it in real time.
So I started doing the unglamorous work, even though part of me still resisted it. I documented what I actually did, step by step. I created short explainer videos so my team could see what the instructions looked like in practice, not just hear them once in a meeting. I set clear boundaries around what they could decide on their own, what needed to be escalated, and what simply needed to be communicated after the fact.
Only then did things actually start moving without me in the room. And if I am honest, there was grief mixed in with the relief. Some part of me missed being needed that much, even as the rest of me finally exhaled.
I share that because I think a lot of leaders are living inside the same gap without a name for it yet.
There is a difference between a leader who is trusted with responsibility and a leader who has quietly become the only person capable of moving anything forward. The first is an honor. The second is a slow erosion, dressed up as commitment.
Some decisions belong on the leader's desk alone. Others require buy-in, and skipping that step does not save time. It spends trust.
Here is the deeper pattern underneath that moment, and it is the same pattern I see sitting across the table from executives every week.
If your organization cannot make a decision, hold a relationship, or carry a responsibility without your direct hand on it, you have not built an organization. You have built a shrine.
A shrine is beautiful. People visit it. People admire it. But nothing grows there. Nothing moves without you standing in the room.
✦ ✦ ✦
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.
✦ ✦ ✦
That realization rarely arrives all at once. It usually starts the same way it did for me. You believe you are describing your team, your workload, your busy season. Then you hear yourself explain why nothing moves without your sign-off, and you realize you are not describing your business. You are describing yourself.
That is not a failure of leadership. It is usually the quiet result of years of being trusted with more and more, without ever stopping to document, structure, or release what no longer needed to sit only with you.
So let me ask you the question underneath this month's pressure question, the one I am asking every executive I sit with right now.
When responsibility lands on your desk, does it arrive as a conversation, or as a foregone conclusion?
If it is the second one, your organization is not being built. It is quietly un-building the very leader holding it together.
The correction is not complicated, but it is not comfortable either. It starts with a decision to keep talking to your team about what they actually want, not just what they are capable of carrying. It starts with training a successor before you need one, not after you are depleted. It starts with asking whether the structure around you can survive your absence, or only your presence.
An organization that can only run through you is not a legacy. It is a ceiling. And most leaders do not build the ceiling on purpose. They build it one unasked question at a time.
-- Dr. Rhonda
The Next Step: If you recognize that quiet resentment of being needed too much, or the fear of what letting go might reveal, take The Close the Leadership Gap Diagnostic™. It is built to help you see whether what you have built is an organization or a shrine, and what to do about it.
Add comment
Comments