Sitting in my pajamas with a cup of coffee, I was ready to hit enter on a LinkedIn post stating that we need to stop spreading the false notion that only 35% of projects are successful. As I was about to press send, I realized this needed more discussion and thought before being shared. Therefore, let’s start by putting an end to this myth. Yes. This is a myth.
It is silly.
Whenever I see an infographic on social media or a consultant using this number (or something similar, as the number commonly ranges from 30-35%) as a reason to justify their thought leadership, training, services, etc. I immediately think of the Ambulance chaser attorneys who feed on accident victims. “If you have been injured in an accident, call so and s, law firm. All I do is win and get you the money you deserve!” Now for my international colleagues, this is a phenomenon that every mid to major city in the US has. Their ads clog up our televisions and roadside billboards Their ads look something like this.
Why am I so adamant about putting this silly notion to rest?
A few reasons:
- It is virtually impossible to accurately measure the success or failure of projects across the globe.
- Factors like culture, economic conditions, access to resources and political instability can greatly affect project outcomes, making it difficult to draw meaningful conclusions from global data, assuming you could harness it all.
- Different organizations have different definitions of what constitutes “success” – time, cost and scope are common criteria for measuring project success, but customer satisfaction, innovation, or impact may also be considered.
Where does this come from? The Standish Report.
The Standish Group’s report on project failure rates is often cited as the most reliable source of information, however, there are several reasons why it may not be accurate. Here are six points to consider when evaluating the Standish Report:
- The report does not take into account the complexity of projects. Projects with more complex requirements and longer timelines have a higher risk of failure, yet the report does not differentiate between these types of projects.
- The report does not consider the impact of external factors such as changes in technology or economic conditions that could affect a project’s success rate.
- The report relies heavily on self-reported data from organizations, which can be unreliable and biased.
- The report does not take into account the quality of project management practices, which can significantly influence success rates.
- The report only looks at IT projects, so it cannot provide an accurate picture of overall project failure rates across industries and sectors.
- The report has not been updated since 2015, so it may no longer reflect current trends in project success and failure rates.
Read the print below the figures. “The percentage of projects that were OnBudget from FY2011-2015 within the CHAOS database. A sample size of 300 does not make a global benchmark. Our studies on climate change impacting projects took data from 30,000 inputs and that is still a drop in the bucket.
Think about it for a moment
Do 65% of your projects fail to meet objectives? I used to track project success against the triple constraint and in my projects, and for a ten year span, projects I managed had a 93% success rate. Am I an exceptional project manager? Well… of course. [kidding]
Does the collective of project management only succeed 35% of the time? Maybe, maybe not. We simply can’t quantify it. There are too many variables.
Despite the complexity of different variables in each individual project, it is undeniable that failure rates exist. Organizations and businesses should take the initiative to analyze their own projects so they can learn from past mistakes, identify areas for improvement, and move forward more strategically.
I am going to go back and enjoy my coffee. Feel free to comment. I would love to have your thoughts on this.
Clef two-factor authentication
Hi Joel, Great post! Neither on budget, nor on time or on target are real percentages due to many lacks when organizations send their figures about IiT projects, to the Standish group. I have sent to them between 2006-2012 many figures related to my former IT company successful projects, or waiting for a probably failure, but their two or three constraint considerations for statistics were weak. I have renounced by those times to send reports. Anyhow, the quality of the output product, customer satisfaction, percentages of contingency or management reserve used in projects, real acquired outcomes from the product utilisation, and expected benefits met or not, final impact on the environment etc., and many other requests for real statistics are usually not presented in many statistics about successful or failed projects, even for megaprojects. More deeper considerations should be set up, probably in a dedicated manual for project performance reporting.