She was leaving in five weeks.

The executive director of one of our partner organizations — I'll call her Denise. Fifteen years in. The call was supposed to be a quarterly close-out. Instead she walked us through her handoff list and told us what her doctor had told her:

"Stress is a main factor — you need to calm yourself. But it's a lot of moving points that I need to take care of before my departure."

Fifteen years of catching what fell. Fifteen years of being the one who knew. And the first thing to break wasn't the organization.

That same week, nothing was failing. Programs running. Board happy. A second senior leader was also on her way out, and even then — nothing on any dashboard moved.

The organization didn't look fragile. It looked fine.

It looked fine right up until fifteen years of unwritten knowledge gave five weeks' notice.

I call it organizational fragility. Most leaders know it as one sentence — the one they say half-joking and mean completely:

"If I step away, this whole thing falls apart."

Here's what makes it different from every other pattern I write about.

The others show up in the organization in ways you can point to — loneliness at the top, a team that can't decide without you. They're in your calendar, your inbox, your Sunday nights.

But this one shows up in you.

When it does, you read it as exhaustion. I've lost count of the leaders who've told me some version of what Denise's doctor told her. Slow down. Rest. The stress is doing something to you. Every one of them heard it as a comment on their stamina.

The truth is, stamina is finite. Most EDs have a ton of it. What they don't have is structure.

Fortunately, structure can be built.

The ifs

I've sat with hundreds of nonprofit leaders. When this comes up, they all say it the same way:

"If I took a month off, I honestly don't know what would happen to this organization."

"If I get hit by a bus tomorrow, this whole place stops functioning within a week."

"I've got leaders thinking about retirement. If I or another senior leader left, I'm not sure the organization would hold together."

"My board keeps asking about succession and I don't have a good answer."

Every one of them is an if.

Nobody says "my organization is collapsing," because nothing is. No incident, no fire, no number moving the wrong way. The other issues I write about speak in the present tense.

This one only speaks in hypotheticals.

Until it doesn't.

Why it never feels urgent

You can sense it. Most leaders can. It arrives as a thought on a Sunday — if I disappeared tomorrow, how much of this goes with me? — or as a sentence you almost say to your board and then don't.

But sensing isn't hurting.

Nothing on your calendar changes when you sense it. Nothing escalates. You do a little more of what you've always done, and the thought goes back in the drawer.

The people watching closely see it too. Your directors know which decisions still can't happen without you. Your board knows the organization's story and your story are the same story. They can ask the question. They can insist on a plan. But they cannot build the systems that keep the organization moving when you're not there.

You can.

But there's a reason you haven't — and it's the same reason you're tired.

You get there first.

Every shock that would expose the fragility, you absorb before anyone else feels it. The funder wobble — you caught it. The gap when someone left — you covered it. Your board isn't worried because the reports are calm, and the reports are calm because you write them.

You are your organization's anesthetic.

Anesthesia doesn't take the damage away. It takes away the feeling of it. Your organization feels nothing because you're the one feeling it instead — and the anesthetic is a person, with a body, and a family, and a doctor.

Underneath, three things are usually true at once. Succession was never planned. Your board has no real visibility. The roles were built around a person instead of an organization. Each one covers for the others, and none of them surfaces while you're still in your chair.

So the organization looks strongest exactly where it depends on you most.

No alarm is sounding. That doesn't mean one shouldn't be.

What actually works

If your board has asked about succession, you may already have a plan — an interim, a search committee, a document. It's worth having. But it names who steps in, not what they'd be stepping into. A successor inheriting an organization only you can run inherits the same collapse, with a title. Which means the search isn't for a leader. It's for someone willing to work 100-hour weeks to keep this running the way you always have.

That's a short list.

But it doesn't have to be that way.

When a cardiologist suspects a problem that doesn't show at rest, they don't wait for something bigger to happen. They put the heart under controlled load and watch. Reality won't stress-test your organization until the stakes are too high. So instead of waiting, you run the test first, at a load you choose, while there's still time to fix what it finds.

Then you build for what it shows you. Five moves, in this order.

  1. Map what runs through you. Two columns: what genuinely requires the executive director, and what only routes to you because it always has. Most leaders are shocked by the size of the second column.

    Want an easy start? The Org Fragility Scorecard runs exactly this exercise and scores it — five minutes. Take the Scorecard

  2. Get your DNA out of your head. The processes, the SOPs that make them repeatable, and the training that puts them in your team's hands. What you know how to do has to become what the organization knows how to do.

  1. Build new connective tissue. The fifteen-minute daily standup. The leadership meeting redesigned to carry weight between people instead of routing it through you. Most organizations have meetings. Fragile ones have meetings that only work when you're in them.

  1. Reset the expectation. Nobody brings you a question they could bring you a recommendation for. Your directors own decisions and generate solutions — with you, not from you.

  2. Stay through the repetitions. Not a training. Reps, on real decisions, with someone alongside them, until it holds when you're not in the room.


We call this process, fortification.

What happens on the other side isn't subtle. You feel lighter. The week you take off stays off. And you finally spend your mind on what only your mind can do.

But you're usually not the first to notice.

One executive director I worked with sat down with her biggest funder for the meeting that decides whether the grant renews. She brought every director into the room with her. They presented their own work.

Afterward the program officer told her: your leadership team has grown so much from last year — it's incredible.

Her words to me: "I didn't do their presentations. They did their own thing. I felt very proud of them."

That's the test coming back clean.

Where things go from here

Organizations get built around a person because that person kept them alive. That isn't a personal flaw. It's how it survived long enough to be worth protecting.

But keeping it that way, after seeing where it leads, is a choice.

Three paths:

  1. Decide you don't need to change anything. Things are running, the team is good, and deep down it feels good to be needed the way that you are. My only ask is that you make this choice knowing the tradeoff.

  2. Get to it next quarter. You'll mean it. But something urgent shows up every quarter, and this never does.

  3. Take the first step today.

Where to start

Move one. Today.

Open your calendar and your sent folder for the last two weeks and write down every decision that came to you. Every approval, every question, every save. Then sort them into the two columns: had to be me and ended up being me.

Don't clean it up. The second column is the map.

Then circle the item that would hurt the communities you serve most if it stalled for a month. That's your first handoff — document it this month and give it, with real authority, to a named person on your team. It is their responsibility to deliver. You are there to answer questions. Schedule fifteen or thirty minutes, one on one, with that person each week for the next month, so there's already a set time for them to ask you what they need to know.

Small test. Load you choose. On your schedule instead of life's.

The Org Fragility Scorecard — five minutes, scored. Ten questions about the last two weeks. Take the scorecard and we’ll send you your score, along with a few thoughts on what it means and where to start.

Everything I've been talking about isn't just about your calendar, or your weekends, or even your health — though all of that gets better.

It's about the family three years into your program who shouldn't have to wonder whether the thing that helped them will still be there next March. It's about whether the change you made outlasts the person who made it.

The highest badge of honor isn't an organization that can't survive you.

It's change strong enough to carry forward without you.

That's legacy.

You've carried this well. That's exactly why it's been invisible.

Hit reply and tell me which path you decided to take. I read everything.

— Durell

P.S. — a few things that might help

Start here:

The Org Fragility Scorecard — five minutes, scored. Ten questions about the last two weeks. Take the scorecard and we’ll send you your score, along with a few thoughts on what it means and where to start.

If you want to go further:

Are Your Internal Operations Holding You Back? — a twenty-minute worksheet that widens the exercise above from who decides to how work moves — where it gets stuck, what only happens when you step in, and what it would look like if it didn't.

Book a Clarity Call — thirty private minutes with someone whose only stake is your clarity. We start with what's actually happening and what you've tried; you leave with a sharper read on the structure underneath it.

Book worth your time: Michael Gerber's The E-Myth Revisited. It's about small business, not nonprofits, and it's still the clearest thing ever written on why what you built shouldn't require you to run it.

More next month.

Reply

Avatar

or to participate