Wednesday, 21 December 2011 09:57

Why Projects Fail: A Root Cause

Written by 
Rate this item
(3 votes)

FEATUREDec21stWhat is one of the root causes of project failure?

Last month we explored how much project management was enough.  It is generally accepted that just the right amount is needed based on the situation.  It is usually when the project is over or under managed that we have failures.  Common project management causes of failure are:

 

  • “Wishful” Planning – Planning that is based on the desire to have something done by a deadline and within a budget limit without regard to the reality of the situation.
  • Lack of portfolio management – initiating projects without regard to whether they are justified based on sound business reasons
  • Poor project control communication – Hiding the reality of project trouble until it is too late to do anything but bemoan a horrible outcome
  • Lack of accountability – Allowing project stakeholders to fail to deliver what is expected of them without accountability.
  • Absentee sponsors – Sponsors failing to perform their functions to provide direction and leverage.

Each of these causes is worthy of an article if not a book.  But, in this article, let’s look for a common root cause. 

In a recent webinar, Joseph Grenny hypothesized that the root cause underlying these and other problems in projects is failure to effectively hold crucial conversations.  It is the Abilene Paradox in action, where silence or avoiding difficult confrontations robs the project team and its organization of the ability to either avoid the causes of failures or to catch the causes early in their life to turn the project around or end it when that is appropriate.

What is the Abilene Paradox, you might be wondering?  It is the phenomena where a group of people collectively decide to do something that is counter to the preferences of everyone in the group and counter to the benefits of the organization or group as a whole.  It involves a breakdown in communications.  Each member of the group avoids saying what they think because they think it would be counter to what the group or its leadership prefers.  As a result valuable information is withheld and the group is not able to make effective decisions.

For example, an individual feels that a project plan is overly aggressive but fails to speak up because he or she is afraid that saying anything about it would have negative consequences.  As a result the “wishful” plan becomes the baseline plan and sets expectations for the project.  This leads to the inevitable overruns and the rushing, corner cutting and such that, in turn, causes poor quality product to be delivered late and over budget.

If, fact, this failure to speak up and hold the crucial conversation in a respectful and candid way is a root cause of these causes of project failure, what can we do about it?

If we are in a position of influence we can create a safe environment in which people do not feel threatened for saying what they think, even if it is not what everyone wants to hear.   If we are a less influential (everyone has some influence, usually more than they think they have) player, we can muster up the courage to “tell it as we see it” and learn the skills of how to confront directly and firmly with appropriate diplomacy.

Don't forget to leave your comments below.

Read 11410 times Last modified on Wednesday, 21 December 2011 10:09
George Pitagorsky

George Pitagorsky, PMP, integrates core disciplines and applies people centric systems and process thinking to achieve sustainable optimal performance. George authored The Zen Approach to Project Management and PM BasicsTM. He teaches meditation and is on the Board of Directors of the NY Insight Meditation Center.

Comments  

 
0 # L Camm 2011-12-21 05:19
More often than not the primary reason for problems occurring is the lack of communication between the Client and the Consultant; the individual members of the Design team; the Design team and the Contractor. The PM can help make sure appropriate communication occurs. Ensuring the Client clearly expresses their requirements; ensuring all of the design team remains on the same page; ensuring the Contractor constructs in accordance with both the Client and the Designer requirements. This formula is not a panacea for all problems but it sure helps avoid significant surprises down the road.
Reply | Reply with quote | Quote
 
 
0 # Hal Macomber 2011-12-21 05:41
Not speaking (up) is one of the two most common sources or waste on projects and in organizations. The other is not listening. We called these "The Two Great Wastes" in a paper we wrote for the International Group for Lean Construction (IGLC) 2004 conference in Copenhagen. As most of us have probably experience not speaking will lead to not listening and vice versa. The pattern can be broken as George says with a little fortitude and an effective crucial conversation. You'll find the paper, along with the others presented in that conference here http://www.iglc2004.dk/13722.
Reply | Reply with quote | Quote
 
 
0 # Bob 2011-12-21 05:50
I certainly support the conclusion and premise here, but not sure if I agree that this behavior is a paradox, as it is a predictable outcome given human nature. Factor in today's economy, where companies try and maximize the amount of productivity from each worker, and have cut those resources to bare minimums, and the pressures are even greater to fit a round schedule into a square budget into a triangular desired quality. You end up with the tur-duck-en of the project management world, but lacking the tasty result....
Reply | Reply with quote | Quote
 
 
0 # Jay P 2011-12-21 06:11
Great article and true on all accounts. As an experienced project manager myself, I've seen first hand how withholding real project risks and issues can derail the entire initiative and diminish expectations rapidly. The worst result- losing trust between a client and supplier. As Jack Welch realized in his many years of tenure at GE - being candid is absolutely critical to the organization's success in both the short and long term.
Reply | Reply with quote | Quote
 
 
0 # Amber R 2011-12-21 11:29
Failure to have candid conversations is definitely a reason for project failure. More central than that is (a) lack of clarity about who (i.e., a person, not a committee) gets to decide what the project is and (b) what constitutes "done." You can have all the candid conversations you want, but if you can't define who gets to decide what the project is (and isn't) you risk trying to please everyone...and we know where that career path leads. "Did you want fries with that?"
Reply | Reply with quote | Quote
 
 
0 # Alan Gladman 2011-12-21 18:45
To me it seems that all these roads lead to one root cause.... "the inability of individuals to speak truth to power". Whether its giving estimates that you think your project manager wants to hear, or keeping issues quiet until its too late. So I agree those of us in these positions of "power" need to make it easy for team members to speak the truth without fear of retribution.
Reply | Reply with quote | Quote
 
 
0 # Joe MacNish 2011-12-22 01:46
Being candid is half the battle, the other half is to be convincing. It is hard to speak up about issues that are counter to the plans and expectations of leaders and groups, but if you don't want to double-down on your Abilene Paradox with a Cassandra Complex, don't just give your opinion- make an argument based on hard data and/or specific similarities with past initiatives. The better your case, the easier it will be to speak up and the greater likelihood of results. Joe MacNish www.TrackerSuite.Net
Reply | Reply with quote | Quote
 
 
0 # George Pitagorsky 2011-12-22 23:33
Regarding the Abilene Paradox (Bob's Comment), the paradox is that groups of intelligent people will end up doing things that are undesirable to all of them. Whether human nature or not is a philosophical question. Practically, Trips to Abilene (i.e., doing things that are undesirable) can be avoided by speaking up skillfully with one's opinion and the facts that support it.. Re Amber R's Comment, the other causes are certainly common and central. can they be avoided by speaking up about omissions and errors in the plan. Most project managers know the right thing to do. The problem is that they don't argue convincingly for doing them.
Reply | Reply with quote | Quote
 
 
0 # Cindy Lee Weber 2011-12-28 03:35
I was part of the study that J. Grenny did with Project Management and Crucial Conversations. It was fascinating. In every project office I've had to work with, my own or my clients, I suggest this skill of having those CC's is one open for improvement. Soft skills are key to leadership!
Reply | Reply with quote | Quote
 
 
0 # H M Thakur 2012-01-11 15:30
Very True, failing to converse and creating an conducive environment to share things openly and with transparency is basically the root cause of failure. Unless, we understand the expectations of the stakeholders, how can we manage these?? Moreover, we tend to hold the facts due to perceptions/app rehensions with regard to what others may feel or others may not like to hear these and/or may see it as a complain etc..
Reply | Reply with quote | Quote
 
 
0 # Aamer Inam 2012-01-23 15:40
Among several reasons why project fail have been briefed in the article . In addition to that based on the experience I have earned so far , there are other reason as well that cause project a fail or problem project (always in a red). In case organization pursue a project that had been done by the ex-colleagues and later on new team all together a bunch of resources absolutely new to the project are included How it fails the project : First of all , the bunch of new resources are to understand the old application in order to incorporate new requirements and it adds petrol to the fire if team members are not technically that sound to for see the impacts of new requirements on the older version. Clien t availability or the domain expert from the client can be one of the reason to linger on the requirement gathering phase . The longer it takes to sign off the requirements , worse it get in the end because initial planning gets affected by tons of hours . In this scenario , contract should be sound enough to cater such delays on client part and due addendum should be in place to revise the contract duration and value otherwise if this factor is not taken in to account ultimately its going to be a fail project . This may deliver the deliverable but at much more higher cost involved and off course will be failed project.
Reply | Reply with quote | Quote
 
 
+2 # Chris 2012-02-09 07:24
I'm also quoting and extending a previous comment. "Bein g candid is half the battle, the other half is to be convincing" needs a little addition, as follows. "Being candid is ONE THIRD of the battle, the other TWO-THIRDS are being convincing, AND ensuring that conversation is recorded or its information is retainedin a way that can be accessed, referenced and used as input on future decisions." Ma ny vital "conversations" are almost useless if all they are is conversations. Someone needs to be accountable to react to them, and keeping an accurate record of them is an important component of creating that accountability.
Reply | Reply with quote | Quote
 
 
+1 # Iain Begg 2012-02-12 17:21
There is always a single Root Cause.......PEO PLE! And it for this reason that Project Management is both and Art and a Science (arguably more Art than Science). Methodologies, Standards and Processes are important and valuable becuase they bring structure and enable common understanding, but it is PEOPLE who implement these.
Reply | Reply with quote | Quote
 
 
+1 # Charles Gallagher 2012-02-13 09:42
Hi George, I really enjoy reading your work. I often find that the lack of crucial conversations are the result of 'knowledge gaps'. As a result, people tend to lack the courage to admit what they don't know...assuming of course that they know what they don't know. Chad
Reply | Reply with quote | Quote
 
 
0 # George Bridges 2012-02-14 20:44
I really like this article George. Can we really say the we can find a root cause to project failures. By definition projects are unique, so how can we say that we can determine a root cause. Perhaps the success factors for each project is unique and the failure factors for the project are unique. Project Managers will debate this subject for as long as the world exist.
Reply | Reply with quote | Quote
 
 
0 # George Pitagorsky 2013-03-22 22:41
I think while all projects are unique there are enough similarities to say that there is a root cause or perhaps a few root causes of failure.
Reply | Reply with quote | Quote
 
 
0 # Asket 2012-02-15 09:51
To drill down even further on this issue, as to why people are fearful to say anything against the 'leadership' is the concept of contracting. Most of the time there are contractors who recognise that proposals being put forth by 'leaders' are not quite correct, but do not say anything in fear of losing out the contract/contra ct extension/futur e contracts. The risk is simple too much for them, however the perms do not any such risk. well maybe a bit smaller in terms of promotion but atleast the job is secure. With more and more firms trimming on perms and getting contractors on board, I feel the problem will compound in coming times.
Reply | Reply with quote | Quote
 
 
0 # George Pitagorsky 2012-02-18 04:06
Chad, re "Knowledge gaps" - I agree that fear of saying "I don't know" is a cause of lack of crucial conversation. Some wise person said "Ignorance is curable; stupidity, much less so."
Reply | Reply with quote | Quote
 
 
0 # Rohit Nayar 2013-03-20 04:44
How well said George. Its also a fact with most of the PMs in the system...
Reply | Reply with quote | Quote
 
 
0 # George Pitagorsky 2012-02-18 04:15
Yes, we can identify root causes (there maybe more than one). While projects are unique, there are sufficient similarities to be able to identify a common process, though with many variations. Failure factors are not necessarily unique just because each project is unique. Look at people, each one of us is unique, yet we are beset by common problems. The root causes of failure may very well be people, however, when he same issues arise over and over again, even when the people are different, seek to change the process.
Reply | Reply with quote | Quote
 
 
0 # Kristine Matt 2012-03-27 13:21
These failures in Communication, Portfolio Mgmt, Planning, Accountability, Absentee Sponsors, could be channeled and guided and in some cases, automated, to prevent things from slipping through the cracks. There are some really effective PPM solutions that keep progress flowing effieciently in the right direction. and a whitepaper on the Top 5 reasons PPM initiatives Fail, and how to prevent that. some of the reasons are related to the system. .... just an interesting perspective : )
Reply | Reply with quote | Quote
 
 
0 # Paul 2012-07-25 19:14
There are two kinds of project. Those that fail and those that re-baseline in time.
I've seen a project go 1000% over its original $30m budget and 2 years overtime and still be held up as a success.
Reply | Reply with quote | Quote
 
 
0 # SR Sarangi 2012-11-06 00:07
The reasons that I have seen too often are:
- Lack of Understanding the stakeholders and their requirements
- Absence of setting a project success criteria
- Misunderstandin g of the requirement (functional, non functional, Quality & Management)
- Improper change management and Quality of communication
Reply | Reply with quote | Quote
 
 
0 # Rohit Nayar 2013-03-20 04:42
Project and Programs fail mainly because of reasons as best known to me as below: -
1). No/lack of distinction between Program and Projects;
2). Program Governance
3). Program Planning and effective roll outs
4). Project Scheduling and effective planning
5). Projects rolling into the program following a separate
project specific escalation matrix and schedule.
6). Communication plans for both projects and the Program
level to be separate and scheduled with client team.
7). Budgets and planning of resource drilled down to the
project phase and not a consolidated program level plan

We normally end up giving the client a very scant picture of their environment and the proceeds within their system, the client team is normally not brought to speed with the technological aspects and complexities within their environment and are normally not informed about the more things that can be done in the system to bring down their cost and deliver with more control of their account, mainly because we would stand to lose the additional few thousands however we forget that with that loss we actually have an enhanced customer satisfaction and this customer first does not look out and also becomes a referral client for you in the market actually nullifying that nominal loss with higher returns through the other client's engagement and more market visibility.
Hope this does help someone somewhere...Pra ctice is what has to be done to see the results this is not just pure data centric however, more practice oriented approach.
Reply | Reply with quote | Quote
 
 
0 # Marcos Ferrer 2013-04-06 12:57
How can you have the right conversations when you don't even have a quality blueprint (requirements)?

We BAs agree that conversations are avoided - Here is the first one - one that you have never ignored, I am sure:

"The scope is off - we have to talk to the sponsors."

Where do you take this the first time it happens? The fiftteenth? I am curious, BA.
Reply | Reply with quote | Quote
 

Add comment