By Kelley Pidhirsky
You bring on a new software-as-a-service (SaaS) application. It improves efficiency beautifully and becomes a critical part of your daily operations. Wonderful! Did you remember to put it into your business continuity (BC) plan? No?
You have made your BC plan a master repository of all the information you could ever want in time of crisis. You’ve included data files, contact information, and all the rest of it. Great! Has any of that data or information changed in your production environment? It has? Have you updated your BC plan to reflect that change? No?
Let’s face it. Because of the rate of change in business today – new SaaS applications, employee-sourced apps, incoming and outgoing personnel – BC plans can become outdated fast. A plan that is just three months old could easily have gaping holes that could cause recovery time objectives (RTOs) and recovery point objectives (RPOs) to go down the drain if you experience an interruption or outage.
The last thing you want to add to a crisis is clutter, chaos, and confusion. But how do you avoid it? You need to de-junk your business continuity plan. Find out how in four steps by downloading this free resource Revitalizing Business Continuity.
Don’t allow yourself to get distracted from this critical step. Yes, it’s easy to devote all your resources to managing production complexity. Business needs to keep going full steam ahead, after all! But all those changes routinely break your business continuity plan and undercut your business resiliency. Without an up-to-date BC plan, you run the risk of downtime and disaster. Discover the four steps necessary to make sure that when crisis hits, clutter, confusion, and chaos will not slow you down!