Derrick explains why business continuity planning is often treated as an afterthought during major system changes. When critical plans and documentation are postponed until after go-live, organizations expose themselves to unnecessary risk. This video outlines why continuity planning must be integrated into the transformation journey, ensuring that when systems go live, there is a clear fallback strategy to maintain operations if something goes wrong.

Chris challenges the common belief that business continuity failures are simply due to poor documentation or lack of testing. Instead, the real issue is that plans are not embedded into everyday operations. In high-pressure, unpredictable situations, teams need more than a document. This video explores how to build true operational readiness by integrating continuity planning into processes, decision-making, and organizational muscle memory.

After experiencing a real multi-day system outage, Andrew highlights a critical gap in most organizations. Disaster recovery is often tested, but business continuity is not. When stakeholders don’t know their roles during a crisis, response breaks down quickly. This video explains why documenting, communicating, and actively practicing your business continuity plan is essential to ensure your organization is prepared when it matters most.

Most organizations don't discover gaps in their business continuity planning during a calm review, they find them when a system won't come back online. Scott Wilson explains why true resilience is an ongoing practice of thinking, testing, and honest self-assessment, rather than a one-time project

Most organizations identify obvious risks like cyberattacks but are often blindsided by "quiet" threats - hidden dependencies. From the "last-mile" telecom problem to external environmental factors like transit strikes, Scott Wilson explains why looking beyond your own walls is critical for true operational resilience

Most organizations know they have operational gaps, but few know the right questions to ask to find them. In the conclusion of our series, Scott Wilson shares the practical framework for dependency mapping, moving beyond "shelf-ware" documentation to identify the vendors, people, and systems your business genuinely cannot function without