Voices on Project Management

by Peter Tarhanidis, Ph.D.

Today’s hybrid work environments, ethical demands, stakeholder complexity, and organizational pace require new success criteria. According to PMI’s 2024 Pulse of the Profession report, only 34% of projects are considered successful by traditional measures of scope, time and cost. For leaders to thrive in this new reality, project guardrails must be modernized to inspire autonomy while aligning purpose, ethics, and sustainable outcomes.

Rethinking Guardrails: From Control to Catalysis
Traditional project governance structures emphasize compliance, change control, and rigid escalation paths. But in environments characterized by complexity, ambiguity, and constant change, rigid control can undermine innovation and engagement.

McKinsey & Co.’s research shows that projects with adaptive governance outperform peers by 25% in delivery of value and 30% in stakeholder satisfaction. Leaders must introduce guardrails that promote empowered decision-making within clearly communicated boundaries, and encourage distributed leadership and agility without sacrificing accountability.

5 New Guardrails for Today’s Project Leaders

1. Value Over Output: PMI’s 2023 Global Megatrends shows organizations that prioritize value over delivery metrics achieve a 42% higher rate of strategic goals. Teams that connect features to customer outcomes develop deeper alignment with mission and increase stakeholder confidence. These leaders define value-centric KPIs rather than milestone attainment.
2. Ethics Over Expediency: Edelman’s 2024 Trust Barometer indicates 71% of employees expect their companies to take a public stand on ethical issues, expect their leaders to anticipate unintended consequences, and apply ethical analysis into key decisions. Ethically governed projects report 30% fewer incidents of rework and stakeholder backlash (MIT Sloan Management Review, 2023). Empowered teams build a culture of integrity and long-term resilience. These leaders add ethical risk as part of project risk registers, ethical checklists and stakeholder impact maps.
3. Psychological Safety Over Hierarchical Control: Harvard Business School’s Amy Edmondson shares teams with high psychological safety are 27% more effective in cross-functional collaboration while enabling openness, faster error detection, and greater innovation. Projects with psychologically safe environments complete 18% faster and report 35% greater team engagement (Google’s Project Aristotle). Team members are more likely to raise early red flags and offer solutions without fear of reprisal. These leaders model curiosity, not criticism. Shifting to questions such as “What can we learn?” versus “Who’s accountable?”
4. Agility Over Certainty: Only 16% of organizations report that traditional planning methods are effective in today’s fast-paced environment (PMI, 2024). Agile projects are 2.5 times more likely to succeed than waterfall counterparts in dynamic sectors like tech, finance and healthcare (Standish Group CHAOS Report, 2023). Teams working in short feedback loops are more responsive to customer needs and regulatory changes, resulting in better user adoption. These leaders use rolling-wave planning and commit to decision-making during sprint steering reviews.
5. Stakeholder Integration Over Stakeholder Management: The modern stakeholder is no longer a passive recipient but an active participant. Projects that actively engage stakeholders experience 29% fewer change requests and 41% greater satisfaction scores (IBM Business Value Institute, 2023). When stakeholders are engaged early, then resistance turns into advocacy. These leaders manage stakeholders by listening and integrating their inputs. Use stakeholder empathy interviews and involve them in prototype testing or solution design.

Making Guardrails Operational
Putting these principles into action requires a shift in mindset and structure. Here are five ways to support your practice:

1. Formalize guardrails. Document in project charters and playbooks the team norms, governance models, and onboarding practices.
2. Measure guardrails. Use KPIs like Net Promoter Score, stakeholder sentiment, innovation speed, and compliance metrics.
3. Empower coaches and champions. Appoint internal coaches or culture champions to reinforce these behaviors during stand-ups, reviews, and retrospectives.
4. Build guardrails into decision trees. Create frameworks where teams can operate with autonomy while escalating only when critical guardrails are approached.
5. Conduct quarterly guardrail health checks. Conduct quarterly “guardrail health checks” to audit, reflect and adapt. Use team surveys and external facilitators to refine policies and culture.

Conclusion
Now more than ever, project success requires leaders who can lead with precision and principle. This requires one to balance execution with empathy, speed with substance, and strategy with stewardship. The new project guardrails of value, ethics, safety, agility and integration do not constrain; rather they are cultural enablers that empower high-performance delivery within purpose-driven boundaries. These guardrails provide structure for leaders where trust replaces control, adaptability replaces rigidity, and purpose becomes the new metric of success.

What actions will you take to ensure guardrails turn from control to catalysis?

References

1. Pulse of the Profession: The Future of Project Work, PMI (2024)
2. Unlocking the Power of Agile Governance, McKinsey & Company (2023)
3. Creating a Culture of Psychological Safety, Harvard Business Review (2023)
4. CHAOS Report: Project Success Rates, Standish Group (2023)
5. The Stakeholder Experience Advantage; IBM Business Value Institute (2023)
6. Trust Barometer: Expectations of Ethical Leadership, Edelman (2024)
7. Ethical Decision-Making in Fast-Paced Projects, MIT Sloan (2023)

By Yasmina Khelifi, PMP, PMI-PBA, PMI-ACP

A few weeks ago, I lost my voice entirely for two days. It finally came back, but I had to wait a few weeks for it to regain its strength.

It was an unpleasant experience on a personal level. I had to use an old slate, a pen, and an eraser to communicate with my family and other contacts. I became aware that my daily environment was not suitable for people who did not speak.

However, it was also an enlightening experience at the professional level. I had to take sick leave for two days because I was not able to work without a voice.

I wrote emails, messages and texts to move projects forward, but I missed being able to use the power of my voice. Electronic communication methods are not enough.

As a project leader, you need to connect, explain, help, negotiate, organize, collaborate and brainstorm. But you also need to listen. I also realized that I spoke too much during conference calls and sometimes had to repeat myself.

The voice translates our inner state, even if we are not conscious about it. We have all experienced team members saying, “I’m fine” with a big smile, but we felt it was not true.

I work most of the time with no videos, and thanks to the international background I work in, I have learned to listen to the hesitations, the “yes” that means “no,” the pauses that indicate a need for help. Smiles can also be “heard” through the phones even if there is no video.

Having a voice is also about learning how to use it. We are so familiar with the sound of our own voices that, for most people, it’s hard to listen to their own voice. But I encourage you to do it. When I began producing podcasts, I had to listen to each entire episode several times to edit it. I heard my voice, and I was surprised—I had spoken too fast, with too much energy, and sounded like I was giving orders. This also explained why, at the beginning of my career, a colleague (politely) told me, “Don't give me any orders.”

My next step is to take vocal training with a coach to learn more about it.

The voice is a fragile muscle: you need to respect it and protect it.

When you have a voice, activate it! Don't shut up, but listen.

How do you use your voice as a project leader?

by Dave Wakeman

My editor asked me about a post I wrote 10 years ago, looking at how to build winning teams on the court and off.

“Let’s bring back March Madness!” he said.

I aim to please.

So, on the eve of the 2025 NCAA Final Fours for men and women, let’s go back to the locker room and see what coaches and project managers have in common when they build winning teams.

1. Establish a culture
I attended the University of Alabama, which I have discussed before. I’ve written often about my respect for football coach Nick Saban, and translated some lessons from his success into project management terms.

Now, Saban has retired. His culture was one of precision, hard work, and constant improvement. But that doesn’t mean Alabama doesn’t have coaches to respect and learn from. We have many.

Nate Oates is the men’s basketball coach, and Kalen DeBoer is the football coach. Both focus on establishing culture in their programs.

• For the basketball team, it is about being gritty. Coach Oates calls it “hardhat basketball.”
• Coach DeBoer has talked about having a “player-led” culture that he believes gives the team extra incentive to buy in.

The two approaches are different, but they teach us one important lesson: The best teams have an identity, something that provides a framework for how they approach their jobs.

This same idea applies to project teams. Projects often deal with turbulence, change and adversity, just like on the court or the field.

2. Handle change, adapt quickly
Going back to Alabama. When I was in school, making the Sweet Sixteen was a huge victory. Last season, Alabama made its first Final Four. This year, we’ve been in the Top 10 all year.

Besides bragging, one thing I’ve learned is that the NCAA tournament is about adjustments and being able to react quickly. How do I mean?

Because of the compressed nature of the tournament, if you make a long run, you play games quickly. You might be selected on Sunday and have your first game on Thursday. Win and you have a day to prepare for a team you may not know anything about for the game on Saturday.

That pattern can repeat three times if you make the Final Four.

It happens even more when you factor in the conference tournaments that might make a team play three or four days in a row. Or even more: Last year, NC State was in danger of not making the NCAA tournament. It won five games in five days (!) at the ACC tournament, automatically qualifying for NCAAs. After just four days of rest, the team won four more games in the NCAA tournament and advanced to the Final Four before losing. (And if you have to play in the First Four, the schedule is even more compact.)

The lesson: You must adapt and change quickly.

That’s true for PMs as well.

A change order pops up.

You might lose access to resources.

A team member may be called away or get stretched in multiple directions.

On and on.

You must adapt and adjust to keep your project on track. Just like a team in the tournament.

3. Find a way
Teams that win the championship must find a way to win.

The only team I remember not having a close call at any point in the men’s tournament was the 2018 Villanova Wildcats. The closest games they played were two that they won by 12. (My wife doesn’t let me forget that season.)

Most teams that make a championship run face adversity. They must find a way to overcome challenges, injuries and other obstacles.

Project teams must find ways to complete jobs as well.

You may have a budget cut.

You may get a schedule change.

There are always change orders.

You might change team members during the project.

Who knows?

You work on enough projects; you see all kinds of crazy things happen. The key thing is that you find a way to bring the project home.

That’s what good teams do.

That’s what good project teams do.

Two questions for you in the comments:

1. Who are you cheering for at the men’s and women’s Final Four?
2. How do you make sure your team is ready to win?

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

By Soma Bhattacharya

What ways can you inspire a team to stay motivated or perform better to minimize losses? Better focus or more time on details can reduce incoming defects or even breakage.

That’s easier said than done. Getting and keeping the team motivated is no easy feat when the same group has been working together for a while.

So, instead of the regular reports or team meeting agenda, try out different information that might result in the required change. That’s enough to trigger a discussion.

Here’s something to think about in trying to improve team efficiency. We didn’t look at individuals, since we always look at the combined team effort. We looked at the input versus the output differently. The hours worked by the team for a sprint, month or quarter led to the input; and the features or potentially shoppable product led to the output. But we brought in another dimension often forgotten: the impact and usage of what was delivered, the defects that came in, and if any breakages happened. That gave the team something to think about; it just wasn’t the count of user stories or features that went out last quarter, but also how that was used by the clients. What was the adoption rate? How was the flow?

These are just the basics, and I am pretty sure some of you reading this might have tried more inputs, more data points, and have a better understanding of metrics for the team. 

What I found was that by changing up the parameters in what goes into the teams working together, the discussions can always be better. Conduct something like a simple theme-based, goal-based discussion on how to reduce the support tickets by just 1% every month. What would it take?

How you have been able to keep your team motivated?