Many business owners and managers readily acknowledge the fact that they need to be prepared for a disaster, and most do have backup-plans in place should something actually go wrong. The thing is, it can be difficult to actually know if your plan will be enough to see your business through a disaster. What can help is knowing the common ways business continuity plans (BCP) fail.
There are many ways a business continuity or backup and recovery plan may fail, but if you know about the most common reasons then you can better plan to overcome these obstacles, which in turn will give you a better chance of surviving a disaster.
1. Not customizing a planSome companies take a plan that was developed for another organization and copy it word-for-word. While the general plan will often follow the same structure throughout most organizations, each business is different so what may work for one, won't necessarily work for another. When a disaster happens, you could find that elements of the plan are simply not working, resulting in recovery delays or worse. Therefore, you should take steps to ensure that the plan you adopt works for your organization.
It is also essential to customize a plan to respond to different departments or roles within an organization. While an overarching business continuity plan is great, you are going to need to tailor it for each department. For example, systems recovery order may be different for marketing when compared with finance. If you keep the plan the same for all roles, you could face ineffective recovery or confusion as to what is needed, ultimately leading to a loss of business.
2. Action plans that contain too much informationOne common failing of business continuity plans is that they contain too much information in key parts of the plan. This is largely because many companies make the mistake of keeping the whole plan in one long document or binder. While this makes finding the plan easier, it makes actually enacting it far more difficult. During a disaster, you don't want your staff and key members flipping through pages and pages of useless information in order to figure out what they should be doing. This could actually end up exacerbating the problem.
Instead, try keeping action plans - what needs to be done during an emergency - separate from the overall plan. This could mean keeping individual plans in a separate document in the same folder, or a separate binder that is kept beside the total plan. Doing this will speed up action time, making it far easier for people to do their jobs when they need to.
3. Failing to properly define the scopeThe scope of the plan, or who it pertains to, is important to define. Does the plan you are developing cover the whole organization, or just specific departments? If you fail to properly define who the plan is for, and what it covers there could be confusion when it comes to actually enacting it.
While you or some managers may have the scope defined in your heads, there is always a chance that you may not be there when disaster strikes, and therefore applying the plan effectively will likely not happen. What you need to do is properly define the scope within the plan, and ensure that all parties are aware of it.
4. Having an unclear or unfinished planContinuity plans need to be clear, easy to follow, and most of all cover as much as possible. If your plan is not laid out in a logical and clear manner, or written in simple and easy to understand language, there is an increased chance that it will fail. You should therefore ensure that all those who have access to the plan can follow it after the first read through, and find the information they need quickly and easily.
Beyond this, you should also make sure that all instructions and strategies are complete. For example, if you have an evacuation plan, make sure it states who evacuates to where and what should be done once people reach those points. The goal here is to establish as strong a plan as possible, which will further enhance the chances that your business will recover successfully from a disaster.
5. Failing to test, update, and test againEven the most comprehensive and articulate plan needs to be tested on a regular basis. Failure to do so could result in once adequate plans not offering the coverage needed today. To avoid this, you should aim to test your plan on a regular basis - at least twice a year.
From these tests you should take note of potential bottlenecks and failures and take steps in order to patch these up. Beyond this, if you implement new systems, or change existing ones, revisit your plan and update it to cover these amendments and retest the plan again.
If you are worried about your continuity planning, or would like help implementing a plan and supporting systems, contact us today.