Everyone has failed projects. We start big and hope for the best – kicking off the bright new project, only to run into problems along the way and the, sometimes 4-5 times out of 10 according to many surveys, something happens that either kills the project or ensures that it won't be considered much of a success by throwing it way off the timeline, budget or quality delivery. Or perhaps we just lose the customer's confidence and satisfaction level along the way. Any of these can result in a project being deemed less than successful.
I've considered my own PM past (and present), the experiences of my colleagues and observations I've made along the way...and below is my list of some of the top underlying reasons projects fail. Of course, there can and will be many others – many that have absolutely nothing with anything on this list or anything we have control over, but this is a solid list...in my opinion...of many key causes of project failures. Please consider your own list and share it.
I've considered my own PM past (and present), the experiences of my colleagues and observations I've made along the way...and below is my list of some of the top underlying reasons projects fail. Of course, there can and will be many others – many that have absolutely nothing with anything on this list or anything we have control over, but this is a solid list...in my opinion...of many key causes of project failures. Please consider your own list and share it.
Lack of funding. Everything fails from lack of funding. No money is no money, no matter what happens next. Without more money added to the Project or the delivery team agreeing to do work for free... no more forward progress can be made. More funding is needed. Customers don't like to hear that. I took over a very large technical implementation for a federal agency and it was already overbudget when I came on board. We never could recover and the end result was project cancellation. It was painful, but no more money is no more money.
Poorly documented or missing requirements. Requirements are the lifeblood of the project. If key requirements are missing or are not documented in enough detail then the chances you'll design the proper solution are slim... you'll be leaving success to luck and that's a bad place to be.
Lack of key skills or resources. Do you and your project team members have the right skills for the project? Many projects have failed when a team tries take on a project that the lack the experience or knowledge base for technically. Yes, you can learn along the way - that's how we grow professionally. But when the stretch is too big that's when we miss key requirements, create a bad design or go through expensive and time consuming re-work that can end up killing the project.
Communication breakdown. Communication is the very heart of successful project management. And by communication I mean good, effective, efficient communication. Speaking, listening, emails, meetings, etc. Everything that communication entails. If there is a breakdown in any of those communication, it can leave the project at risk. If meetings aren't happening or are poorly attended...that's can cause project failure. If the project manager to project team and vice versa communication is poor, that can definitely contribute to project failure as project tasks are not delegated properly and requirements are poorly communicated. If project team to project customer communication is poor that can definitely be a problem because that communication has to happen in order for requirements to be properly understood and interpreted, the customer is needed for input to decisions, and the customer is needed for weekly participation to ensure that progress is happening...and the right progress is happening...throughout the engagement.
Technology disconnect. If there is any technology aspect to the project and the tech solution misses the mark – that can be a project disaster. The final solution rolled out to the user community may be unusable. This goes back to not taking on a project that the project team is not technically ready to take on because failure is too likely of an outcome...leaving success to chance or luck is always a bad idea. If your organization and team are not ready for this technology, avoid proceeding.
Summary / call for input
Again, this is just my list from experience and observation. What's your list? Difficult customers? Change in direction from senior management? Everyone's had at least one project failure (if they care to admit it)...what caused yours?
Poorly documented or missing requirements. Requirements are the lifeblood of the project. If key requirements are missing or are not documented in enough detail then the chances you'll design the proper solution are slim... you'll be leaving success to luck and that's a bad place to be.
Lack of key skills or resources. Do you and your project team members have the right skills for the project? Many projects have failed when a team tries take on a project that the lack the experience or knowledge base for technically. Yes, you can learn along the way - that's how we grow professionally. But when the stretch is too big that's when we miss key requirements, create a bad design or go through expensive and time consuming re-work that can end up killing the project.
Communication breakdown. Communication is the very heart of successful project management. And by communication I mean good, effective, efficient communication. Speaking, listening, emails, meetings, etc. Everything that communication entails. If there is a breakdown in any of those communication, it can leave the project at risk. If meetings aren't happening or are poorly attended...that's can cause project failure. If the project manager to project team and vice versa communication is poor, that can definitely contribute to project failure as project tasks are not delegated properly and requirements are poorly communicated. If project team to project customer communication is poor that can definitely be a problem because that communication has to happen in order for requirements to be properly understood and interpreted, the customer is needed for input to decisions, and the customer is needed for weekly participation to ensure that progress is happening...and the right progress is happening...throughout the engagement.
Technology disconnect. If there is any technology aspect to the project and the tech solution misses the mark – that can be a project disaster. The final solution rolled out to the user community may be unusable. This goes back to not taking on a project that the project team is not technically ready to take on because failure is too likely of an outcome...leaving success to chance or luck is always a bad idea. If your organization and team are not ready for this technology, avoid proceeding.
Summary / call for input
Again, this is just my list from experience and observation. What's your list? Difficult customers? Change in direction from senior management? Everyone's had at least one project failure (if they care to admit it)...what caused yours?
RSS Feed
