Why Do Big IT Projects Fail So Often? - InformationWeek

InformationWeek is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

IT Leadership // CIO Insights & Innovation
09:56 AM
Jim Ditmore
Jim Ditmore

Why Do Big IT Projects Fail So Often?

Obamacare's website problems can teach us a lot about large-scale project management and execution.

By now nearly every American has heard about or witnessed the poor performance of healthcare.gov. Early on, only one of every five users was able to actually sign in to the site, while poor performance and unavailable systems continue to plague the federal and some state exchanges. Jeffrey Zients, the Obama appointee called in to fix healthcare.gov, promised on Oct. 25 that the site "will work smoothly for the vast majority of users" by the end of November.

Soon after the launch on Oct. 1, former federal CTO Aneesh Chopra, in an Aspen Institute interview with The New York Times' Thomas Friedman, shrugged off the website problems, saying that "glitches happen." Chopra compared the healthcare.gov downtime to the frequent appearances of Twitter's "fail whale" as heavy traffic overwhelmed that site during the 2010 soccer World Cup.

But given that the size of the signup audience was well known in advance and that website technology is mature and well understood, how could the government create such an IT mess? Especially given how much lead time the government had (more than three years) and how much it spent on building the site, (estimated between $300 million and $500 million).

This project failure isn't quite so unusual, unfortunately. Industry research suggests that large IT projects are at far greater risk of failure than smaller efforts. A 2012 McKinsey study revealed that 17% of lT projects budgeted at $15 million or higher go so badly as to threaten the company's existence, and more than 40% of them fail. As bad as the U.S. healthcare website debut is, there are dozens of examples, in both the government and private sector, of similar debacles.

In a landmark 1995 study, the Standish Group established that only about 17% of IT projects could be considered "fully successful," another 52% were "challenged" (they didn't meet budget, quality or time goals) and 30% were "impaired or failed." In a recent update of that study conducted for ComputerWorld, Standish examined 3,555 IT projects between 2003 and 2012 that had labor costs of at least $10 million and found that only 6.4% of them were successful.

Combining the inherent problems associated with very large IT projects with outdated government practices greatly increases the risk factors. Enterprises of all types can track large IT project failures to several key reasons:

Global CIO
Global CIOs: A Site Just For You
Visit InformationWeek's Global CIO -- our online community and information resource for CIOs operating in the global economy.

-- Poor or ambiguous sponsorship

-- Confusing or changing requirements

-- Inadequate skills or resources

-- Poor design or inappropriate use of new technology

Strong sponsorship and solid requirements are especially difficult to come by in a political environment (read: ObamaCare), where too many individual and group stakeholders have reason to argue with one another and change the project. Applying the political process of lengthy debates, consensus-building and multiple agendas to defining project requirements is a recipe for disaster.

Furthermore, based on my experience, I suspect the contractors doing the government work encouraged changes, as they saw an opportunity to grow the scope of the project with much higher-margin work (change orders are always much more profitable than the original bid). Inadequate sponsorship and weak requirements were undoubtedly combined with a waterfall development methodology and overall big bang approach usually specified by government procurement methods. In fact, early testimony by the contractors indicated a lack of testing on the completed system and last-minute changes.

We welcome your comments on this topic on our social media channels, or [contact us directly] with questions about the site.
1 of 2
Comment  | 
Print  | 
More Insights
Oldest First  |  Newest First  |  Threaded View
User Rank: Author
10/30/2013 | 4:25:32 PM
re: Why Do Big IT Projects Fail So Often?
The problem, evidence suggests, is both, not one or another: weak leadership; poor technology choices and implementation methodology.
Joe Stanganelli
Joe Stanganelli,
User Rank: Author
10/31/2013 | 3:42:11 AM
re: Why Do Big IT Projects Fail So Often?
Not even just sloppy code, but too much of it! Over 500 million lines. (The tech community has criticized Microsoft for coming out with an operating system ten percent that size as way too bloated.) One wonders if they were paid by the line of code!
InformationWeek Is Getting an Upgrade!

Find out more about our plans to improve the look, functionality, and performance of the InformationWeek site in the coming months.

Remote Work Tops SF, NYC for Most High-Paying Job Openings
Jessica Davis, Senior Editor, Enterprise Apps,  7/20/2021
Blockchain Gets Real Across Industries
Lisa Morgan, Freelance Writer,  7/22/2021
Seeking a Competitive Edge vs. Chasing Savings in the Cloud
Joao-Pierre S. Ruth, Senior Writer,  7/19/2021
White Papers
Register for InformationWeek Newsletters
Current Issue
Monitoring Critical Cloud Workloads Report
In this report, our experts will discuss how to advance your ability to monitor critical workloads as they move about the various cloud platforms in your company.
Flash Poll