Most operations leaders wait until a departure is imminent before thinking about who comes next. By then, the window to develop a capable successor has already closed.
Ask most operations leaders when they last formally reviewed who would step into their role if they were unavailable tomorrow — not eventually, not in theory, but with enough operational grounding to actually function — and the honest answer is usually: never.
The delay isn't irresponsibility. It's a rational response to short-term incentives. Building a successor takes 12 to 24 months of sustained effort, requires sharing authority and decision-making while the COO still holds the role, and delivers no visible return until the moment of transition. Until that moment arrives, the development investment competes with dozens of more immediate operational priorities — and loses.
The result is a predictable pattern: succession planning becomes urgent at exactly the moment it's hardest. A founder announces they're stepping back. A COO accepts another opportunity. A health situation forces an accelerated transition. In each case, the question "who steps into this role?" is answered by whoever is available rather than whoever is ready. The operational continuity the business needs is replaced by an improvised handoff.
The good news is that succession planning for operations isn't a complex program — it's a 12 to 24 month development arc with a small number of concrete milestones. The organizations that execute it well don't treat it as a special initiative; they treat it as a standing operational priority in the same category as process documentation and ownership coverage. Like those disciplines, it compounds over time — and its absence only becomes visible when it's too late to act on it.
These two concepts are often conflated — but they address different problems and require different responses.
Key person risk is a defensive posture: identifying where operational knowledge is concentrated in a single individual and building redundancy so the organization can function if that person is unexpectedly unavailable. Key person risk management asks: what happens if this person is hit by a bus tomorrow? The answer is a set of mitigation actions — documentation, cross-training, backup ownership assignments — that reduce the concentration without necessarily developing any specific individual into a leadership successor.
Succession planning is a proactive posture: identifying and developing a specific individual who can step into a leadership role with the strategic judgment, operational ownership, and organizational relationships required to be effective. Succession planning asks: who should run this function in 18 months, and what do they need to get there? The answer is a development arc — specific responsibilities, decision authority, knowledge transfer, and visibility that prepares one named person to assume a named role.
The confusion matters because organizations that stop at key person risk management believe they've addressed succession. They haven't. They've reduced the cost of an unexpected departure; they haven't built the capability to sustain leadership continuity. An organization that has documented every COO process but has no identified successor still faces a leadership vacuum the moment the COO exits. The documentation reduces the recovery time — it doesn't prevent the gap.
Effective succession planning incorporates key person risk management as a subset. The documentation and cross-training that reduce key person risk are also the foundation of operational knowledge transfer to a successor. But succession planning goes further: it adds individual development, deliberate exposure to strategic decisions, and a timeline with milestones that tracks the successor's readiness against a specific transition horizon.
The most common mistake in identifying a successor is optimizing for current performance in the wrong domain. The best individual contributor on the operations team, the person who manages their area with the fewest escalations, the one who consistently hits their metrics — these are signals of execution capability at the current level. They are weak predictors of leadership effectiveness at the next level.
The qualities that predict success in a COO or senior operations leadership role are different in kind from the qualities that predict success as a team lead or senior individual contributor:
The assessment process for these qualities needs to create genuine test conditions, not simulated ones. The best evidence that someone has the right qualities is observing them exercise those qualities in real situations with real stakes — not in hypothetical scenarios or 360 surveys.
Once the successor is identified, the development arc follows a deliberate sequence. The timeline depends on the successor's current level and the complexity of the role — a senior team lead who already has broad operational exposure might be ready in 12 months; a high-potential individual contributor might need 24. The structure, however, is similar.
Months 1–4: Expanded ownership. Extend the successor's responsibility into areas of the operation they don't currently own. Not as a project lead — as an accountable owner with full decision rights. The goal is to create genuine skin-in-the-game exposure to problems they haven't previously had to solve. The COO should meet with the successor weekly during this phase, not to manage their decisions but to discuss the reasoning behind them. This is where judgment development happens fastest — in real-time conversation about real decisions, not retrospective coaching.
Months 5–10: Strategic exposure. Begin including the successor in the leadership forums the COO attends: board updates, CEO operating cadence conversations, cross-functional planning sessions. Initially as an observer; gradually as a contributor. The goal in this phase is for the successor to develop the organizational relationships and strategic context that the COO currently holds — knowledge that can't be transferred through documentation, only through direct exposure over time.
Months 11–18: Acting authority. Create structured opportunities for the successor to function in the COO role in bounded contexts — leading a cross-functional initiative end-to-end, representing operations in an external forum, managing a significant operational crisis with the COO in an advisory rather than decision-making capacity. The feedback loop in this phase should be explicit: after each acting-authority experience, the COO and successor debrief specifically on what worked, what the successor would do differently, and what gaps remain. This converts experience into calibrated learning.
Months 18–24: Transition preparation. The final phase focuses on the institutional knowledge transfer that only happens at the end of the arc: the relationships, the undocumented context behind key decisions, the political dynamics in the organization that aren't visible from outside the COO role. This is also when the successor should begin building their own relationships with the CEO, board members, and key external stakeholders independently — not as the COO's proxy, but as someone the organization is learning to trust in their own right.
Operational knowledge transfer is the piece of succession planning most organizations underinvest in — and the piece that determines whether the transition is smooth or disruptive. It falls into two categories that require different transfer approaches.
Structured operational knowledge — the documented processes, task ownership records, vendor and partner relationships, compliance obligations, and decision frameworks that govern how the operation runs — is transferable through the operational system. If this knowledge exists in a structured, queryable form, a successor can access it directly: which tasks are owned by whom, which recurring obligations exist and when they're due, what documents are in place, where the process documentation lives. A successor inheriting a well-structured operational record has a running start; one inheriting a collection of personal files, email threads, and institutional memory locked in the departing COO's head has months of archaeology ahead of them.
This is where the investment in cross-training and knowledge documentation pays a direct succession dividend. The same structured operational data that reduces key person risk across the operations team also gives the successor a comprehensive view of the function they're inheriting. The better the operational record, the shorter the effective transition window needs to be.
Tacit operational knowledge — the judgment calls, relationship context, and undocumented history that inform how the COO makes decisions — is only transferable through time and direct exposure. No document captures why a particular vendor relationship requires specific handling, or which board member is likely to push back on a particular initiative, or which historical decisions constrain current options. This knowledge transfers through the strategic exposure and acting-authority phases of the development arc — through hundreds of small observations, conversations, and decisions over 12 to 24 months.
The implication is significant: succession planning that begins when a departure is announced has already forfeited the only window in which tacit knowledge transfer can happen. Structural knowledge can be transferred quickly when documentation is in place. Tacit knowledge can't be accelerated. It requires the time it requires.
Succession planning that only exists in the COO's head is fragile — it can be reversed or deprioritized under pressure without accountability. Making it visible to the CEO and, where appropriate, the board transforms it from a personal commitment into an organizational process with stakeholders who track it.
The CEO needs to know three things: who the designated successor is, what the development arc looks like, and where the successor currently stands against the milestones. A quarterly update — five minutes in the COO's standing CEO check-in — is usually sufficient. The goal isn't to create a formal review process; it's to establish that the succession plan exists as an organizational fact, not a private intention.
For companies with a board, succession planning for the COO role is a governance topic that most boards appreciate surfacing. A brief annual update — "here's our succession plan for the operations leadership role, here's the current state of the development arc, and here's our assessment of timeline to readiness" — is appropriate in a board session that covers organizational health. It signals operational maturity and reduces the board's concern about key-person concentration at the leadership level.
The operational records that Sintris structures — task ownership, process documentation, decision history, compliance coverage — are the foundation of everything the C-suite and board need to evaluate succession readiness. When that record is current and comprehensive, a successor's onboarding is a structured handoff rather than a reconstruction project. When it isn't, the transition cost falls on the successor, the team, and ultimately the business.
You can see how Sintris structures operational knowledge to support transitions, explore what it costs, or learn more about the company if you're evaluating how to build a more transferable operation.
More from the Sintris blog.
Every operations team has them: the one person who knows how the invoicing system really works, or who owns the vendor relationship no one else understands. Here's how to find them — and fix them.
Key person risk identifies who holds critical knowledge. Cross-training builds the skill coverage that makes their departure manageable. Here's the COO's playbook for a cross-training program that produces genuine redundancy, not just documentation.
Once the discovery window closes, a COO's priorities shift from building to maintaining: sustaining visibility, protecting review cadences, managing risk continuously, and connecting day-to-day execution to strategic direction.
New on operational intelligence, knowledge, and risk — Monday, Wednesday, and Friday.
