Succession planning nobody owned
She'd been VP of Engineering for three years. When she gave notice, the company realized nobody else could do the job. The 30-day handoff was a fiction.
A VP of Engineering at a series-B company gave notice on a Tuesday. She was leaving for a larger company, with thirty days of notice and an offer to support the transition. Within 24 hours the CTO realized the company had no internal candidate to replace her, no external pipeline started, and no documented understanding of which of her responsibilities were institutional versus personal. The thirty-day notice would not be enough. The company went into a leadership scramble that ran four months and produced an external hire who took another four months to ramp.
The total cost was eight months of degraded engineering leadership, two senior engineers who resigned during the interregnum, and a roadmap delay that became visible in the next board meeting. The departing VP had given the company every reasonable courtesy. The company had failed to be ready, not because of anything she did, but because nobody had been responsible for the readiness.
Succession planning is the leadership discipline that exists in HR documents at large companies and almost never exists at growth-stage ones. The reasons are predictable. The company is small enough that everyone knows everyone, so the absence of a formal plan feels manageable. The senior leaders are visibly present and engaged, so the question of who would replace them feels theoretical. The HR function is too small to drive the discipline. Nobody has it on their quarterly goals. The plan accumulates as an unwritten expectation that we would figure it out if anyone left. The figuring-out, when required, turns out to take eight months and cost two senior engineers.
The minimum viable succession discipline is small and sustained. For every role above director, the leadership team names two internal candidates who could take the role within six to twelve months, with active development. The list is reviewed quarterly. The candidates are told they are on the list — secrecy defeats the purpose, because the development requires conversation. The candidates work with their managers and the role's current occupant on specific gaps that need closing, which means handing them real scope to grow into rather than dumping tasks and calling it development. Some of the candidates leave; some take the development and grow into the readiness; some remain on the list for years without the role ever opening.
The most common objection is political. Naming a successor implies the current incumbent is replaceable, which creates tension with the incumbent. The right framing is that every incumbent is replaceable — not as a slight, but as the structural reality of organizations. Pretending otherwise is the failure mode, not the planning.
The retention benefit is the underweighted side of this discipline. Being named as a successor to a senior role is one of the strongest career signals an employee can receive. It communicates that the company sees them, has a future for them, and is investing in their development. The signal often retains the employee for years longer than they would have stayed without it, which makes succession one of the quieter tools for engaging and retaining your best people.
The external version of the plan is keeping a passive pipeline. For each senior role, the founder or the head of people maintains a relationship with two or three external operators who could plausibly take the role. A coffee every six months. A note when something relevant comes up. When the role opens unexpectedly, the pipeline exists. The four-month external search becomes a two-week conversation.
The notice your VP gave you was the warning you didn't think you needed. Build the plan now, for every role above director, before the next notice arrives.