What happens when an entire organization has run through one person for too long.
For years, I served as business manager for a nonprofit organization, and nearly every financial decision, every transaction, every piece of operational judgment ran through my hands. I did not fully register how disproportionate that workload had become until the day I had to sit down and actually document every part of what I had been doing.
Seeing it written out, in full, was its own kind of quiet shock. I had absorbed years of responsibility that had never been formally distributed. I had simply kept saying yes, kept being capable, kept being the answer, until the answer had quietly become the entire operating structure of the organization.
I want to describe how that felt from the inside, because from the outside, it likely looked like competence, maybe even like generosity. I was the one who knew where everything lived. The passwords. The vendor relationships. The particular quirks of the accounting software that no one else had patience to learn. Every time someone needed something, I was faster than teaching them to find it themselves. Every time a decision needed to be made quickly, I already had the context loaded, ready to go.
I liked being that person, if I am honest. There was a specific comfort in being indispensable, a comfort I did not examine closely enough at the time to notice how much weight it was quietly asking me to carry alone, indefinitely, with no plan for what would happen if I ever needed to set it down.
Looking back, I can name the specific moments where I could have distributed some of that weight earlier and chose, instead, to simply absorb it myself. A board member once offered to learn the accounting system alongside me, genuinely offered, with real willingness. I said yes in the moment and then never actually followed through on the training, because it was easier, that particular week, to just handle the task myself than to slow down and teach it properly. That happened more than once. Each time felt reasonable in isolation. Together, they built the exact fragility that would later take a full year to unwind.
✦ ✦ ✦
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.
✦ ✦ ✦
Then I had to move, permanently, halfway across the country. The decision itself was not about the organization at all. It was personal, necessary, not something I could delay or restructure around. But the moment it became real, I remember sitting with a kind of dread I had not anticipated, not dread about the move itself, dread about what leaving would actually require of everyone left behind.
What followed was not a simple handoff. It took an entire year to train four separate people on everything I had been carrying alone. Four people, one full year, to replace what one person had been holding by herself for far longer than anyone had realized, myself included.
I remember specific moments during that year that stayed with me. A board member, midway through a training session, asking, almost involuntarily, how I had been doing all of this by myself for so long, the question landing less like curiosity and more like quiet alarm. I did not have a satisfying answer. I had simply never stopped to ask myself the same question.
There was mutual regret on all sides once the scope became visible. No one, myself included, had anticipated the day I would no longer be there to serve in that capacity. No one had spoken up soon enough about what the arrangement actually cost, in risk, in fragility, in how little margin existed if anything had ever happened to me sooner, without a year of runway to prepare for it.
I do not think anyone involved acted in bad faith. I think competence and willingness, mine included, created a structure so convenient that no one questioned whether it was sustainable until sustainability was no longer optional. It is easier, in the moment, to let the capable person keep carrying the load than to interrupt that convenience by asking what happens when she cannot anymore. I understand that instinct. I benefited from it too, in the sense that being needed completely fed something in me I had not fully named.
When every decision stops at one source, succession planning becomes arduous, and the growth of the entire organization quietly stalls long before anyone names the reason why.
I think about that year of training often now, whenever I meet a leader who prides herself on being the one who holds everything together. I recognize the particular pride in it, because I felt it myself for years before I understood what it was actually costing the organization around me. Being the answer to every question feels like strength. It is only in the scramble to replace that answer that its actual fragility becomes visible to everyone, including the person who has been carrying it.
I do not regret the years I spent in that role, or the competence I built during them. What I would do differently, if I could go back, is start documenting far earlier than the year I was forced to by circumstance. Not because I expected to leave. Precisely because I did not expect it, and neither does anyone else, until the day arrives without warning and the organization discovers, all at once, exactly how much weight had quietly been resting on one person's shoulders.
Here is the question I now ask early in every engagement with a leader who prides herself on being capable and willing. If you left tomorrow, permanently, with no notice, how long would it take to replace what you currently hold alone? If the honest answer is longer than a few weeks, you are not looking at a compliment to your competence. You are looking at a risk to everything you have built, quietly waiting for the day it finally comes due, whether or not you ever choose to look at it directly before then.
I did not choose fragility on purpose. I simply chose convenience, repeatedly, without ever adding up what the repetition was quietly building. That is, I think, how most unsustainable structures actually get built. Not through one bad decision, but through many reasonable ones, each easier in isolation than the alternative, none of them examined for what they were accumulating into over time.
The four people who eventually replaced me were not less capable than I was. They simply had not been given the years I had, the accumulated context built session by session, decision by decision, over a long enough stretch that the knowledge had become second nature to me and entirely foreign to them. Watching them absorb in twelve months what I had built over years reminded me how much of what feels like individual talent is often simply accumulated familiarity, the kind that looks like magic to everyone who has not yet had the time to build it themselves.
I keep a version of that lesson close now in every organization I advise. Capability that cannot be transferred is not actually an asset to the organization. It is a liability wearing the costume of one, indistinguishable from strength until the exact moment it is tested.
-- Dr. Rhonda
The Next Step: If you suspect your organization is more dependent on you personally than it should be, take The Close the Leadership Gap Diagnostic™. It is built to help you see exactly where succession is missing before circumstance forces the question.
Add comment
Comments