By John Covan
[Editor’s note: This opinion piece originally appeared in Vol 35 Issue 4 of Journal of System Safety in 4Q 1999. It has been reformatted from the original, but the text is otherwise unchanged.]
I‘d like to begin a debate about the role of system safety in business.
I have often heard the complaint that safety (in particular, system safety) is viewed by system developers as a necessary evil – something that must be tacked on after the important decisions are made about system architecture and function. How many of us have heard, when trying to inject system safety into a new project, “Come back later, it’s too early for us to talk to you just now”?
Of course we know that to be maximally effective, system safety must be fully integrated from day one. But if we act as if system safety is at the top of the list and argue for our presence based on our company’s slogan (let’s assume it is “Safety is job one”), we will never achieve this integration.
In my opinion, nobody in upper management of the typical company believes that safety is the top priority. This simply reflects the cold, hard facts of business. In his March 1998 Atlantic Monthly article on the crash of ValuJet Flight 592 into a Florida swamp, William Langewiesche writes, “Safety is never first, and it never will be, but for obvious reasons it is a necessary part of the venture.” What venture? The business venture.
So what if you don’t work in the corporate, for-profit world? Does that mean you, as a government or military employee, are exempt from the “business” mindset? No, not for at least the last decade or two. Let’s face it, all the outfits we work for boil down in the end to a business of some sort, competing to produce goods and services and maintain the status quo. Maybe they don’t have a profit line, but they work pretty hard to grow their budgets.
Business people (including project leaders and upper management) tend to focus on words like functionality, marketability, cost and schedule. And why shouldn’t they? If they don’t tend to these issues, their business —- whether product or service – is at risk of failing from loss of competitiveness or other business deficiencies. But safety is not their long suit, and that does hurt their business.
Now, nearly three-and-a-half years after the crash, the lawsuits are still making the news. It was a high consequence event, especially in the business sense. One would think that the airline industry would have gotten busy and hired a phalanx of system safety experts to improve things. But recent press releases tell of improper hazardous materials shipments (the reason the ValuJet flight went down) continuing to flood the airways.
Consider the demise of the billion dollar offshore oil-drilling platform Piper Alpha by fire and explosion in the North Sea in 1988, with the loss of 167 lives. System safety could undoubtedly have prevented the accident by re-emphasizing safety culture as a necessary part of the profit motive, for example. And system safety could have mitigated the horrible consequences by redesigning the rig’s survival systems when the decision was made to retrofit for gas production. Yet the platform design and its management enjoyed no such benefits, and the system blundered forward to a predictable, catastrophic end. The business impact was a bitter pill to swallow – Occidental Petroleum left the North Sea, never to return.
So what’s wrong with this picture? It’s that missing or inadequate system safety is a business risk – just like any other business risk. Sounds simple, right? I don’t think so. If it were, I wouldn’t be writing this essay. The temptation for upper management to separate safety from other business concerns is strong. As long as this way of thinking persists, system safety will continue to be a day late and a dollar short.
To my way of thinking, the only road to success is convincing the powers responsible for designing, building and running systems to add system safety to their business toolkit. These people must become active partners in the process and understand it to its core. Only then will our tasks be elevated to the importance they deserve.
So what can be done to turn things around? Probably lots of things like educating the business community, CEOs and the like. Perhaps we can start with the SSS. What can we do to attract such an audience? Or, are there other avenues to changing the culture of the business community?
I would like to hear your opinions. I believe the SSS has a golden opportunity to reinvent itself and become inclusive of a broader audience. If we don’t, we will remain a bunch of specialists talking to ourselves.
About the Author
At the time of writing, Dr. John Covan was the Vice President of the New Mexico Chapter of the International System Safety Society and was a senior member of the technical staff with Sandia National Laboratory.