The CEO’s Job Is Not to Carry the Organization
There’s a moment that happens in almost every organization I work with, usually within the first conversation. I ask the CEO or executive director what’s keeping them up at night, and the answer — phrased a dozen different ways — always boils down to the same thing: if I’m not holding this together, it falls apart.
I understand the instinct. You built this. You’ve shouldered the crises, made the calls no one else wanted to make, and kept the organization moving when funding fell through, when a key staff member left, when the board wavered. Carrying the weight has probably worked, in the sense that the organization is still standing.
But here’s what I need to say clearly: your job is not to carry the organization. Your job is to build an organization that doesn’t need to be carried.
Those are radically different jobs. And the leaders who confuse them eventually become the ceiling their organization can’t grow past.
Carrying vs. Building
A leader who carries the organization is the answer to every hard question, the final approver on every decision, the person whose absence creates visible panic. It feels indispensable. It often is indispensable — and that’s precisely the problem.
A leader who builds the organization does something different: they create systems, develop people, and design structures so that good decisions can be made without their direct involvement in every one of them. Their value isn’t measured by how much they personally hold up. It’s measured by how much capacity they’ve built into everyone and everything around them.
I see this distinction most clearly in moments of crisis. In carrying-style organizations, a crisis means the CEO drops everything and personally manages the fire. In building-style organizations, a crisis activates a team that already knows what to do, because the CEO already built the muscle for it.
One of these is a leadership style. The other is a liability waiting to mature.
Why Carrying Feels Like Leadership (And Isn’t)
Carrying the organization feels like leadership because it’s active, visible, and immediately gratifying. You solve the problem. You make the call. You’re the hero of the story, again.
But ask yourself what it’s actually building. Every time you personally absorb a problem that a developing leader on your team could have handled, you are quietly teaching your organization two things: that problems are your job, and that your team’s judgment isn’t trusted enough to be tested.
This is how key-person dependency forms — not through one dramatic moment, but through a thousand small instances where carrying it yourself was faster than developing someone else to carry it. The math feels right in the moment. It’s catastrophic in aggregate.
Nonprofits are especially vulnerable to this pattern because mission urgency makes “I’ll just handle it” feel virtuous. Government leaders feel it through the pressure of public accountability — when something goes wrong publicly, the instinct to personally control every outcome intensifies. Small and mid-size business owners feel it because, often, they genuinely were the only person who could do it all — once. The problem is that “once” became “permanently,” long after the organization outgrew the need for it.
What Building Actually Requires
Shifting from carrying to building isn’t a mindset change you can simply decide to have. It requires structural work.
Decide what only you should decide. Most CEOs have never actually drawn this line. Everything defaults to them because no one has explicitly said otherwise. Get specific: what decisions genuinely require your judgment — strategic direction, major risk, key external relationships — and what decisions are being routed to you out of habit, not necessity?
Build decision-making capacity, not just task capacity. It’s not enough to delegate tasks. You have to develop the judgment behind decisions — which means investing time in coaching your leadership team through how you think about problems, not just handing them solutions. This is slower in the short term and exponentially faster in the long term.
Tolerate the discomfort of imperfect decisions made without you. This is the hardest part. Building leadership capacity means allowing your team to make decisions that aren’t exactly what you would have done — and resisting the urge to override them every time. If every decision gets corrected back to your preference, you haven’t built anything. You’ve just added a delay to your own decision-making.
Measure your success by what happens in your absence. The truest test of whether you’re carrying or building is what occurs when you’re out for two weeks. If the organization stalls, you’ve built a dependency. If it functions — not perfectly, but functionally — you’ve built capacity.
The Real Risk of Staying in Carry Mode
Every organization eventually faces a moment where the carrying leader is gone — by choice, by health, by retirement, or by something unplanned. Organizations that have never built beyond their CEO face that moment in crisis. Organizations that have built real leadership depth face it in transition.
The difference between those two outcomes isn’t talent. It’s whether the leader spent their tenure carrying the weight personally, or building the structures and people who could share it.
If your organization’s stability is still tied directly to your personal bandwidth, that’s not a sign of strong leadership — it’s a sign of unfinished leadership infrastructure. At Thompson Impact Consulting, we help CEOs and executive leaders across nonprofits, government, and growing businesses build the leadership pipelines, decision frameworks, and succession structures that let an organization stand on its own — so your leadership becomes a multiplier, not a single point of failure. If you’re ready to stop carrying and start building, let’s talk.