We’re sure that by now, you’ve seen all of the stories about last week’s computer turmoil at the New York Stock Exchange, United Airlines, the Wall Street Journal, and TD Ameritrade. And as a top-level executive you’ve probably launched an internal review, or at least asked yourself, “Could it happen here?”
The simple answer is, unfortunately, “yes, it most definitely could.”
When news of the NYSE and UAL outages first hit the wire, the initial response was to question whether these were incidents of cyberterrorism. It turns out they weren’t, but it demonstrates the current mindset. The root cause turned out to be software robustness… actually, the lack of it.
“Software robustness” may sound mundane when compared with “cyberterrorism.” But it’s far more fundamental to your company’s IT infrastructure…even more so, as many of the world’s largest companies engage in what Gartner calls “digital transformation.”
But software robustness is being ignored for any number of reasons:
What’s the solution? Structural quality must be measured and owned. The standard metrics have been available for years, and are getting the official stamp in September. The challenge is that it all starts with you and others in the C-suite. The best practitioners institute something like a “10-10-10” program, where:
In addition, there are emerging standards to quantify software quality that will be adopted by an industry-wide body by the end of this year. (We’d be remiss to mention that at CAST, we have an automated system that can help you meet these standards. 250 companies around the world use it; one-third are on the Global 2000.)
Outages like those that hit the NYSE and UAL can cause immediate loss of revenue, loss of confidence and reputation damage to the brand and to yourself. We trust you’ve already implemented a software robustness review at your firm. If not, we are here to help.