Business continuity is the ability of a business to get back to work after something has disrupted it: hurricane, fire, flood, pandemic, or whatever. Business continuity planning is all the planning you do to prepare for disasters before they happen, so you can get back to work smoothly afterwards.
In Part One, I described a basic risk-handling protocol. In Part Two , I described the elements of how you turn regular risk-handling into business continuity planning. But of course it’s complicated. Some risks can wipe you out; others are nuisance level; many are somewhere in between. Some risks require specialized expertise to address them, but their consequences are grave enough that you can’t just delegate them to the specialists and then forget about them. How do you focus?
The answer is that you have to distribute risk-handling throughout your organization so that risks are addressed by the right people, but in a way that always traces back to top management (who have, after all, final responsibility for the organization as a whole). Let me talk about it.
Back in Part Two I said that each member of the Executive Team has to go back to his (or her) people to work out the details of that area’s approach. That step is the key to setting up a system of cascading risk management.
After all, even though business continuity affects everyone, there will always be some actions or some risks that are specific to a particular department or to a particular kind of disaster.
So yes, you have to start at the top. And the risks you track at the top level are the ones that can wipe you out. But then the members of your Executive Team go back to (let’s say) the middle managers who work for them, to do two things:
And then the middle managers do the exact same thing again, engaging with their employees at the working level, to achieve the exact same two goals.
Naturally if (during one of these lower-level reviews) anyone discovers a risk that affects a wider group (or even the whole organization) but was accidentally missed, escalate it on up the management chain to where it belongs and then ask everyone to update their work to account for it.
In the end, every unit in your organization—every division, every department, every plant, every team—ends up doing some level of business continuity analysis, and tracking the measures that apply at their level. And every year, the whole organization repeats the analysis: to identify what’s changed and to check if all the defined measures are still correct and current.
**************
Michael Mills has spent over 25 years managing quality and documentation systems for large companies and small ones. Now he does internal audits and consults on Quality projects, while regularly posting online. He publishes every week at the Pragmatic Quality Blog (pragmatic-quality.blogspot.com), and writes the Management Light column for the Organizational Excellence Specialists Group on LinkedIn. You can find him on LinkedIn at Michael Mills | LinkedIn.
**************
Oil & Gas Global Network “OGGN”
Texas Quality Assurance and the #QualityMatters podcast
Houston Young Professionals Network
KEEP READINGBusiness continuity is the ability of a business to get back to work after something has disrupted it: hurricane, fire, flood, pandemic, or whatever. Business continuity planning is all the planning you do to prepare for disasters before they happen, so you can get back to work smoothly afterwards.
I said in Part One that business continuity planning is a part of risk management in general. Specifically, business continuity planning means identifying all the risks that could interrupt your business, or some part of it, and then taking action to mitigate those risks or planning contingency actions in case they take place. The basic approach is exactly what I described in Part One , but a few features are unique.
In the first place, you have to start with your Executive Team. This is not a job you can delegate to the Safety Committee. The reason is that every entity inside the organization—every division, every department, every plant, every team—has to be engaged. They have to contribute to defining how to secure their work (because they know it better than anyone else); and they have to know what to do in case disaster strikes. So you start at the top.
When you start to identify business continuity risks, remember that you are looking for anything that can interrupt any aspect of your operations. This means you have to look not only at your direct operations, but at any support functions: billing, payroll, purchasing, and the rest. It also means you have to think about anything that can interrupt your customers or your supply chain. If you were unscathed by a disaster, but your main customers are out of commission and won’t be ordering for another year, you could have a problem. Likewise with your supply chain.
When you identify a risk, you cannot assign it to just one Owner. This is one of the big differences between business continuity planning and other kinds of risk management. If disaster strikes—hurricane, fire, flood, earthquake, or whatever it is—it’s probably going to strike everybody. So you can’t assign the whole problem to Fred or Max and ask him to figure out a solution for the entire company. Instead of that, each member of the Executive Team goes back to his people (or hers, of course) to determine how they have to secure their parts of the business. Depending on the size of your organization, some of them might have to go back to their people as well, to work out the details. Do whatever you have to do, but come back to the rest of the Executive Team with a plan for your area.
Then the Executive Team as a whole reviews the plans to make sure they are consistent. You can’t respond to a disaster by pulling in different directions: so while every team has to figure out what they specifically need, the plans still have to mesh together. As just a single example, if you are going to tell the office folks to work from home they should all be using the same communication platform to keep connected. If your team is the odd one out, you might have to change your plan a little to align with the rest of the company. Make sure you engage all the people you engaged before, so that everyone understands what’s changed.
Finally, when all the details have been worked out, document your plans in the simplest format possible, and store them somewhere that’s easy to find in an emergency. Remind people periodically where to look. (If you do regular fire or emergency drills, you might be able to incorporate pulling a copy of the emergency plan.) And mark a day on the Executive Team’s calendar—six months out, or maybe twelve—to do the exercise again.
**************
Michael Mills has spent over 25 years managing quality and documentation systems for large companies and small ones. Now he does internal audits and consults on Quality projects, while regularly posting online. He publishes every week at the Pragmatic Quality Blog (pragmatic-quality.blogspot.com), and writes the Management Light column for the Organizational Excellence Specialists Group on LinkedIn. You can find him on LinkedIn at Michael Mills | LinkedIn.
**************
Oil & Gas Global Network “OGGN”
Texas Quality Assurance and the #QualityMatters podcast
Houston Young Professionals Network
KEEP READINGBusiness continuity 1: Basic risk handling
Business continuity is the ability of a business to get back to work after something has disrupted it: hurricane, fire, flood, pandemic, or whatever. Business continuity planning is all the planning you do to prepare for disasters before they happen, so you can get back to work smoothly afterwards.
It’s a big topic. In a sense it’s a part of risk management in general, though saying that doesn’t narrow it down much. But let me start there.
You probably already have a risk handling system in your organization, so what I say here will all look pretty elementary. Still, I’ll review it briefly.
Think of the Safety Committee in a grocery store. They brainstorm all the ways somebody could get hurt, and then define measures to keep it from happening. If someone breaks a jar of spaghetti sauce in Aisle 3, put up a “Wet Floor” marker and mop it up. Don’t put heavy things on high shelves. And so on.
Sometimes they might think of a risk that’s not very likely: What if a customer brings his dog and the dog bites somebody? Well, OK. It’s true you want to know what risks you face, and (for example) the ISO management system standards all require some level of risk identification. (ISO 9001, ISO 14001, and ISO 45001 all put this requirement in section 6.1.1.) But you can’t prevent everything, so you need to rank your list in order of importance. Then you plan for the ones that really matter, and let the rest go. But what ranking do you choose? Generally there are at least two questions to consider:
Anything that scores high on both questions goes to the top of the list. After that, it’s not so obvious. But here’s one simple approach you can take. Please note two things:
Step one: Score all of your risks according to how likely they are, using just three values: High, Medium, Low.
Step two: Now score all of your risks according to their impact—how bad things would be if they happened—using the same three values: High, Medium, Low.
Step three: Use these two scores to calculate a priority for each risk, using the following formula:
Priority = Likelihood x Impact
High | Medium | Low | |
High | High | High | Medium |
Medium | High | Medium | Low |
Low | Medium | Low | Low |
On this scale, for example, “getting bitten by a customer’s dog” would probably rank Low for likelihood but potentially High for impact, for a composite priority of Medium.
Now that you have assigned a priority to every risk on your list, what next? The next step should be to address the important ones.
What happens to the risks that you choose not to address? If the store’s Safety Committee updates their list of risks to include “getting bitten by a customer’s dog” and then calculates its priority as only Medium, they might not plan any action for it. So why put it on the list?
The point is that the priority ratings aren’t static. From time to time—at least once a year, if not more often—you’ll review your list to see if things have changed.
So even if a risk falls below your threshold and you decide not to address it right now, keep it on the list. Then the next time you review the list—next quarter, next year, or whenever—you can think about it again. And as long as it stays on the list, you won’t forget.
**************
Michael Mills has spent over 25 years managing quality and documentation systems for large companies and small ones. Now he does internal audits and consults on Quality projects, while regularly posting online. He publishes every week at the Pragmatic Quality Blog (pragmatic-quality.blogspot.com), and writes the Management Light column for the Organizational Excellence Specialists Group on LinkedIn. You can find him on LinkedIn at Michael Mills | LinkedIn.
**************
Oil & Gas Global Network “OGGN”
Texas Quality Assurance and the #QualityMatters podcast
Houston Young Professionals Network
KEEP READING