Voices on Project Management

By Peter Tarhanidis, Ph.D.

Many leaders accept failure as part of their learning to enhance their future and mature outcomes. At the beginning of a new year, we must reflect on the past year’s successes and failures. Reflecting on project failures in 2024 offers leaders valuable insights to foster success in 2025. Understanding these challenges, supported by data and examples, is crucial for leaders aiming to enhance project outcomes in 2025.

Here are some notable quotes and perspectives on failure and resilience:

• Failure as the stepping stone to success: "Only those who dare to fail greatly can ever achieve greatly." — Robert F. Kennedy.
• The power of perseverance: "The secret of life is to fall seven times and to get up eight times." — Paulo Coelho
• The need to take risks: "Risk is not to be evaluated in terms of the probability of success but by the value of the goal." — Ralph D. Winter

Leaders should reflect on 2024 project failures with a focus on identifying root causes, assessing systemic issues, and implementing actionable lessons. Below are examples of challenges organizations and leaders faced or continue to struggle with:

1. Poor resource management: Inefficient allocation of resources led to project delays and budget overruns. TeamStage’s 2024 survey cites 60% of respondents identified poor resource management as their biggest challenge. Prosymmetry illustrates this impact; the Denver International Airport's automated baggage handling system faced severe delays and budget overruns due to inadequate resource allocation and management.
2. Lack of defined project management methodologies: The absence of standardized processes resulted in inconsistent project outcomes. Plaky’s 2024 survey indicates that 42% of project managers do not follow a defined project management methodology, making their projects 15% less likely to meet goals and stay within budget. Prosymmetry 2024 shares an example of when the Ford Edsel project failed due to the absence of a clear project management methodology, resulting in misaligned objectives and market misjudgment.
3. Unrealistic deadlines: Setting unattainable timelines leads to compromised quality and team burnout. Tempo 2024 states that 31% of project managers reported unrealistic deadlines as a top challenge. A key highlight noted by the Project Management blog is when the FBI's Virtual Case File project was abandoned after four years and $170 million spent, primarily due to setting unattainable deadlines that led to incomplete and faulty deliverables.
4. Insufficient budget: Unsurprisingly, underfunded projects struggled to procure necessary resources, affecting deliverables. Exploding Topics 2024 survey notes that 17% of project managers cited insufficient budget as a significant challenge. ProjectManager blog cites the California DMV's IT modernization project was canceled after $135 million was spent over nine years, largely due to chronic underfunding and budget mismanagement.
5. Poor project quality: Without the voice of the customer, deliverables failed to meet stakeholder expectations, necessitating costly revisions. This was noted by the Exploding Topics 2024 survey by 13% of project managers, who identified poor project quality as a major issue. ProjectManager blog notes the Healthcare.gov website launch in 2013 suffered from numerous glitches and downtime due to inadequate testing and quality assurance, leading to a poor user experience.

2025 Strategies to Ensure Success

1. Implement defined project management methodologies: Adopt a standardized framework like agile or waterfall to provide clear guidelines and improve project outcomes. Tempo 2024 confirms projects are 15% more likely to meet goals and stay within budget when following a defined methodology.
2. Set realistic deadlines: Engage stakeholders in setting achievable timelines based on resource availability and project scope. Leaders will reduce the risk of team burnout and maintain quality standards.
3. Ensure adequate budget allocation: Conduct thorough cost estimations during the planning phase to secure necessary funding. Leaders can prevent resource shortages and maintain project momentum.
4. Enhance project quality: Implement quality assurance processes and continuous improvement practices. Organizations can deliver products that meet or exceed stakeholder expectations, reducing rework.
5. Invest in resource management tools: Utilize project management software to optimize resource allocation and track progress. This will aid leaders in improving efficiency and in meeting project objectives.

By addressing these challenges with targeted strategies, leaders can build project maturity and drive more successful outcomes in 2025. What project challenges did you have in 2024, and what actions will you take to ensure success in 2025?

References

1. https://teamstage.io/project-management-statistics
2. https://www.prosymmetry.com/blog/4-famous-project-management-failures-and-what-to-learn-from-them
3. https://www.tempo.io/blog/failed-projects
4. https://plaky.com/learn/project-management/project-management-statistics
5. https://www.projectmanager.com/blog/failed-projects
6. https://explodingtopics.com/blog/project-management-stats

Kevin Korterud

Life is full of surprises…they always seem to show up unexpectedly. As project managers, we rely on our PMI certification training—as well as our experiences—to both detect and mitigate the effects from surprises, such as missed milestones, new regulatory requirements and quality issues.

But what happens when the surprise turns out to be a short-term outage of the project manager? This can come about for a variety of reasons, including family, health and other personal matters. A recent health issue that took me away from a project for a few weeks got me thinking about how to address this special type of surprise.

In my early career days on projects, the short-term loss of a project manager meant the project was typically put on hold until the PM returned. In today’s complex, high-speed technology delivery environment, stopping a project is less viable due to market needs, dependencies, specialized domain knowledge, engaged suppliers and many other factors.

So, in addition to all of the usual risk factors, one has to consider a risk mitigation plan for the project manager should a surprise occur (this plan also applies to other key roles such as the delivery, test and PMO leads).

Let’s look at a few questions to help you prepare for surprises when they occur to the PM role:

1. Who could be a backup PM? The process of finding a backup project manager usually falls into two categories: easy…and not so easy. If there are project track leads with prior PM experience, rank order them as to the size and complexity of the prior projects they have managed. Discuss the project(s) with them and create a plan for the areas that you look to build out as part of their duties in being a backup.

If nobody on your project has any prior PM experience, another option could be to consider an existing program management office lead. With today’s complex program office operations, it’s common to have program management office leaders with prior project management experience. They could assist as a backup PM.

2. When should you have a backup PM? As one never knows when surprises will occur, the best time to identify a backup project manager is during mobilization of the project. By having a person identified early in the project life cycle, it better positions the backup PM to be successful should a surprise occur.

If it’s not possible to identify and develop a backup at the start of a project, consider an approach that takes advantage of the upcoming or current phase of the project. For example, if the project is headed into the design phase, consider your functional lead as a potential backup. Just be cognizant of the additional burden the backup PM role places on an existing team member; consider additional program office resources to help with the execution of project operational processes.

3. How do you make someone a backup PM? After selecting a backup, create a list of topics to educate them in the many facets of the project. This can start with operational topics such as risk/issue reporting, status report and work planning, and cross-training. From there, they can start to be immersed in domain-related topics with the project (e.g., how does a month-end financial close work?). The domain-related topics may require some specialized training if they have not been exposed to them before.

Keep in mind that the backup PM still has their core project duties to execute, so they should not be overburdened with immersion activities. Keep the window for these activities to a few hours each week, and continue them through the life of the project. It is also helpful to bring the backup PM along to attend key project meetings to make them aware—as well as to make other project team members aware of their provisional role in the event of the unexpected.  

The days of having a project being placed on hold due to the short-term loss of a project manager are long behind us. In particular, with the highly integrated technology project ecosystem that exists today, the stoppage of one project can impact several others—thus affecting the overall progress of a company portfolio.

Knowing who your backup project manager is offers a mitigation path when surprises occur. In addition, it’s also an essential form of career building by exposing the backup PM to the next level of delivery stewardship.

How have you selected and groomed a backup project manager for your delivery efforts?

by Dave Wakeman

I was scrolling ProjectManagement.com recently, looking for inspiration and ideas for this month’s piece when I saw one author pose a question about “business context” and another one post about “business acumen.”

These got my attention, because over the years, my entire collection of posts has been about reinforcing these two points:

1. One, the business context matters.
2. Two, business acumen will make you a better project manager.

So this month, I want to reinforce the importance of your business skills to be a better project manager by highlighting two key ideas.

1. The best project manager can’t fix the wrong project. Peter Drucker said something about the worst waste of timing being doing something that need not be done at all.

One of the key ways that you can use your business skills to improve your PM performance is by understanding what projects are really going to push your business toward its key strategic goals.

This speaks directly to context. You get there with your business acumen.

Why does this matter? First, a lot of projects end up taking place due to momentum. A project starts gaining steam, no one steps in to ask if it is “essential.” It just seems important. So, it gets done.

Second, a lot of projects are done because that’s the way similar projects have been handled in the past. So, a project is just done because it is consistent with “best practices” even if there have been no lessons learned to update the process.

These scenarios highlight the importance of context and business acumen for PMs, because being able to step in and understand if a project is essential and impactful can stop the wrong projects from taking place.

2. Context is key in any situation. The best project manager in the world is still operating in a situation filled with context, no matter what.

The idea of any project, business or PM operating in a vacuum is funny, because nothing occurs in a vacuum. Great PMs know that context matters in every situation, and that context is fluid.

Andy Jordan recently wrote about there being “multiple” contexts, and that is right to a point, but it can be confusing to people. A good PM’s frame of reference for “context” in their projects revolves around the answer to the question of, “What does success look like?”

Why does this matter? One, we need to isolate the signal from the noise. I agree with Andy that there are multiple contexts for any project decision. Where I want you to focus your attention is on recognizing which one is most important.

In the modern business environment, you are never going to be able to manage all the contexts, so the process of isolation and focus matter more than ever.

So, look for the thing that is going to help you achieve “success,” whatever that means in your situation.

Two, the proper context should help you justify your project’s execution. Above, we discussed business acumen and the “right project.” Here is where context helps that come true because the context can change—and likely will change.

So, it is your job to make sure you know what success looks like so that you can place the project in the proper context to ensure that the right projects move forward.

Remember, the best project manager in the world can’t save the wrong project—and that’s where the meeting of business acumen and business context come together.

What do you think? Am I off the mark?

By Peter Tarhanidis, Ph.D.

There is a dramatic increase in the strategies corporations implement to meet the needs of their stakeholders. Driving value from all parts of an organization and its functions may seem like repetitive exercises—and even feel more like a medieval gauntlet with only a few successful programs. HBR (2021) wrote that by 2027, about 88 million people will be working in project management—with economic activity reaching $20 trillion USD. Also noted: Only 35% of projects are successful, leaving immense waste of resources.

There are many reasons projects fail. HBR (2021) states of the 70% of failed projects, and after exhaustive root-cause analysis across all industries, one can identify common themes such as undervaluing project management skills and methods, and poor performance. Yet organizations that apply project management methods recognized their performance had a 2.5 more times chance to be successful, and organizations can waste 28 times less resources. As such, when applied, the implementation of PM methods works.

Yet in a world filled with a variety of project taxonomies, many organizational boards are now contemplating the need to implement environmental, social and corporate governance (ESG) and corporate social responsibility (CSR) programs. Forbes states the benefits of ESG and CSR initiatives include:

1. Advancing organizational culture, empowering staff to do social good, and welcoming diversity.
2. Encouraging partners and investors who are interested in long-run strategy to manage risks and opportunities by emphasizing the organization’s ethics.
3. Raising an organization’s staff confidence and productivity, creating a workplace that achieves the business mission.

Therefore, to ensure success for ESG and CSR programs, an organization’s top leaders need to prioritize and align across all the organization’s businesses. Leaders can use the balanced scorecard to achieve this alignment, and can extend its use across the entire project portfolio.

This theory was developed by Kaplan and Norton, which state the balanced scorecard method converts the organization’s strategy into performance objectives, measures, targets and initiatives. Linking the concept of cause and effect, the balanced scorecard covers four perspectives:

1. Customer: How do customers see us?
2. Internal: What must we excel at?
3. Innovation and learning: Can we continue to improve and create value?
4. Financial: How do we look to shareholders?

Marr (N.B.) reported over 50% of companies have used this approach in the United States, the United Kingdom, Northern Europe and Japan. One clear benefit has been to align the organization’s structure to achieve its strategic goals.

In conclusion, applying project management methods and aligning an organization’s performance through the balanced scorecard can unlock ESG and CSR benefits that can supercharge a company’s efforts to achieve its mission.

References

1. HBR: The Project Economy Has Arrived
2. HBR: The Balanced Scorecard—Measures that Drive Performance
3. Project Management Statistics: Trends and Common Mistakes in 2023
4. Forbes: Three Reasons Why CSR And ESG Matter to Businesses
5. Balanced Scorecard: How Many Companies Use This To

by Dave Wakeman, PMP

On a recent visit to Reddit, I noticed a trend from some project managers—who were asking questions about how you can tell if your company is doing project management all wrong.

That got me thinking about some signs that an organization doesn’t have a healthy PM culture—and three big ones came to mind. Do you experience any of these where you work?

1. No idea why the role of project manager is key to a project’s success: I believe we’ve all been there—we see someone assigned as the project lead due to being in the wrong place at the wrong time.

Why do I say that? Because just throwing out the PM assignment is never a case of being in the right place at the right time.

This is truly the biggest warning sign that an organization isn’t project manager ready—they just have no definition of why the role of PM is so important to a project’s success.

Instead of having a clear expectation of the PM’s role with a defined process in place to help with achieving specific goals (including communication expectations, a definition of success, and an understanding of how the project ties into the organization’s strategy), the organization basically sticks its hand into a paper bag with pieces of paper, drawing one name out. (Or worse.)

Beware!

2. No clear definition of success: This one seems to take hold in a lot of organizations, and it is usually coupled with the impression that “I’ll know it when I see it.”

This kind of attitude almost guarantees failure. There are exceptions where a project comes together well without this definition in place—but that is very rare.

Why? Because without an understanding of what success looks like, any direction is a good direction.

This can be frustrating for all stakeholders, because when pressed for objectives or measures, a lot of time the feedback comes back as fluffy terms that aren’t related to the project’s success like “man hours,” “activities” or something else.

Bad project organizations judge success by “feel.” Good project organizations judge success with metrics.

That way, you can say, “We hit our target. Here is why…”; or, “We missed the mark. Here’s why, and here is what we can do to change it next time…”

3. No resource investment tied to specific projects: This is one I’ve been blindsided by in the past.

Why? Because I’ve fallen prey to the answer, “Whatever it takes!”

Trust me: “Whatever it takes!” is never actually “Whatever it takes!”

Organizations without a project culture underestimate the resources needed to make a project successful. This leads them to offer “commitments” or “promises.”

Most of the time, when a PM tries to cash in on those “promises” and “commitments,” it is impossible. The resources aren’t actually available.

This stands in contrast with an organization that is built for project management—where you have the scope, you know what success is going to look like, and you have a clear understanding of the resources that are going to be needed to hit the project’s objectives.

Does this mean that there are never changes or limits to the resources available? No. Not even close.

What this does mean is that a good project organization starts with some base level of commitment of resources, not just “commitments” and “promises.”

To me, every project requires these minimums from an organization in order to give success a chance:

1. An appreciation of the role of the PM. You are a leader, not a magician.
2. A clear definition of success, not just platitudes.
3. Resources. Maybe not everything I wanted, but more than “promises” or “commitments.”

I’m curious what things you have noticed that set an organization’s projects up for failure. Let us know in the comments below.