Most succession plans are documents, not capabilities. They exist to satisfy a board, a regulator, an investor, or a family's own anxiety about continuity, and they are almost never tested until the person they name is suddenly, actually gone. At that point the document either reveals itself as a real transfer of authority or as a piece of paper that assumed the wrong thing was hard to replace.
Consider a hypothetical organization — a mid-sized firm, a family business, a government agency, the specific form does not matter — that names a deputy as successor to its founder or director. The plan is reviewed annually, discussed at board meetings, filed with whatever regulator requires it. On paper the organization looks prepared. What the plan usually does not capture is where the actual judgment lives: which relationships only the departing person can activate, which decisions were never formally delegated because delegating them felt unnecessary while the person was still there, which informal knowledge about clients, staff, or political terrain exists only in one head.
The Document and the Capability
A succession plan names a person. It rarely transfers the thing that made the departing person effective, because that thing is usually not a title or a set of written responsibilities. It is accumulated judgment about which risks to take, which relationships to trust, which shortcuts are safe and which are not — knowledge built through repetition, not documented through policy. An organization can satisfy every formal requirement of succession planning — a named successor, an org chart update, a transition timeline — while the actual capability to run the institution the way it has been run remains concentrated in one person until the day that person leaves.
This is why succession planning functions, in most organizations, primarily as a reassurance artifact rather than an operational one. It answers an external question — is there a plan? — without answering the internal one — does authority and knowledge already exist somewhere other than in the departing person's head? The two questions look similar and are treated as the same by most governance frameworks, but they produce entirely different outcomes when tested.
What the Plan Assumes
Every succession plan carries a hidden assumption: that the context surrounding the departure will resemble the context the plan was written in. It assumes an orderly transition, adequate notice, a cooperative outgoing leader willing to transfer knowledge deliberately over months. Departures that actually stress-test succession plans are rarely this considerate — sudden illness, abrupt resignation, scandal, death, a hostile removal. In these scenarios the plan's careful handoff assumptions collapse at once, and what remains is whatever authority and knowledge had already been distributed before the emergency, not what the document promised would be distributed after it.
The named successor in an untested plan often discovers, at the moment of transition, that being named was not the same as being prepared. Relationships the predecessor held personally do not transfer with the title. Judgment calls the predecessor made instinctively, based on years of pattern recognition, cannot be inherited from a memo. The successor inherits the position and has to build the capability in real time, under pressure, in front of an organization that expected continuity and instead experiences a gap.
Testing Readiness
The only reliable way to know whether a succession plan is real is to remove the named person for a defined period, under normal conditions, and observe what breaks. Not what the plan says should happen — what actually happens when the deputy has to make a judgment call the founder would ordinarily have made, when a client or partner insists on speaking to the person who is not there, when a decision surfaces that the organization's informal culture has always routed to one office. If the organization functions smoothly without the named leader for that period, the plan is describing something real. If it does not, the plan is describing an intention the organization has not yet acted on.
This test is rarely run voluntarily, because running it requires admitting, in advance, that the current concentration of authority is a vulnerability rather than a strength. Organizations built around a strong central figure tend to resist this admission precisely because the figure's centrality is also what makes the organization effective in ordinary times. The same concentration that produces speed and coherence day to day produces fragility at the moment of transition. Institutions rarely choose to weaken their most effective structure in the name of a contingency that has not happened yet.
What this means in practice is that succession readiness is not a document you write once and file. It is a continuous redistribution of authority and knowledge that has to happen while the person being succeeded is still present and still, in some sense, giving something up by allowing it. Most organizations do not do this, not because they have not thought of it, but because doing it costs something in the present — slower decisions, more people in the room, less deference to a single point of judgment — in exchange for a benefit that only materializes if and when the emergency actually arrives.
A succession plan is only as real as the authority already distributed before it is needed. Everything else is paperwork waiting for a crisis to expose it.
Discussion