aNewDomain.net – For years I’ve noticed a glaringly obvious and unfortunate situation–most businesses rely on computers, yet have no plan for what to do without them. Think about it: What would you do if a disgruntled employee sabotaged the server? Or what if an employee stole important customer data? These are only two of the many unfortunate possibilities, and I’ve seen several with my clients. Disasters such as floods, fires and electrical surges all happen more often than we care to admit.
If your organization is going to survive them, you need to have a plan in place for seeing your technology—and business—through a disaster. Yet few organizations want to have these necessary conversations. Many organizations are too busy and employ an ostrich approach, hoping disasters will leave them unscathed. Many start thinking of a disaster plan after a disaster.
In May 2011 we had some of the worst flooding in Waterbury, Vermont, in recent years.
Photo credit: Jeremy Lesniak for aNewDomain.net
You’ve heard the adage, “They never planned to fail, they just failed to plan.” It’s excellent advice, and probably the best advice I can give you. Whether you develop your technology disaster plan in house or look to an outside consultant, it’s critical that it gets done. Every organization I’ve worked with has found large issues with their infrastructure by using this planning process. As onerous and time-consuming as this process can be, it’s far better to know the reality than have a false sense of confidence.
If you choose to develop your plan internally, I suggest you start with these main considerations to build a plan around:
- Create a list of all the disasters that could befall your organization. Base it on the region you live in.
- Review your technology and the impact each disaster would have on it.
- How would you respond to each of these situations?
- Is the response adequate to the needs of the organization?
A technology disaster plan is more than off-site file backup – it is an honest assessment of what could go wrong and how your organization can survive and move forward. As with insurance, you hope you’ll never need it, but it’s far better than needing it and being without.