Succession Planning When You Only Have Eleven Senior People

Succession planning has an enterprise reputation: nine-box grids, talent review cycles, a deck for the board. Companies with a few dozen leaders look at that and reasonably conclude it is not for them. So they do nothing, and then a key departure costs them two quarters.

The lightweight version is genuinely light. It requires one afternoon a quarter and answers three questions.

Question one: which roles would actually hurt?

Not the org chart. The specific seats where an unplanned exit would create material damage within thirty days. In most mid-sized firms there are between four and eight, and at least two of them are not on the leadership team. The person who holds the customer relationships, the engineer who understands the legacy system, the controller who knows why the reconciliation works.

Name them explicitly. Half the value of the exercise is the surprise on that list.

Question two: what happens Monday morning?

For each critical seat, write down two things: who covers immediately, and what they would need on day one. Access, context, relationships, documentation. This is a continuity plan rather than a succession plan, and it is the part that most often prevents actual damage.

If the answer to "who covers" is a name that appears in four different seats, you have found your real risk and it is concentration, not vacancy.

The question is not whether you have a successor. It is whether the work survives ninety days without the incumbent.

Question three: who is two years away, and from what?

For each critical seat, identify anyone who could plausibly hold it in twenty-four months, and name the specific gap. Not a vague development area — a concrete missing experience. Has never managed a P&L. Has never presented to the board. Has never hired a team from scratch.

Then close one gap per person per year with a real assignment. That is the entire development program, and it works better than most formal ones because the gap was identified against a specific seat.

Keep the honest version private and the developmental version public

You cannot promise a role to someone who may not get it, and vague hints do more harm than silence. But you can say the useful part out loud: we think you could hold a much larger scope, here are the two experiences you are missing, and we are going to give you one of them this year.

That conversation is motivating whether or not the succession ever happens, and it does not commit the company to anything it may not be able to deliver.

Review it when reality changes

Refresh the list when someone leaves, when the business shifts materially, or twice a year by default. Most updates take twenty minutes. The point is not the document. The point is that a small group of leaders has said out loud, recently, where the organization is fragile — and has done one concrete thing about it.