The Truth About Building Something That Needs You Forever
Every leader believes their organization would survive without them for a while. Not every leader has actually tested that belief.
There was a stretch of time when I could not be reached. I expected some disruption. What I found instead was that the day-to-day operations of the organization came to a complete stop and stayed stopped until I returned.
That kind of result rarely comes from a lack of capable people. It comes from a structure that was never built to run without one specific person in it. Decisions, information, and authority stay concentrated in a single place, usually without anyone deciding that on purpose. It happens gradually, one exception at a time, until an entire organization quietly depends on one person's availability. No one sits down and designs it that way. It accumulates through a thousand small moments where it was simply faster for the leader to handle something herself than to build the structure that would let someone else handle it instead.
The uncomfortable part is that this dependency can look like strength for a long time. A leader who can be reached for everything, who makes every important call personally, often gets read as deeply committed and highly capable. Board members praise the hands-on approach. Staff appreciate having quick answers. The same pattern that earns praise in year one becomes the exact thing that stops the organization cold in year five, once the organization has grown large enough that no single person can realistically stay involved in everything and still do the job well.
✦ ✦ ✦
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.
✦ ✦ ✦
There is a difference worth drawing out here between a leader being important and an organization being dependent. Every leader should be important to the mission, the culture, and the direction of what she has built. That is not the problem. The problem is when importance and dependency get treated as the same thing, so that the leader's absence does not just create a gap in leadership, it creates a full stop in operations. Those are two very different situations, and only one of them is sustainable.
A useful question is not whether the people around you are capable. Most already are. The real question is whether they have been given authority that matches their capability, or whether every meaningful decision still quietly waits for you to weigh in. Capability without authority does nothing for an organization in a crisis. A team can be full of smart, willing people and still freeze completely if none of them has been given permission to actually decide anything without checking first.
This is worth testing on purpose, rather than discovering by accident the way I did. A planned, short absence, with no email and no calls, will reveal in a matter of days exactly where the real gaps sit. What decisions stalled. What information only lived in one inbox. What questions came up that no one else felt able to answer. That kind of test is far less expensive than finding out the same information during an emergency, an illness, or any other unplanned absence that offers no warning and no control over the timing.
The fix is not becoming less available out of principle, and it is not stepping back from leadership. It is building real decision authority into other people before you are tested by an absence you did not plan for. That means documenting how decisions actually get made, not just what the decisions were. It means giving other people the standing to make calls within a defined scope, not just the instructions to follow when something predictable happens. Authority that only works for predictable situations is not authority. It is a checklist.
An organization that can only move forward with one person in the room is not evidence of that person's importance. It is evidence of a structure that still needs to be built. The good news is that structure can be built deliberately, on your own timeline, rather than being discovered under pressure when the timing is worst.
There is a specific kind of excuse worth naming here, because it sounds like humility but functions like control. It would take longer to explain this decision than to just make it myself. That statement can be true for a single decision on a single day. It is rarely true across a year. Every hour spent explaining a decision once, clearly and completely, is an hour that pays back many times over the next time a similar decision comes up and someone else is able to handle it without involving the leader at all.
It also helps to separate the idea of delegation from the idea of decision authority, because the two get treated as the same thing far too often. Delegating a task means handing off the work. Delegating authority means handing off the right to decide how the work gets done, including the right to make a call the leader might not have made herself. Many organizations delegate tasks freely while quietly withholding authority, which is exactly why decisions still bottleneck at the top even after work has technically been spread across a team.
A leader who wants to test whether real authority has been delegated can ask a simple question of her team. If I were unreachable for two weeks starting today, what decision would you be uncertain you had permission to make. The honest answers to that question usually reveal the true boundary of delegated authority far more accurately than any org chart or job description ever could.
The work of building this kind of structure is rarely glamorous. It looks like writing down a decision that used to live only in the leader's head. It looks like sitting with a team member while they make a call, staying quiet even when their instinct differs slightly from what the leader would have chosen, and letting the decision stand. It looks like resisting the urge to jump back in the moment something looks slightly off, because that urge is often what undoes months of real delegation in a single afternoon.
The work of building this kind of structure is rarely glamorous. It looks like writing down a decision that used to live only in the leader's head. It looks like sitting with a team member while they make a call, staying quiet even when their instinct differs slightly from what the leader would have chosen, and letting the decision stand. It looks like resisting the urge to jump back in the moment something looks slightly off, because that urge is often what undoes months of real delegation in a single afternoon.
There is also a difference in how this looks across the size of an organization. In a very small operation, one person holding most of the decisions can be a reasonable and even efficient stage, as long as it is treated as a stage rather than a permanent design. The trouble comes when growth continues, the number of decisions multiplies, and the structure never catches up. What was efficient at ten people becomes a genuine bottleneck at fifty, and the leader who does not notice the shift keeps running the small operation's playbook inside an organization that has already outgrown it.
A practical starting point is a short list, built honestly, of every decision that currently requires the leader's direct involvement. Not every decision needs to stay on that list forever. Some belong there permanently, tied to the leader's unique judgment or accountability. Others are on the list only out of habit, because no one has ever formally moved them off. Reviewing that list twice a year, and asking which items could move to someone else with the right documentation and authority, keeps the structure honest instead of letting dependency creep back in unnoticed.
None of this diminishes a leader's importance. If anything, it strengthens it. A leader who has built real decision authority into her team is free to focus on the work only she can do, the direction, the relationships, the long view, rather than staying trapped inside the daily operations a well built structure should be able to carry without her constant presence.
-- Dr. Rhonda
The Decision Impact Clarity Tool is a free way to see exactly where decisions in your organization still depend on you alone, before an unplanned absence tests that dependency for you.
Add comment
Comments