We use cookies and other similar technologies (Cookies) to enhance your experience and to provide you with relevant content and ads. By using our website, you are agreeing to the use of Cookies. You can change your settings at any time. Cookie Policy.

Manage Tomorrow's Surprises Today

Steven Minsky

How ERM Prevents Disasters: Case Studies by Malcolm Gladwell

Vote 0 Votes
Plane - Transport Industry

Over the weekend while traveling, I was reading Malcolm Gladwell's Outliers, and as coincidence would have it, I hit "Chapter Seven: The Ethnic Theory of Plane Crashes," at a cruising altitude of 30,000 feet. 

The challenge with Enterprise Risk Management is quantifying how many disasters have been prevented due to its efforts.  Because of this, there is still skepticism among senior management around exactly how ERM can help to prevent major operational, strategic, regulatory, and reputational disasters.

In the chapter, Gladwell examines not just plane crashes, but industrial accidents as a whole.  His primary argument is that accidents are not the result of a single event, like a major mechanical failure as people often fear, but are actually a series of "completely unrelated events... each of which, had it happened in isolation, would have caused no more than a hiccup in the plant's ordinary operation," using Three Mile Island meltdown as a case study.

These are exactly the types of situations an Enterprise Risk Management Taxonomy helps to identify.  A taxonomy creates a common repository of business processes, product lines, geographic regions, strategic goals and resources such as physical assets, applications, vendors, and people. 

A risk taxonomy enables risk assessments, controls, tests, issues, findings, and incidents, to be conducted for a variety of governance and operational reasons, integrated or independently, and all tie back to each other and to central components of your organization.   As a result, you can identify when red flags, that on their own "would cause no more than a hiccup" in operations, all tie to a common area that could combine to cause a disaster. 

As an example, using LogicManager's Taxonomy, one of our customers was able to start looking at vendors holistically because vendor management, legal, finance, and the process owner could all tie their assessment of the vendor to a common source.

With changes in the economic environment, the organization re-evaluated vendors and discovered that this vendor was weak financially and posed serious financial and operational threats. However, the vendor had extraordinary performance in a key line of business, so when brought to the attention of the process owner, a stalemate occurred, as the alternative was to take away certainty of profit and performance in order to potentially prevent a loss event in the future.

With a common taxonomy and a risk-based approach, the information gathered in the assessment of the vendor uncovered the multi-dimensions of the problems and put all the facts on the table. The true source of the risk was identified and a contract change provided a cost-free way to significantly mitigate the financial risk of this vendor.  The organization was able to prevent a major loss event, and add value to the organization by finding a way to continue using the vendor when it was most beneficial to the bottom line, while significantly mitigating the risk. 

To learn more on the explaining the bottom-line benefits of ERM, download our free whitepaper: Return on Investment: Enterprise Risk Management.

Leave a comment

In this blog, risk expert Steven Minsky highlights the differences between traditional risk management and true enterprise risk management, which is about helping things happen rather than preventing them from happening. Manage Tomorrow's Surprises Today is designed to help you think about risk in new ways and learn how to benefit practically from this rapidly evolving field.

Steven Minsky

Steven is the CEO of LogicManager, Inc. the leading provider of ERM software solutions. Steven is the architect of the RIMS Risk Maturity Model for ERM, author of the RIMS State of ERM Report among many other papers, and a RIMS Fellow (RF) instructor on ERM. Steven has conducted ERM and RIMS Risk Maturity Model training for hundreds of organizations around the globe. Steven is a patent author of risk and process management technology and holds MBA and MA degrees from the University of Pennsylvania’s Wharton School of Business and The Joseph H. Lauder Institute of International Management. You can reach Steven at steven.minsky@logicmanager.com.

Recently Commented On

Monthly Archives