Companies Don't Learn From Previous IT Snafus

By Kim S. Nash, Computerworld |  Business Add a new comment

Computer projects have failed for as long as there have been computers. But now that most companies are only as stable as their bits and bytes, the consequences of information technology screwups aren't easily disguised -- they show up in earnings reports.

When IT goes bad, high-growth rocket ships like Oxford Health Plans Inc. and Ben & Jerry's Homemade Inc. report their first-ever financial losses. Others crater and run for bankruptcy protection, as did drug distribution giant FoxMeyer Corp.

In a Computerworld study of multimillion-dollar IT disasters, the following two not-so-surprising themes emerged:

• User companies like FoxMeyer often file tough-to-win lawsuits against the vendors or consultants involved. Nonetheless, collectively, users rarely seem to learn much from the episodes or apply the lessons to future projects.

• All of the botched projects in Computerworld's Top 10 disasters list were big and richly complex; many were the toughest IT projects the users had ever tried. Five were hideously difficult enterprise resources planning (ERP) system implementations.

Root Causes Remain the Same

The root causes of IT failures haven't changed a bit over the years.

Miscommunication, hazy goals, "scope creep," inept leadership, pitiful project management -- you've heard, if not heeded, it all before.

"We may be neck-deep in the New Economy and Internet time, but you still have the same factors and the same failings," said Bruce Webster, a director at PricewaterhouseCoopers in Washington.

Webster recently studied 120 IT lawsuits filed since 1976, and he said he's convinced that most flops could be avoided if people simply knew the time-honored best practices of systems development.

Kevin Hickey was hired to clean up the IT mess at Oxford Health Plans


"I don't know how many IT managers, team leaders, directors and CIOs have actually sat down and read The Mythical Man-Month, The Psychology of Computer Programming and Death March," he said, referring to three books that amount to the software development canon. "The causes of disasters are all well documented. They're fundamental."

Still, warning lights are easy to overlook when the whole room is spinning.

"There's a natural tendency to get overly committed to something, especially when there are no clear signals telling you you are off course," said Mark Keil, an associate professor at Georgia State University in Atlanta.

The infamously buggy baggage-handling system at the Denver International Airport is one case that offered unambiguous proof of technology glitches: shredded luggage.

But tests of most questionable IT projects don't yield such graphic evidence.

In large systems integration or ERP deals, "there's no torn suitcase sitting at your feet to wake you up," said Keil, who has studied IT disasters for nine years. "So it's a lot easier to delude yourself into thinking things aren't that bad."

Project Euthanasia

Top 10 Failures

See Top 10 Corporate Information Technology Failures in a PDF chart. (Requires Adobe Acrobat Reader)

Euthanasia for the project might be the best course, but people often have too much heart and money invested to end it.

One technique for preventing a disaster is to add some humility to the endeavor. Invite a third party to review your work - a reliable consultant, an academic or a buddy CIO.

    Add a comment

    Post a comment using one of these accounts
    Or join now
    At least 6 characters

    Note: Comment will appear soon after you have activated your account.
    Obscene/spam comments will be removed and accounts suspended.
    The information you submit is subject to our Privacy Policy and Terms of Service.

    ITworld LIVE

    BusinessWhite Papers & Webcasts

    White Paper

    Insiders Can Ruin Your Company. Take Action.

    Did you know that 80 percent of threats to an organization come from the inside? The threat from insiders is often overlooked in organizations worldwide. This white paper from NetIQ, discusses key technology solutions that help to prevent and detect insider threats.

    White Paper

    Ten Steps to an Enterprise Mobility Strategy

    Enterprise employees are more mobile, relishing the ability to work productively anywhere, at any time. They may use any means to get connected, often creating financial and security risks for your company. Discover how to get control of your enterprise mobility strategy and ensure mobile worker productivity with these ten steps.

    White Paper

    What You Need to Know About the Costs of Mobility

    Mobile workers want to get connected anywhere, at any time, often at any cost. Enterprise mobility is often a hidden "black" budget in your company. Ensure that your traveling employees are productive everywhere, even while you control cost and security, through an enterprise mobility strategy.

    White Paper

    The 2011 iPass Mobile Enterprise Report

    This industry survey covers trends, recommendations and a policy guide on managing Enterprise Mobility for IT management and CIOs. Get data on employee device liability, as well as smartphone/tablet penetration, budget control and provisioning. Find out how your organization compares, how to ensure mobile worker productivity, and control costs.

    White Paper

    Smarter Commerce is redefining value chain visibility

    Smarter Commerce is redefining the value chain in the age of the customer. It starts with putting the customer at the center of your operations - which of itself is not a new idea - however, truly operationalizing this strategy is not easy.

    See more White Papers | Webcasts

    Ask a question

    Ask a Question