Disasters and how you can (try to) avoid them

[caption id="" align="alignright" width="300"]disasters View of Chernobyl taken from roof of building in Pripyat Ukraine. Photo Taken by Jason Minshull, then digitally zoomed. (Photo credit: Wikipedia)[/caption] Have you noticed how often it happens that when things go wrong, they don’t just go wrong, they go horribly wrong? From the truly horrendous disasters like Chernobyl and Fukushima to the merely painful like a company going bust, once things have started to go bad, the interventions people make often exacerbate the situation. Why is that? When things start to go wrong, there can be a number of immediate reactions, depending on the circumstances. One is to hide your head in the sands, and pretend that there is nothing wrong. That is almost guaranteed to make things worse! More common is the fire hose approach:  do something drastic with the intention of stopping the immediate threat, which may deal with the underlying causes (although it may also exacerbate them), but certainly soaks everything, whatever the consequences. Following the analogy, the fire hose is good at putting out some sorts of fires, but inadvisable on oil or electrical fires! In between is the timid approach – not wanting to do any more damage than can be avoided, the attempted cure finishes up being too little and too late. How difficult it is to get the balance right!

Fast disasters …

It is understandable that in a crisis people react by tackling the obvious problems. If your house is on fire, stopping the flames obviously seems more important than avoiding ruining the furniture.  When the situation is relatively simple, that approach works. The problem comes when the situation is more complex. In a crisis, you act instinctively, and you do not usually have time to think through the consequences of your actions. Almost by definition, complexity will bring unforeseen consequences. How many organisations have no more complexity than they need? What to do about this? There are two possible approaches. You can minimise the risk of unforeseen consequences in a crisis by keeping the organisation as simple as possible. Or you can practice crisis management through exercises and so attempt to learn what adverse consequences might occur and how to avoid them. Or you can do both, of course. Clearly though, both of these have a cost which needs to be incurred when there is no crisis in sight.

… and slow disasters

Slow disasters pose different and much more difficult problems. The fire-hose approach is much less likely; head-in-the-sands and timidity more so. It all starts with ability to acknowledge the problem in the first place. The organisation’s leaders may not believe that what they are seeing are signs of a problem. Even if they do think there is a problem, they may not want to admit this. They or people they are connected to may have vested interests; they may be unwilling to admit failure, or believe that admitting problems will damage confidence and make them worse; they may believe that other issues are more urgent. Perhaps the most common situation is that leaders recognise the problem, but simply underestimate what is needed to fix it. Most managers are optimists at heart, and in deciding what – often painful - actions are required, optimism bias will tend to creep in to minimise the pain. These can be very difficult decisions:  for example, no manager wants to make any more staff redundant than they absolutely have to. However, if the ‘cure’ is insufficient, the problem remains, and will have to be treated again – with the ‘patient’ now in a weaker condition than previously. Underestimating can be fatal: death by a thousand cuts is a phrase I have heard repeated too often, and the consequences for staff can be worse than being bold at the outset. In summary then, perhaps the message in both cases is the same: optimism rarely provides salvation; taking what feels like unnecessary pain early may do.

A mug’s game?

informing board members I’m on my way to a Board meeting. My job as a Board member is to turn up about once a month for a meeting lasting normally no more than a couple of hours to take the most important decisions the company needs – decisions which are often about complex areas, fraught with operational, commercial, legal and possibly political implications, and often with ambitious managers or other vested interests arguing strongly (but not necessarily objectively) for their preferred outcome. Few of the decisions are black and white, but most carry significant risk for the organisation. Good outcomes rely on informing Board members effectively. This is a well-managed organisation, so I have received the papers for the meeting  a week in advance, but I have had no chance to seek clarification of anything which is unclear, or to ask for further information. In many organisations, the papers may arrive late, or they may have been poorly written so that the story they tell is incomplete or hard to understand (despite often being very detailed), or both. The Board meeting, with a packed agenda and a timetable to keep to, is my only chance to fill the gaps. I have years of experience to draw on, but experience can only take me so far. Will I miss an assumption that ought to be challenged, or a risk arising from something I am not familiar with? If that happens, we may make a poor decision, and I will share the responsibility. In some cases – for instance a safety issue - that might have serious consequences for other people. It’s not a happy thought.

Informing Board members

In order for a Board (or any other body) to make good decisions, it has to be in possession of appropriate information. These are some of the rules I have followed when I have set up arrangements to promote effective governance.
Good papers
Good papers tell the story completely and logically, but concisely. They do not assume that the reader knows the background. They build the picture without jumping around, and make clear and well-argued recommendations. They do not confuse with unnecessary detail, but nor do they overlook important aspects. As Einstein said, “If you can't explain it simply, you don't understand it well enough." Provide rules on length, apply (pragmatic) quality control to the papers received, and refuse to include papers if they do not meet minimum requirements (obviously it helps to be able to give advice on how to make them acceptable). You must of course choose a reviewer whose judgements will be respected. This may well result in some painful discussions, but people only learn the hard way.
Timely distribution
If members do not have time to read the papers properly, it does not matter how good they are. If I am a busy Board member, I may need to reserve time in my diary for meeting preparation, and this is a problem if I cannot rely on papers arriving on time. Set submission deadlines which allow for timely and predictable distribution, and enforce them. Again, be prepared for some painful discussions until people learn.
Informal channels
Concise papers and busy Board meetings are never going to allow for deep understanding of context. To overcome this, I have organised informal sessions immediately preceding Board meetings, over a sandwich lunch if the timing requires. Allocate a couple of hours for just two or three topics; bring in the subject experts, but spend most of the time on discussion. Not all Board members will be able to attend every session, but in my experience not only have they found them hugely valuable in building their wider knowledge of the business, but the opportunity to meet more junior staff has been appreciated all round. There are many other ways that informal channels could be set up. Different things will work in different organisations. Key to all of them is building trust: informing Board members properly means allowing them to see things “warts and all”, and trusting a wider group of staff to talk to them.
Organisation
To do all of these things effectively, you need to have someone (or in larger organisations a small secretariat team) whose primary objective is to deliver them. This is not glamorous stuff, however important, and it easily gets put to the bottom of the pile without clear leadership. Finally, remember that nothing will happen unless the importance of this is understood at the very top.  If the CEO does not set an example by sticking to time and quality rules, no one else will.

Bang!

wrong assumptions Years ago, I was managing the sale of a business division. The business was based on carrying out a highly-specialised technical test on clients’ products, and each time a test was carried out, it made a loud bang. This would have been of no concern if it had not been that they were carried out in a large workshop also used for other activities. However, checks had been made and the noise levels were within legal safety limits. Just before signing the deal, we happened to mention to the purchaser that we had some tests scheduled for the next day, and he said he’d like to send someone round to check the sound levels. It was a beautiful summer’s day – until their measurements showed that the bangs were over the limit. What a toe-curling moment! Clearly, we had made the wrong assumptions. In the end it was not as bad as it seemed: a sound-attenuating box solved the problem without making access too difficult, at quite modest cost and with only a few weeks’ delay. But the proving tests provided another surprise – the noise levels were legal again without the box. The reason – we now realised – was that the humidity of the air could affect its sound-attenuating properties.

Avoiding wrong assumptions

Conclusion 1 – Make sure you know what factors can affect your assumptions. Wrong assumptions may lead to disaster. Conclusion 2 – Don’t rely on conclusion 1! If something is critical, don’t rely on a modest safety margin – do what you can to increase it early, in case there is something you have not anticipated.