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 Marian Haus, PMP

Projects are rarely conducted in a vacuum. Whether the project you’re managing is small or large, simple or complex, you will most likely encounter dependencies tied to assets outside your project organization.

Here five simple steps to help you manage project dependencies that are spread across teams, departments and assets.

1. Assess and document potential project dependencies: Determine each dependency’s type, profile, specifications, timeline and owner. For example, you might have to rely on the QA or legal department to check your work, end-users to validate your product or other teams that will have to adapt their products because of your project’s outcome.

You could document HR dependencies in your project’s HR plan. Non-HR resources could be documented in a hierarchical resource breakdown structure (RBS). Or you could just use a simple spreadsheet, where you store all your dependencies organized by types, ownership, etc.

2. Align and interlock scope: Define a clear and determined purpose/scope for each dependency and align with the team providing or fulfilling it. Interlock your dependencies with the related teams or organizations.

For instance, if your project will need a certain setup from your company’s infrastructure team, ensure that you define the requirements (how many servers you need, what the technical specs are, what software needs to be installed, etc.). Finally, confirm that this setup can be delivered as requested.

3. Align dependency timelines: Specify exactly when your dependency is required and for how long. Interlock the timeline to secure its on-time delivery or availability.

To continue the previous example, you might request your company’s infrastructure team to deliver the servers no later than July 31 so you can use the setup during a testing period that would stretch from August 1 to September 30.

4. Monitor and control dependencies throughout the project: It will probably be impossible to precisely plan for all of your project’s dependencies from the very beginning—and then stick to that plan until project closure.

Therefore, you should maintain and review your dependencies list, HR plan or RBS throughout the project. New dependencies might show up while others might become dispensable.

5. Collect sign-offs: Sign-offs are as important as interlocks. You have to secure and collect them from your counterparts.

Interlocks enforce commitment, responsibility and accountability, whereas sign-offs confirm the delivery or the fulfillment within the agreed boundaries.

For instance, an end-user outside of your project team will sign-off on the product change your project generated, confirming that it conforms with his or her requirements or expectations. Or an interface project team will sign-off on your revamped software component, confirming that your project’s outcome did not break their related components or business processes.

How do you identify all of a project’s related dependencies? How do you manage them as the project progresses?