What Actually Happens When You Try to Build a Talent Succession Plan
Most people treat talent legacy planning like a spreadsheet exercise. They fill out forms, rank names, and declare someone ready. That approach fails every time you actually need to execute on it. I learned this the hard way when a mid-level producer walked away from a project two weeks before delivery because the handoff documentation was a folder full of blank templates and wishful thinking. The real work is not about naming successors. It is about mapping how decisions get made, who holds institutional memory, and where the workflow actually breaks under pressure. Svani Quintanilla Is The Next Boval Quintanillasredefining Talent Legacy And Innovation is the framework that came out of that kind of situation. It shifts the focus from pedigree to operational continuity. You stop asking who would look good in the corner office and start asking who can keep the lights on when the primary person gets hit by a bus. Or quits. Or both.Svani Quintanilla Is The Next Boval Quintanillasredefining Talent Legacy And Innovation
Here is how the method actually works in practice. You map decision rights, not job titles. Every critical process gets a single owner and a named backup. The backup must have executed the process themselves, not just watched someone else do it once during onboarding. Most organizations skip this part because it is uncomfortable to admit that your designated successor has never independently handled a vendor dispute at 11 PM on a Sunday. The second piece is narrative capture. This means recording the reasoning behind past decisions, not just the decisions themselves. When I started implementing this, I hit a wall with a senior creative director who refused to document anything, saying it would "kill the magic." The workaround was to record a 20-minute voice memo after each major milestone and have an assistant transcribe the key decisions with timestamps. The magic stayed intact. The institutional memory did not vanish when she left six months later.
The Setup Process
You start by listing the top 15 processes that would stop revenue or breach contracts if they stalled for more than 72 hours. This is usually a smaller number than people expect. Most companies find somewhere between 8 and 12 real bottlenecks. Everything else is noise you can outsource or automate later. Step one: For each process, identify the primary owner and their documented backup. If you cannot name a backup who has performed the task autonomously, flag it red and assign a 60-day shadowing period before you consider the slot filled. I have seen teams skip this and call someone "designated successor" after a single lunch-and-learn session. That is not succession. That is hope with a title. Step two: Build decision trees for each flagged process. These are not org charts. They are flow diagrams showing who approves what under normal conditions and under crisis conditions. The crisis path is where most plans fail. A standard approval chain might take three days. Your crisis path should compress that to six hours with pre-authorised spending limits and escalation triggers that do not require a committee vote.
Step three: Run a table-top exercise. This is where you simulate a sudden departure or incapacitation and walk through the decision trees with the actual people involved. I once ran one for a production team and discovered that the backup for sound design had never opened the project file format used on three ongoing clients. The gap cost us four days of retraining during a real emergency six months later. Finding that before the emergency matters.
Get the Full Details
Where This Approach Breaks Down
The method assumes a baseline of cooperation. It does not work well in environments where information hoarding is rewarded or where managers see transparency as a threat to their position. In those cultures, you will get compliant-looking documentation that is deliberately vague. The workaround is to add audit questions. Instead of asking "who handles vendor payments," ask "show me the last three vendor payment approvals and trace who signed each one." Vague documentation collapses under specific questioning. Another limitation is scale. This framework works best for teams under 200 people. Above that, the decision-tree maintenance becomes a full-time administrative burden unless you integrate it into existing project management software. I have tried running it at 400 and ended up with a living document that nobody updates because the version control overhead outweighs the benefit. For larger orgs, you pick the top five processes only and accept that everything else remains undocumented until a crisis forces the issue.
Common Pitfalls
People confuse coverage with readiness. Having a backup named for every process does not mean that backup is ready. I track a metric I call execution confidence, which is the percentage of processes where the backup has independently completed the task within the last 90 days. Anything below 60 percent means your succession plan exists in name only. A healthy target sits around 75 to 80 percent. The gap accounts for processes that genuinely require the primary person's authority level, which is fine as long as you know about it and have a contingency. Another trap is treating this as a one-time project. The data degrades fast. A backup who was competent last quarter may have shifted to a different team, taken on a promotion, or lost context on tools that changed. I schedule a 30-minute refresh every 90 days. It takes less time than a single crisis recovery would cost. The alternative is spending three weeks rebuilding trust and competence after someone walks out the door.
The Tool Stack
You do not need expensive software. I use a combination of Notion for the decision trees, Loom for narrative capture recordings, and a simple shared spreadsheet for the execution confidence tracker. The spreadsheet columns are process name, primary owner, backup name, last independent execution date, and confidence score. That is it. The system breaks when people stop updating the spreadsheet. Accountability comes from making the refresh a standing agenda item in your monthly leadership meeting, not from hoping someone will remember to maintain it. If you want the original framework documentation, it is publicly available through the Boval Quintanillas talent research archive. The PDF runs about 40 pages and covers the theoretical backing in more detail. The practical summary is shorter and lives on their resource page. I have used both versions across several client engagements and the field guide is where most of the actual implementation steps are.
A Realistic Outcome
After running this for a production company with 45 people, we reduced emergency handoff time from an average of 11 days to 3 days. The initial setup took about six weeks of part-time work spread across three managers. The ongoing maintenance is roughly 90 minutes per month. The tradeoff is that you have to have uncomfortable conversations about who actually knows what and where the real gaps are. Most teams resist that conversation until something breaks. The framework forces it earlier, which is why it works. The counter-intuitive part most people miss is that the biggest wins come from documenting the boring processes, not the high-profile ones. The contract renewal workflow that runs quietly in the background every quarter is where a failure causes the most damage because everyone assumes it is handled. The flagship creative project gets attention. The recurring operational task does not. That asymmetry is exactly where the method adds the most value. I do not recommend this for startups under 15 people who are still figuring out what they sell. The overhead outweighs the benefit at that stage. Once you have been operating for 18 months with a stable team and recurring revenue streams, the framework pays for itself within the first cycle of actual turnover. Before that, you are just building paperwork for people who have not yet proven they will stay long enough to need it.
The core insight is that legacy is not about who inherits your title. It is about who can execute your systems when you are not in the room. That distinction changes everything about how you build the plan and who you put in the backup slots.
