Thursday, February 16, 2012

Can self-directed teams manage BCP projects?

If you're responsible for Business Continuity Planning in a community bank, odds are you can only spend about 20% of your time on the project. If you're lucky.

Even if you can manage 20%, the time is not evenly distributed. BCP work comes in disruptive bursts, usually driven by the threat of an upcoming audit.

So idea of self-directed, "collaborative" BCP projects is tempting.

You know, where the work is distributed evenly across all business units. Featuring that slick BCP database application that looked so good in demo mode.

But what happens when the project ends badly, and you've got auditors breathing down your neck?

You can call me.

I have an unusual skill: I can look at a BCP database and tell if it is maintained by a self-directed team or by an individual.

If its an individual, I can figure out their background.
  • IT professionals leave unmistakable fingerprints. The tip off is all of the extra-budget hardware purchase orders
  • Facilities Managers: Lots of crisis management but not much business recovery.
  • Operations Managers: All the deposit related systems are critical. Loan systems not so much.
  • Loan Managers: Loan systems are critical. Deposit systems can wait until next week.
  • Marketing Managers: No. Just no. 
So what does the data look like with a self-directed, workload-balanced team?


Lists of business functions that include too much (or too little) detail. A software inventory that looks like a list of vendors. Vendors listed three or four times. Recovery tasks included in the BIA.Peanut butter in the chocolate.

If your self-directed BCP Committee has gone off the rails, you need help.

In fact, you need someone with an unusual skill: A Forensic BCP Database Analyst. A seventh inning BCP Project relief pitcher. A BCP Crime Scene Investigator.

A long-term banking professional that can enforce consistency across all business units.

Send email now: Hurry up, I hear the examiners coming up the front walk.