|
|
Before we begin, let's clarify that a CRISIS communication plan is not the same as your existing corporate communication plan. It's certainly not meant to take the place of your corporate communications, except in the event of a CRISIS. Think of it as a subset/addendum to your corporate communication plan and don't close the door on a resilience practitioner who just wants to ensure that specific processes are followed during a crisis event. |
Some, and I repeat, some, organizations have absolutely stellar crisis communication plans that have been well thought-out, the people involved have been trained and the plan is tested "on the regular", to use a phrase popular with those crazy kids these days.
Some make an effort and have basic contact information documented for folks who would be required during a crisis and assume the information is current and they'll answer when called. They use phone trees… Well, the 1990s called the phone tree and want their process back. I'm not saying phone trees are a bad thing, but there are so many better ways to contact the right people effectively these days. You're wasting valuable time calling your 3 – 7 people to advise them of the situation vs pushing a button. This is time that could be better spent responding to the crisis you're calling them about in the first place.
Some make an effort and have basic contact information documented for folks who would be required during a crisis and assume the information is current and they'll answer when called. They use phone trees… Well, the 1990s called the phone tree and want their process back. I'm not saying phone trees are a bad thing, but there are so many better ways to contact the right people effectively these days. You're wasting valuable time calling your 3 – 7 people to advise them of the situation vs pushing a button. This is time that could be better spent responding to the crisis you're calling them about in the first place.
Then there are the organizations who just assume they'll know how to get in touch with people and that those people will know how to respond and whom they're responsible for contacting, etc., etc., etc. This methodology gets very ugly, very quickly in a crisis situation. |
|
What many organizations don't realize, is that contacting people is not the whole story. The whole story involves processes, contact information & methods, media (traditional and social) management, and most importantly, ensuring you're managing the narrative of the event and not allowing outside influence to distort things.
As I've mentioned in many articles I've written over the years, communications is almost always listed as a takeaway for improvement in resilience program/plan/response/exercise post-mortem meetings. Sadly, over and over and over again in the same organization. I have many theories on why this is, but will not get into them and distract from the point of this discussion.
How can BC/DR/EM Practitioners do better?
Here's DRI's Professional Practice 9 – Crisis Communications as a guide:
|
This has been something I've noticed in several organizations I've consulted with over the years. For reasons unknown to me, the resilience team and the communications team are not simpatico. So there's a disconnect during crisis events. |
The communications team members are the experts in ensuring the organizations reputation is protected and they know how to deal with outside/media questions. Letting them develop the strategy for a response by giving them your requirements is the most effective way to ensure relatively smooth sailing in a crisis.
Plus, it's one less thing you need to worry about while you're fighting whatever particular fire constitutes the crisis you're responding to at the moment. I've been part of Crisis Management Teams (CMTs), Emergency Response Teams (ERTs), involved in Emergency Operation Centers (EOCs), and called out at 2 AM to failed IT hardware over the years and believe me, any time you can download effort to someone who's an expert, it's a good thing.
Wait? What? The HR Team? Whiskey Tango Foxtrot? How is the HR team part of crisis communication planning and response?
Good question! Glad you asked
The HR team are the folks who know:
If you haven't coordinated with HR, you may find yourself dealing with agonizing employment law or collective bargaining agreement issues during and after a crisis. Avoid this by involving them early in the communication and response process planning.
An important gotcha that Resilience practitioners likely wouldn't catch, that the HR Team will, is related to privacy legislation. They are the people who are responsible for ensuring the legislation found HERE is followed within the organization and avoids leaving the door open to possible legal actions from crossing the privacy line.
I was the auditor of an exercise for a client this past summer. To that end, I had studied their response plans, audited their exercise event plan and everything looked great, was a truly impressive effort and product. I had high hopes that they would hit it out of the park and everyone would be rock stars.
Things went as expected for about 5 minutes and when I asked the Crisis Management Team (CMT) why they weren't sending alerts through their mass notification software, there were many red faces who admitted they didn't know how to use the software and did not know the passwords.
|
Oopsie… That's gonna leave a mark
|
They felt a little better after I pointed out that this is what tests are for and that it was better here than in a real event.
I didn't put it on the people who developed the plan that they should have noted that there was no check mark next to the task of educating the CMT on this key process. I spoke with them offline and told them to expect questions from the senior leadership team about why they weren't trained. I won't throw you under the bus, but my analysis report will be scrupulously honest.
As mentioned in the previous example, testing finds those dark corners that aren't immediately apparent and can throw your response into complete disarray right from the get go. I won't go into my test diatribe here, but if you want to hear more about testing, see my article on the TUG Buzz e-zine. |
|
This article isn't a replacement for a full crisis communication planning process, but I hope I've opened your eyes to some of the pitfalls and how to avoid them in your resilience planning! Good luck and remember to hug your Practitioner today
![]()
As always, thank you to the folks who provided peer review for this article and suggestions to help us appear smarter than we are.
Date: Wednesday Nov. 20, 2019
LOCATION:
Sandman Signature Mississauga Hotel
5400 Dixie Road
Mississauga
** FREE Parking **
SPEAKERS:
Kyle Foster has spent over 25 years with IBM Canada in a variety of successful sales management and leadership roles.
He has experience in all facets of IBM's business, including hardware, software and services sales in both large and small enterprises.
Kyle has a comprehensive history with the IBM POWER Brand and IBM i.
Daniel Lefebvre has over 20 years of experience in business development for the technology industry, and has assisted many clients in improving their IT systems. He particularly excels at focusing on customer service and establishing a sustainable business relationship. With a dynamic attitude and a willingness to learn, Daniel enjoys communication, business development and teamwork. His role as the Director of the Canadian Ecosystem allows him to help Fresche's partners and clients choose the best solutions to modernize, maintain and transform their IBM i applications, thereby bringing more value to their business.
Robert Arce assists companies all over the world with their modernization projects.
He has vast experience designing and developing applications, especially for manufacturing, sales and distribution environments.
He is an expert in the X-Analysis suite for IBM i application analysis and management and is an active member of the Dallas/Fort Worth Metro Midrange Systems Association (DFW MMSA users group).
AGENDA for November 20th MoMADMISSION: Free for TUG members (non-members also free,
|
The Toronto Users Group is committed to providing you with communications that are timely, relevant, and insightful. Canada's Anti-Spam Legislation (CAS) requires that we receive your permission to continue sending you emails.
You may have already given us your consent. If you haven't done so yet, or if you're not sure, please click on the following link to indicate that you would like to continue receiving electronic communications from TUG.
Should you change your mind, you can unsubscribe at any time, by clicking on "manage your subscription" at the bottom of our messages.
The Toronto Users Group for Power Systems (TUG) is a user group/forum for the exchange of ideas, and specializes in providing affordable education relating to the IBM iSeries, AS/400, System i, and Power Systems platforms. TUG is in its 35th year of operation.
Browse our
Articles & Downloads archives
Browse our
TUG Buzz! archives
Browse our
eZine archives
TUG GOLD Members |
Copyright 2019 - Toronto Users Group for Power Systems (Power Systems is a trademark of IBM Corporation.) IBM and the IBM logo are trademarks or registered trademarks of International Business Machines Corporation in the United States and are used under license by IBM Canada Ltd. Linux is a registered trademark of Linus Torvalds. Other logos appear in this message for reference purposes only, and are trademarks or registered trademarks of their respective owners.
(Please note that if you forward this email to any third party, they will be able to view your personal data once they click on the link to Manage Your Subscription, unless you remove that line from the message.)
eNewsletter design by Eclipse Technologies Inc. (www.e-clipse.ca)