Return of the Guru

Why Do So Many IT Projects Fail?

Ara Trembly
Insurance Experts' Forum, June 16, 2011

What is it about IT projects that dooms them to failure about two-thirds of the time, according to experts?  This was the question I sought to answer when I put together a panel discussion on the topic at this year’s IASA Educational Conference and Business Show in Nashville. 

Apparently quite a few others were interested in this topic as well, with registrations for this session outpacing all others in the same time slot.  I called together some of the most knowledgeable consultants and insurance IT executives for this session.  I also asked some savvy vendors what they thought.  As you might expect, they came up with a lot of answers. 

First, let’s consider an amazing fact.  When I first started writing in the technology space in the 1980s, IT projects were deemed to have failed about 60 to 70 percent of the time.  Now, almost 30 years later, they still fail at the same rate!  Haven’t we learned anything over that time?  Hasn’t our technology improved to the point where we fail less?  Haven’t we found methodologies that will meaningfully impact the failure rate?  The answer, sadly, is no. 

My panel bravely took on this challenge and came up with a number of potential reasons for failure, most of which make a lot of sense.  The culprits included poor communication, poor business/IT alignment, shifting priorities over the lifetime of a project, poor understanding of the business purposes of the project, and poor understanding of the capabilities of IT to deliver on what the business wants.  Many of these involve the relationship between business and IT personnel, and certainly the history of business vs. IT in many organizations looks more like the Hatfields vs. the McCoys than anything else. 

Yet relationship problems are usually fixable.  Not that I’m suggesting that all business and IT executives get together for a group hug, but initiatives like agile methodology do provide for cooperative thinking and doing between the two groups.  Indeed, some of my IASA panelists thought agile might offer some hope for improvement over previous methods, but in terms of project success, I have yet to see the evidence.  Others tried to parse the term “failure,” noting that putting time and budget constraints on IT projects might not be completely fair. 

Well, it might not be fair, but it is reality. 

One interesting suggestion came from a vendor.  “It’s the customers,” he insisted, noting that organizations tend to change personnel, change direction and just change their minds over the course of a project that could take anywhere from six months to five years to complete.  I don’t know that I buy this completely, but I have to agree that this certainly is a powerful reason why projects don’t turn out the way they were first envisioned.  Added to this, let’s also consider that over the course of years, technology itself is continuing to evolve and improve, so that the changes planned in year one may be much less relevant in year four. 

I’m tempted to say that the reason many projects fail is that they’re just too long.  Then again, we don’t want to rush things when we’re pouring millions into a key systems replacement or upgrade.  In the end, probably the best course is to engage in smaller projects that take less time and that allow for a great deal of modification after they are complete.  The better prepared we are for change, the less likely we will deem our projects as failures. 

Ara C. Trembly ( is the founder of Ara Trembly, The Tech Consultant, and a longtime observer of technology in insurance and financial services.

Readers are encouraged to respond to Ara using the “Add Your Comments” box below. He can also be reached at

This blog was exclusively written for Insurance Networking News. It may not be reposted or reused without permission from Insurance Networking News.

The opinions of bloggers on do not necessarily reflect those of Insurance Networking News.

Comments (3)

Justin - here's a different perspective...

We find that our IT partners have a difficult time translating our functional requirements into a solution that works for the business, not just IT. We are clear on what we want, but when we walk through our ideas they assume their ideas are better instead of really trying to understand our needs.

Communication and understanding business processes is paramount to successfully deploying an application that has both ROI and improves business efficiency and effectivity. Sometimes IT doesn't realize that business clients need real input on solutions and that's where they would do better to really partner with us instead of showing us what they think we need.

Posted by: Larry C | June 17, 2011 4:52 PM

Report this Comment

Agreed on the vendor comment with Justin L. Must be a new sales strategy I have not heard of yet. With the P&C insurance industry in a flat growth pattern, ones growth gain is anothers loss. Business innovation is what results in growth. Organizations that have leadership at the CEO level, "I want IT to lower expense ratio's by 2%; quickly expand products, attract new agencies increasing agent count by 20% this year", will provide IT the target to execute. As Chesire the Cat said in Alice and Wonderland, "If you don't know where you are going, any road will take you there...." And how innovative is a project that takes 18 months to 2, 3 years to implement? The good news...lots of opportunity for P&C leaders.

Posted by: Robin G | June 17, 2011 12:59 PM

Report this Comment

Ha! I can't believe the vendor said what he did in front of potential clients!

We find that the business customers have a difficult time translating what they need into a functional description of how the solution should work for them. Or they think they know what they want, but when we talk through the solution we come up with a better idea.

Communication and an understanding business processes is paramount to successfully deploying an application that has both ROI and makes the users work efficient and effective. Sometimes the business user doesn't know a better solution is possible and that's where we come in to show them.

Posted by: Justin L | June 17, 2011 10:58 AM

Report this Comment

Add Your Comments...

Already Registered?

If you have already registered to Insurance Networking News, please use the form below to login. When completed you will immeditely be directed to post a comment.

Forgot your password?

Not Registered?

You must be registered to post a comment. Click here to register.

Blog Archive

Emerging Technology: From Insurance Challenge to Opportunity

We are now entrenched in a digital revolution that is powered by these maturing and emerging technologies.

How Insurers Can Develop Thoroughly Modern Mainframes

The user experience can make or break an application. Here are five ways to measure whether itís positive or negative.

The Peer-to-Peer Economy and the Uberization of Insurance

Insurance is about risk sharing, so what better model to bring in technology and make that risk sharing as efficient and effective as possible?

Rethinking Commercial Lines Underwriting Automation

The value an insurer can achieve from the powerful combination of a modern policy system and a complete suite of advanced underwriting solutions will far outweigh any effort involved.

Students are Pushed to Look Past Obstacles, and so Should We

Student teams, in the space of a few weeks, developed a variety of fresh ideas leveraging unique technologies that could help build products and services for insurance customers.

The Best Policy Administration System I Have Ever Seen

So many systems we view look like they screens were designed by a programmer and, worse, could only be used by a programmer.