Succession Is Not an Event. It Is a Design.

There's a question I ask leaders early in our work together: if you were out for three months, what would stall?

The answer is rarely the answer. The silence before it is.

Most leaders can eventually produce a reassuring list — capable people, documented processes, a board with a plan on file. But the pause tells the truth: a mental walk through all the decisions that currently route through one office, all the relationships held by one person, all the judgment calls nobody else has been allowed to practice.

That pause is the real succession problem. Not the vacancy that might come someday. The dependence that exists right now.

The research on this is sobering where it's been studied best. Cornell's family business center reports that only about three in ten family firms survive into the second generation, and barely one in ten makes it to the third. In the cooperative world, the numbers take a different shape — a long wave of general manager and senior-staff retirements — but the underlying exposure is the same: organizations built, often lovingly, around the judgment of a few irreplaceable people.

Here's what I've noticed about how succession usually gets handled. It's treated as an event to be planned — a document, a date, a name in an envelope. And the document may be perfectly good. But while the plan sits in the drawer, the daily design of the organization keeps teaching everyone the opposite lesson: bring it to the corner office. Wait for the founder. The GM decides.

You can't name a successor into an organization built to need you. The role will swallow whoever steps into it, or the organization will keep reaching past them to wherever the judgment used to live.

Which is why I've come to believe succession isn't really an event at all. It's a design question, and it's answered in the present tense. Where do decisions actually happen today? Who holds real authority, not just responsibility? What can this team carry — genuinely carry, with the power to act — when you're not in the room?

David Marquet, the submarine captain turned leadership writer, describes the shift as moving authority to where the information lives. I'd put it this way: you don't prepare a successor. You prepare an organization. A successor inherits whatever design you leave behind — either an organization that knows how to think, decide, and act, or one that knows how to wait.

The design work is unglamorous and available immediately. Hand over whole decisions, not tasks — the question, the authority, the deadline, and the aftermath, with your name nowhere on it. Let your team run a quarter-close or a board prep without you, and pay attention to what stalls, because what stalls is the syllabus. Make the three-month question an annual habit rather than a hypothetical, and treat every item on the stall list as this year's development plan.

And if you sit on a board: ask the question of your organization's relationship with its chief executive. A board that gets nervous even asking it hasn't found an HR gap. It has found a governance finding — evidence that the organization's continuity currently rests on one person's health, energy, and tenure, which is precisely the risk boards exist to see.

None of this diminishes the leader at the center. The founders and long-tenured GMs I know built something worth succeeding — that's the whole point. The final act of building it is making sure it doesn't need you.

Succession isn't an event you schedule.

It's a design you're already living in.

The plan in the drawer matters far less than the question in the room: what would stall — and what are we doing about that this year, while there's still time to do it well?