Some projects are not worth rescuing or keeping alive, be courageous, be smart, and kill them
We’ve all been there. The project is a zombie. It has failed. It will not meet expectations. Everyone knows it. Yet no one dares to step up and kill it.
The 𝟳 𝗿𝗲𝗮𝘀𝗼𝗻𝘀 Why we tend to stick with failing projects:
I will argue that one of the most fundamental roles of a PMO (and of project portfolio management) is not just the ability to discern and prioritize the projects that promise the highest returns, but also the courage (and authority) to terminate those that do not meet strategic objectives.
Yet, this is rarely seen and done.
The obstination towards keeping bad projects alive ignores a fundamental principle of opportunity cost. Every moment and resource dedicated to these distressed projects is a moment not spent on new, potentially more lucrative ventures.
The consequences are far-reaching, encompassing not just financial losses but also detrimental impacts on team morale and the strategic misalignment of the organization's goals.
Recommended by LinkedIn
Here are 5 practical ways to avoid this trap:
Some projects are not worth saving. They stay alive because of inertia and because of other people's egos. They steal away resources from more promising projects.
As a PMO Head, a Senior Leader, or even as a PM, have the courage to embrace the difficult, yet essential practice of discontinuing projects when necessary.
Eric's Note:
Want to read all my best posts? Subscribe (for free) to my other Newsletter on Substack. Click here and See you there! 😎
Putting your success first Consultant, Project Manager Speaker, Author: Project Management Bootcamp: - A Step by Step Guide. Please follow the link below or go to your favourite online bookstore to find out more.
9moProbably the best approach is to build in go/no go points into the project's governance. Especially when supported by independent reviews such as the UK government's Gateway Reviews killing bad projects and revising ugly ones becomes normalised as simply the way we do projects. For more thoughts please follow the link on my profile page to the #Routledge website and have a free read of the first part of Project Management Bootcamp A Step-by-Step Guide or check it out on Amazon or other online booksellers.
Stop dreading your projects! I boost team skills and experiences to deliver visionary projects ::: 20+ years experience ::: executive insight ::: PMP, LSSBB, CCMP, GSC certified
9moGreat article, Eric Raza. This is one of the things that perplexes me, and I'm grateful for your list of reasons why projects carry on after they should have been killed. What is so surprising is that resources are always so strained, and yet these projects persist at abysmal paces. Thank you!
Founder / CIO / Senior IT consultant
9moVery few managers are considering that matter Anyhow, too much projects are kicked-off without any long term strategy
Helping B2B companies generate qualified leads and close more deals in 90 days using our client acquisition system | Without paid ads or referrals | Try out my free cold email course in the featured section👇🏾
9moExcellent analogy! It's crucial to assess projects thoroughly for growth opportunities.
Compliance Manager at Sologic LLC
9moAs an investigator, I have dealt with projects that weren't killed but should have been and a few that we told them to kill. Our role was to fully understand what went wrong and help establish actions to prevent future events. Typically projects that weren't killed ended up as monetary and/or reputational losses for the company. Often such projects were contracted using "Slideware Solutions" concocted by sales personnel without the appropriate inputs from the technical teams. Huge efforts were expended trying to preserve the company's reputation and deliver. The post-project support efforts tended to be just problematic. What is not spoken, and unmeasurable, is the cost to personnel in the form of stress, work-life balance and reputation. I remember one of the first projects that we recommended be killed very well. The company requested that the investigating team present our recommendations at a company-customer meeting; as the lead investigator, I got that pleasure. I found it very interesting that the key personnel on both sides were relieved by the recommendation. After the meeting, we found out that both sides recognized the need to kill the project but neither had the "guts" to propose it. Be brave.