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, PMI-ACP, PMI-PBA, PMP

Questions can help move your project forward and solve issues. Sometimes, questions allow you to discover common ground or interest that will strengthen work relationships. But we need to be mindful with them.

I’ve recently thought about some of my experiences as a project manager. I’ve contributed to different teams, and I’ve led other teams. In both instances, I have the same doubt: Do I ask too many questions of them? I want to share some things I’ve learned about this over the years. If you’ve ever faced the same concern, keep these tips in mind.

1. Explain what motivates you to ask questions. You need to understand what motivates you to ask questions. Is it out of curiosity? Is it a way to build rapport with your teams? Is it because you anticipate questions other stakeholders will ask you? Is it part of your routine to check in with the team? Is it to solve a problem?

• If you are intellectually curious about their work, clearly state that. Then you can decide if you need training that can bring you more answers.
• If you want to build rapport, some team members expect you to ask questions not only about work, but also about family and important personal events (birthdays, weddings, etc.). For some colleagues, it is essential to know people personally to work with them—but others want to refrain from talking about these things.
• If it is your routine to check in, discuss that with the team.
• If you want to solve a problem, ask questions until you get to the root of the issue.
• Questioning is also a way to help people. Perhaps a colleague cannot verbalize issues that he or she faced, and by asking questions, you may understand that they need help.

Each of these reasons is valid, but you need to explain it to the team.

2. Keep the answers. In the rush, you may ask a question and get the needed answer—and then not document it. Then, one week later, you ask the same question. That can be interpreted as a lack of interest. If you have the answers, document them.

In uncertain environments, the same question can result in a different answer because some elements have changed. So you can say something like this: “I remember you told me that feature was going to be delivered Week X. Is that still the case?” You will show that you listened properly to the answer. If you don’t remember it, be honest about that.

And even if you explain your reasons for asking questions to your team members, don’t expect everyone to react similarly.

3. Observe behaviors and tailor your reaction. There are many reasons you might face difficulty with a line of questioning:

• Some people will be reluctant to answer some questions if they sense you want to micromanage them or control their actions.
• They may think it is a waste of time because the questions are outside your remit.
• Others may think you are intrusive and wonder why you need to know these answers.
• Some will interpret it as a lack of trust. It will also depend on whether you ask only some people rather than others.

On the other spectrum, some team members will view it as a lack of interest if you don’t ask them questions about their work. Don’t neglect the intercultural aspect, and the power dynamic you are in.

Responses will also depend on the number of questions you ask. Do you ask open or closed-ended questions? If each meeting comes across like a police interrogation, it will be unpleasant for team members.

And if you ask questions, do you allow people to ask them in return? You should allow some time for this, as they may be curious about what you’re doing. I once contributed to a project where I had many questions. I would have loved to ask the project manager, but I didn’t dare. To help make them feel more at ease, you can end your questions with an invitation: “Do you have any questions you’d like to ask me?”

And be careful that no question you ask comes across as hurtful. Even if a question is asked with good intent, it can still come across the wrong way (“That was with good intent” isn’t an excuse). Be careful with your words and tone.

What kind of experiences have you had with questions (on both sides)?

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

Since the start of the pandemic, changes in our ways of working, our ways of interacting, and with new technologies have accelerated. It's hard to keep up, and sometimes you plan to upskill—but you can’t find the time. Keep these three things in mind as you navigate our new normal:

1. Talk with people
Since 2020, I've been more engaged in communities: a marketing community, a project management community, and a coaching community. Each has its own rules of engagement. Some encourage one-to-one video calls—and that's the best way to push yourself to talk with people who may be of different academic backgrounds, work experiences and industries from yourself. Communities or professional associations (like PMI and its local chapters) can help you expand your network.

In addition, you can expand your network easily by reaching out and connecting with people after you take part in webinars or face-to-face events, or when you listen to a podcast you liked.

I also like to schedule informational interviews with people. The aim is to gather information about an industry, a role, and how people have gotten there. The aim is not to ask for a job or to send your CV. The interviewee must be open and share as much as they can. If you are the interviewee, don't expect the interviewer to ask you questions about what they don't know. Describe what you do, the diplomas or certifications in the field, and remove the local jargon.

You may think "people are too busy" to do this, but you'd be surprised by the number of helpful responses you get. After each informational interview, write down what you learned, and where you need to learn more; along with what you did and didn’t like about what you heard.

2. Be kind to yourself
It’s easy to blame yourself with negative thoughts like "I'm too slow" or "I don't know what I want." But for some people, it takes time to know what they do and don’t like, along with their strengths and how they want to have an impact. There are also personal and family constraints to consider.

So be kind to yourself and find a supportive network of friends so you can formulate the different steps and what you learned in the process.

I remember a colleague I talked with many years ago who wanted to change jobs. I met him a few months ago, and he told me with a shameful face, "After all of that, I didn't change." And that is okay. If the end result is no change, there is no shame because at least you took the time to explore new paths. You learned about yourself during the process, and you met new people.

Don’t compare yourself with others. That’s easier said than done, but remember that we all have different paths.

3. Go to a professional for help
As a project manager, you can work in different roles in the same industry or even transition to a new industry. Project management has transferable skills, but changing your industry may not be so easy. You may need to pave the path with certifications, diplomas, or online courses. Some options are risky for valid reasons. For example, I will not take the risk of managing a nuclear project (and would an employer trust me to do so when I’ve had no experience in that field?).

If you’re becoming too anxious or overwhelmed, or if you feel lost, seek professional help to get guidance to make sense of what you feel and want.

What other things do you recommend to help define your next career step as a project leader?

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

A few years ago, I replaced a contractor who was an expert in his field. We met once a week, and he answered my questions. But the domain was new to me. He was an expert, and I was not—so I thought it was normal that I didn't understand it.

He didn't write documents for me. So when he left, I spent difficult months catching up on things. Fortunately, I worked with a helpful technical expert. Then I wrote the necessary documents. We also developed a short training course. Since then, I have had to onboard colleagues, and I could use this documentation.

I belong to many teams at work (and in the volunteering setting), and I’d like to share some thoughts on how this kind of transition can be better handled. Let's call Moa, your new team member.

1. Think of the needs of the newbie. When you onboard someone new, you first need to understand what they need. This is not about you; this is about Moa. You need to take into consideration some questions:

a. Big picture vs. task only: Some people need to have the big picture to understand. Others need to understand only their sandbox.

b. Learning methods: How does Moa learn and memorize?

• Does he need to get documentation?
• Does he need to observe people at work?
• Does he need to talk with you regularly, in addition to documentation?

c. Learning rhythm: What is Moa’s rhythm to learn? I am a bit impatient and need to know what is expected from me from the outset. If I don’t know it, I become anxious. Sometimes I get feedback like “Relax! You have time.” It doesn’t reassure me. On the contrary, it makes me nervous and a bit upset because by these words, I feel like people are not listening to my needs.

d. Face-to-face meetings: If Moa is a remote team member, you’ll have to talk with his manager to plan a face-to-face meeting quickly after he joins. Perhaps a longer visit will be advantageous (and a great opportunity to gather the whole team together).

2. Define the best approach. Once you have had these first conversations, you can tailor an onboarding plan. Onboarding doesn’t stop the first week—it is a journey that can take several months and can take different forms:

• You can have weekly meetings
• You can invite Moa to your conference calls even if it isn’t directly linked to Moa’s role (and you can catch up afterward)
• You can send documents/information
• You can add Moa in the email loops and explain things

3. Demystify languages. You will also be Moa’s “translator.” The language of your team includes:

• Acronyms and vocabulary of the domain and organization
• Business language (for example, French business language is a mix between English and French)

These are the kinds of things you cannot get from training. Perhaps you have a glossary, or you can create one.

4. Uncover the unspoken rituals. When it comes to rituals, people often think of coffee breaks or after-work social gatherings. But rituals also encompass practical things about ways of working.

Perhaps Moa is more interested in those items than the coffee breaks. You can anticipate answering the following questions:

• What types of meetings do we have on the team?
• During the meetings, can questions be asked?
• Are the meetings recorded if I can’t attend?
• Are there minutes?
• How do we communicate?
• How are new ideas proposed?

5. Start early…and include everyone. With the overload at work and deadlines to catch up, your team member sometimes isn't in a hurry to train Moa. That doesn’t mean they don’t want to help him. But onboarding someone takes more time than expected.

We all manage things without writing them down. Or a process is written, but after a while, we adapt it without updating the written process. Because of that, a 30-minute conversation can last longer than expected. Moa may ask many questions, like me.

Welcoming a new member is not only the responsibility of the manager. It is even more important if Moa already works in the company. The onboarding process can start before with a handover period. Moa can begin to meet his colleagues and exchange with them.

Onboarding new members is a key process in the life of a team. It is an opportunity to strengthen ties, and also a learning opportunity for everyone.

What other things do you plan to onboard new team members?

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