Agile Business Continuity

21 May, 2010

BCP Documentation

Posted by: pdjamez In: BCM|Blogosphere|Embedding

Since I took a break from the blog there have been some interesting posts from other bloggers, that I have only recently had time to catch up on. One which caught my eye was from the the Business Continuity Guru Blog by John Ames entitled BCP Documentation – Keep It Simple & Uniform. In this post John asserts that software is causing much frustration amongst his small and medium sized clients and that the solution to this is a much simpler approach using standard templates. I can sympathise with his client’s frustration, but doubt that software is the issue, although there is clearly some truly badly designed software out there.

So first let me take issue with one half of John’s solution, although I will add a caveat at the end of this paragraph. I certainly agree with a simpler approach to the planning process and have indeed promoted this on the ABC blog in previous posts. I would however take issue with the idea of uniform plans. It is not that I believe that each part of a business should have different types of plan, but rather some areas require more detail than other areas. I don’t believe that my own perspective on this and John’s are that far off, but I do worry that uniformity merely leads to that old tickbox culture that we are all busy fighting. Aren’t we? Promoting the idea that “fill in this set of documents and your done” benefits no one, except of course those who promote such ideas. The caveat on this is of course that John seems to deal in the small and medium sized organisations who need a much lighter touch than larger organisations. In these types of organisation John’s cookie cutter approach will almost certainly develop a more beneficial output, although it may not be optimum.

On the software issue, as you may already know, I disagree that software is the root of all evil. As I have said before, if software is not providing a material benefit then it is likely the wrong software. With a single stroke many practitioners paint business continuity as not benefiting from software optimisation, and I find this a little hard to believe. The suggestion that we don’t need software is often followed by an assertion that all you need is … Word and Excel … or as I like to call it … software. Now that you are using Word and Excel, can you imagine one small feature that could be added to your Word and Excel system that would make your clients life easier, simpler and more cost effective. Great, now imagine another, and another … and possibly another.

I have seen the disasterous concequences of the application of a Word, Excel based solution. Indeed, I have a number of clients who have previously spent vast quantities of money implementing such a solution only to find that they have made no material difference to the resilience of their organisation. I am not suggesting that software is a panacea (software never is), but suspect that in terms of this argument, it may simply be a useful diversion from other issues. Rather than blaming the software tools (or Word templates) it may be time to understand that some Business Continuity practices are the problem.

On a side note, here is my favourite section of John’s post:

Ask yourself the following questions. What does the content of your documentation reveal? How is the document organized? Can you (or someone other than the planner) follow the defined path for response, resumption and recovery? Just how effective would the documentation be if you actually had to utilize it?

I couldn’t agree more John, if only more people asked these questions, how much more resilient the world would be.

Related posts:

  1. Can Software Support Your Resilience?

3 Responses to "BCP Documentation"

1 | Jim Mitchell

September 30th, 2010 at 1:06 am

Avatar

You make several good points. Documentation should not be the goal of BCM. But all too often it is.

The goal of BCM ought to be Preparedness, but it seldom is. Preparedness isn’t just planning, it’s understanding (and practicing) how you will deal with the unexpected.

Burying facts (dependencies, strategies, key resources) in Word documents hides them everyone but the document owner (I won’t even address the all too common fact that most plans don’t contain much more than a call tree and a few lists – like BP’s!!).

When an Incident occurs, what happens? Leaders try to lead. To manage an Incident intelligently they need facts and information. When all the information is buried inside Plans, they waste valuable time trying to ferret it out (if they can).

It’s not the document that’s at fault. It’s the lack of coordinated data availability that makes many planning programs of limited use.

That’s where some software programs can provide a major advantage that Word and Excel can’t. Starting by ‘modeling’ dependencies, impacts, RTO’s, critical resources and enterprise-wide alternative strategies, software can provide a two-fold benefit:

Providing decision support for Incident Management and,

A useful starting point for creating plans that have value – because they incorporate strategies to recover/acquire the critical ‘assets’ that enable business operations to continue or recover.

When I hear someone say “we don’t need software’, I know several things about them: they’ve never experienced a prolonged or consequential disruption, and they are merely plan auditors – not Business Continuity Program managers.

2 | Marc

January 6th, 2011 at 7:45 pm

Avatar

Very good points!

I do have one thing to add though. You mentioned that software CAN in fact be a boon to business continuity, and I agree with you wholeheartedly that it must be the “right” software. Do you think, though, that software can often become a crutch that gets in the way of purely inter-personal methods of BCP implementation?

3 | Rachel Cade (scenario-based continuity exercise specialist)

December 17th, 2011 at 8:14 am

Avatar

Ok, I’m going to confess that every year I do the rounds at the BCI conference and look at the software, and every year I fail to find anything that I can wholeheartedly recommend to clients.

My worry with software based planning is that it has the ability to become a form-filling exercise rather than a planning process.

I’ve recently seen one system that I think might be useful if it was tweaked more but, even then, I wonder if I just want it to work because my companies (when I work in-house) and clients (when external) really want me to have a recommendation.

Until I have one I stand by my notion that it’s better to have a real plan done in plain old word than a beautiful and organised one that was created after a form filling exercise in a manner that those who used it haven’t truly thought through their step-by-step arrangements and checklists…

Which software might you recommend I look at next?!

Comment Form


About

The main purpose of this site is to capture business continuity issues and share the ways in which practitioners are overcoming them.