OUTDATED PLANS, LOST KNOWLEDGE, AND THE OPERATIONAL DEPT NOBODY WANTS TO TALK ABOUT
There's a kind of risk that most organizations already know they have, and most of them are doing very little about it.
The continuity plan that was comprehensive when it was written three years ago but hasn't been touched since the last reorganization. The runbook that documents a process that no longer exists in that form. The recovery procedure that depends on calling John, who left the company two years ago.
These aren't exotic risks. They come with the quiet accumulation of the operational debt that builds up when documentation doesn't keep pace with how the organization actually works. And like any form of debt, it's manageable when it's small and genuinely dangerous when it's large.
Scott Wilson, who leads 2Oaks Consulting's Business Resiliency practice, has spent more than 30 years watching organizations reach for their continuity plans during a real incident and discover what they actually have.
TLDR; Key Takeaways
Outdated continuity plans and runbooks are a form of operational debt that accumulates quietly and becomes critical at the worst possible moment.
The "tribal knowledge" problem (critical knowledge held by individuals rather than documented in systems) is one of the most common and most costly business continuity failures.
Organizations frequently waste significant time during incidents following procedures that no longer reflect how the business actually operates.
The same dynamic that creates technical debt in software also creates continuity debt in operations: the work that keeps getting deprioritized.
Addressing this proactively costs far less than discovering it under pressure.
The Binder in the Cupboard
Almost every experienced continuity practitioner has the same story, in different variations.
An organization experiences a disruptive event: a SARS outbreak, a major blackout, a regional incident that forces a change in operations. They reach for the continuity plan. The binder is right where it's supposed to be.
But the plan inside reflects an organization that no longer exists. The processes have changed. The vendors have changed. The teams have changed. The systems that the plan was written to protect have been replaced or restructured.
Scott describes the pattern directly: "We've gone into organizations that have put some effort into business continuity or disaster recovery when there was an issue. They had realized there was a problem or they experienced an outage or something occurred like SARS or the blackout. And they realized they hadn't touched it. The binder is sitting in a cupboard. It's so out of date due to organizational changes that it didn't help them at all."
The result wasn't catastrophic failure in every case, but it was worse than it needed to be. "They had to work with what they had and had to make mistakes and take a lot longer to respond to it."
This is the fundamental continuity debt problem: the plan represents a historical snapshot of the organization, not its current reality. And the gap between the two grows every time a system changes, a process is reorganized, a vendor is replaced, or a person leaves. It is precisely the kind of problem the 2Oaks Business Operations Excellence practice is designed to address, building the ongoing management discipline that prevents plans from drifting out of alignment in the first place.
When Runbooks Become Liabilities
The same problem appears at a more granular level in runbooks: the operational procedures that document how specific systems and processes are managed and recovered when something fails.
Scott describes what happens when an incident occurs and teams reach for outdated runbooks:
"Things are being done that are no longer the way it's been done. The process has been reorganized. The whole process is handled by a different department now. Whatever. And you end up with someone saying, okay, this is what we have to do. And they're wasting hours trying to figure out how to bring something back online that's either no longer needed or being done completely differently, because they're drawing on outdated materials."
This is operational debt in a concrete form. Time that should be spent on recovery gets consumed by confusion. Teams follow procedures for systems that have been replaced, try to contact vendors that no longer hold the relevant contracts, or execute steps in a sequence that hasn't applied for years. The financial exposure compounds quickly: according to the ITIC 2024 Hourly Cost of Downtime Survey, 90% of mid-sized and large enterprises lose upwards of $300,000 per hour of downtime. Every hour a team spends working from the wrong procedures is an hour of preventable loss.
The analogy to software development is exact. Outdated runbooks are the equivalent of legacy code that nobody wants to refactor. The 2Oaks article on the problems nobody wants to solve addresses how AI is beginning to change the economics of exactly this kind of work. Runbooks, audit trails, and legacy documentation are precisely the category of work that has historically been too time-consuming to keep current, and that is now increasingly tractable with the right tools and approach.
Is your organization's continuity documentation current? Contact 2Oaks to discuss a continuity documentation review.
The Tribal Knowledge Problem
The most acute version of continuity debt isn't documentation that's out of date. It's knowledge that was never documented at all.
Scott puts it plainly:
"You have people that know how certain things are done within the organization that haven't been documented in your plans or your runbooks or anything like that. And if they're not available, it's a problem. Sure, John knows how to do that. But John left the organization two years ago."
In this scenario, the organization isn't just dealing with an incident. It's dealing with an incident while simultaneously discovering that a critical piece of its recovery capability walked out the door.
"How do we get this process up and running? How do we contact that vendor? Who's the relationship person in that vendor? Well, Sean managed all of that. It was his little world. You can run into major, major hours added to your recovery because of these oversights."
This is a problem the 2Oaks article on mastering business process mapping addresses directly: when key employees leave, does their knowledge leave with them? The answer, in most organizations, is at least partly yes. Addressing that requires deliberate documentation effort, structured systematically, not just good intentions when the next person hands in their notice.
The tribal knowledge problem is a continuity issue, an operational risk issue, and a succession planning issue simultaneously. Organizations that have solved it have typically made deliberate investments in process documentation and knowledge transfer before an incident forced them to. The 2Oaks Technology Operations and Continuity Planning practice works with organizations to identify where that knowledge currently lives and build the structures to preserve it.
What Treating This Seriously Looks Like
Addressing continuity debt doesn't require a massive program. It requires a commitment to treating continuity as an ongoing practice rather than a periodic project.
That means building regular review cycles into how the organization operates. When a system changes, the runbook changes. When a vendor relationship changes, the continuity plan reflects it. When a person who holds critical knowledge transitions out of their role, the knowledge transfer is treated as a continuity requirement, not just an HR consideration.
It also means testing. Not reviewing plans in a meeting, but actually running through recovery scenarios that surface whether the documentation still matches reality. The 2Oaks article on Beyond the Go Live makes a related point in the context of software implementations: the stabilization and optimization work that happens after launch is what determines whether a project actually delivers. Continuity programs follow the same logic. The plan that was thorough at launch needs active maintenance to stay that way.
Scott's observation about the biggest failure point in continuity programs applies directly here: "Ongoing practice. That's always been the biggest thing, and that's always why we get called in."
Organizations that have made this shift don't necessarily have more resources. They've made a different decision about priority. They've accepted that continuity planning isn't something you do once and put away. It's something you maintain, test, and improve as a fundamental part of how the business operates.
The cost of addressing continuity debt proactively is a fraction of the cost of discovering it during a real incident. The harder question is whether your organization is treating this work with the priority it deserves, or whether it's accumulating quietly on the shelf.
If you're not sure, it's a good time to find out. Get in touch with the 2Oaks Business Resiliency team.
About Scott
Scott Wilson leads the Business Resiliency practice at 2Oaks Consulting. He brings more than 30 years of experience in business continuity and disaster recovery across financial services, insurance, and public services. To discuss how your organization can address its continuity debt before it becomes a crisis, reach out here.