Show Notes
It is always difficult to be precise about the causes of project failure for a number of reasons. Our human inclination is to avoid any blame being attached to us, no matter how much we might proclaim the benefits of a no-blame culture, when it comes to our own career on the line, we don't want to stand up and take full responsibility for the failure ourselves. So clients will blame the project manager, the stakeholders will blame the business analyst for inadequate requirements, the project manager might blame the client for a poorly articulated business case but none of this helps to define the real cause of the failure.
Questionnaires can be used to gather information on the causes of project failure, but the questions are usually too general and the answers given to the questions are biased depending on the role the individual played in the project. There are also, frequently, several different reasons which contributed to the project failure so such questionnaires make it difficult to pinpoint the exact reasons for failure.
Add to this the fact that many projects are completely unique: with objectives, scope, technology etc that have not been experienced before and it is understandable that assessing the true reasons for project failure is extremely difficult. Nevertheless, if you take note of some of the reasons regularly cited for project breakdown they might help you to avoid disaster in your own projects.
The most commonly identified reasons are:
Deadline missed Budget exceeded Poor communication Requirements not met Inadequate quality of final product/service Poor planning with respect to risk management, estimates and schedule Poor client - supplier relationship Final deliverable not acceptable to the client Lack or professional / technical skills within the team Failure to manage client expectations or unrealistic expectations Poorly defined or incomplete requirements Frequent changes to requirements and/or specification Weak business case New technology did not live up to expectations No support from senior management No involvement from end-users Limited Resources Lack of focus on the business needs
Some of these reasons are the result of an underlying failure. For example, a poor client-supplier relationship is usually the result of poor communication or communication that lacks detail and fails to manage client expectations. A factor that could be improved by developing project managers via professional courses in project management.
And some of the reasons are not actually the reason for the failure but simply the outward manifestation of the project failure such as a deadline not being met. The reason the deadline was not met is actually the reason for the project failure and that could be any number of things such as failure to understand new technology, staffing issues, skills issues etc.
So if we accept that there are problems in genuinely determining why a project failed, we cannot fully understand the failure and so avoid making the same mistakes again. All the more reason why an experienced project manager is vital on major projects and why that person should have undertaken professional project management training. The experience will assist in avoiding problems that have occurred before and the training will provide the skills to deal with those problems that are unexpected and new to everyone.
So next time you are conducting, or involved in, a post-project review to analyse the causes of a project failure, try and look below the surface of the standard answers and resist the temptation to rush on to the next project and put the failure behind you. You just might learn a worthwhile lesson that could help you during your next project.
More from APM Project Management Training
What does it take to move from project manager to project leader? In this episode, Matt and Ruth at Parallel Project Training explores the shift from managing plans and processes to leading people, influencing others and making decisions under pressure. We discuss why the transition can be challenging, the habits that hold us back and how to build confidence as a leader. We also introduce our new Applied Project Leadership Programme, designed to help experienced project managers put leadership into practice now. To find out more about our leadership programme contact us at [email protected] or call on 0118 321 5030.
In this episode of the Parallel Project Training Podcast, host Ruth Phillips is joined by Becky Willmott, Senior Training Consultant, to discuss their career journeys in project management in recognition of International Women's Day and its theme, "Give to Gain." Becky shares how she entered project management through public procurement in the NHS, later moving into logistics and eventually becoming Head of a Project Management Office (PMO). The conversation highlights the wide variety of roles within project management, particularly the often-misunderstood role of the PMO. Rather than being purely administrative, PMOs provide vital support through governance, reporting, data analysis, and specialist expertise that enable project managers to deliver successful outcomes. Ruth and Becky also explore the different career paths within the profession, from project coordination through to programme and portfolio management. They emphasise that project management offers a dynamic, flexible and highly transferable career, with opportunities across many industries. The episode concludes with practical advice for anyone interested in starting or developing a career in project management, including gaining experience through workplace projects, exploring training and professional qualifications such as the APM Project Fundamentals Qualification, and taking advantage of networking opportunities within the profession. Finally, the discussion looks ahead to the future of project management, considering how AI may reduce administrative workload and allow project professionals to focus more on leadership, stakeholder engagement, and organisational change—while also creating opportunities for greater diversity in the profession.
15. Ethics, Compliance and Professionalism - This podcast discusses the ability to work consistently in a moral, legal and socially responsible manner, and covers: a) The importance of continuing professional development, which should cover both knowledge, skills and behaviours, and the individual's role in identifying and addressing their own competence gaps. b) Knowledge of the sources of specialist advice and standards that need to be adhered to. c) The impact of the legal and regulatory landscape on projects (such as the impact on working conditions, risk management, governance and sustainability).
14. Diversity and Inclusion - This podcast discusses the ability to build and maintain an inclusive environment that embraces a diverse culture, and covers: a) Knowledge of diversity, including characteristics which may cause a person to be treated less favourably, such as: age, disability, marriage and civil partnership, pregnancy and maternity, race, religion or belief, sex, and sexual orientation. b) Why incorporating diversity into all parts of a project, from team members to customers, is a factor in creating a positive working environment and the importance of embracing diverse thinking in teams as a means of generating innovative solutions. c) How conscious and unconscious bias can affect actions and how to treat people fairly, including adapting behaviours to support individuals' needs and facilitate their contributions.