A wise old soothsayer once said: “The reasons for project failure are more numerous than grains of sand in the desert.”
The diversity of failure reflects the prominent role played by the human element in failure situations. Failures typically arise from mismatched expectations across information silos or boundaries, financial (or other) objectives that run counter to project success, and so on.
Most lists describing reasons for failure focus strictly on direct project management issues. They cover topics such as failure to gather requirements or properly plan for resources, which are important but also frequently repetitive and uninspiring.
On the other hand, there is great value in examining deeper structural conditions underlying IT failure. (Actually, these conditions are generally true for business projects across a range of disciplines, but let’s stick to IT.)
In this spirit, I draw your attention to AntiClue: Musings based on adventures in health care IT. In a recent post, author Elyse Nielsen discusses the difficulty of even defining IT project success or failure.
Her post then presents five common reasons projects fail:
- The wrong business need has been addressed – Nothing is more frustrating that solving the wrong problem. Every so often projects are launched and executed delivering a solution which doesn’t address the true business need. In these cases, the project will be considered a failure, even though everything was delivered according to plan – on time, on budget.
- The business case is a fairy tale and outcome delivery is a dream – Welcome to mission impossible for project managers. Optimistic Honesty is your true course here. We all enjoy challenges, but be truthful about the risks and work to mitigate and avoid the troublesome ones as much as possible.
- Project Goverance has not been define or implemented – Quite often in change transformation projects, sponsorship and project governance are the key ingredients to successful adoption and implementation. Project governance comes in the form of a steering committee.
- Execution is heralded by Hail Mary Passes – If in order to deliver your project, you know it is going to rely on a few hail mary passes its time to look at the execution roadblocks. Delivering technology adoption kicks it up from just implementing a solution, but if the solution implementation is not your team’s strong suit you have an impending project failure.
- The business environment changes – It’s the management renewal process, one day while getting coffee down the hall, the rumor mill is buzzing with the latest management changes. Suddenly your project has become outdated while in mid-step.
Although we all recognize the challenge of running successful IT, difficulty does not excuse failure. To succeed, look closely for subtle warning signs and clues that suggest possible impending problems. Failed projects remind us to look more closely, and act more decisively, next time.
Remember, IT failure is a common experience. Every major enterprise, software vendor, and system integrator has experienced failure. It’s high time we learned to discuss failure openly and honestly.
What do you think? Share your opinion in the comments!
Photo showing the desert, in which each grain of sand represents yet another reason for project failure as predicted by a wise soothsayer, from Flickr Commons.