The most common approach adopted to business continuity in private companies derives from the typical IT systems project activities, i.e. you select the requirements that are to be considered inside the system (within “scope”), and plan the deliverables accordingly.
What do you get? A continuity project carried out by external resources with minimal involvement of internal resources, where instead a continuity service (whose key actors should be internal resources) is what is required.
A software can be designed to deliver a certain set of results based on constraints it receives from a carefully designed environment.
Unfortunately, as discussed in the previous issue of BFM (Issue 02 Strategic Outsourcing ) almost no business can imagine to achieve the same level of control on its business and human environment.
The risk inherent in adopting a typical project approach?
That, in order to ensure compliance with the design, complexity will be obviously reduced by ignoring elements that are “outside scope”.
A more appropriate approach?
Business continuity as a programme that creates a set of services, services whose “delivery agents” will be their users .