The Critical Path – Project Management & Leadership in Complex Environments

Why mentoring is essential for professional growth and leadership development.

Great leadership is not developed through experience alone. It grows through learning, reflection, feedback and the guidance of others.

In this episode of The Critical Path, we explore the importance of mentoring in professional development, particularly for project and programme managers who must navigate complex decisions, challenging stakeholders and demanding leadership situations.

Drawing on research and real-world examples, we discuss the benefits of mentoring, how to find the right mentor and how to build a productive mentoring relationship. We also explore the value of shadowing experienced leaders, learning through observation and using those experiences to develop better judgement and leadership skills.

Importantly, mentoring is not just for junior professionals. Regardless of our experience or seniority, there is always something new to learn, and mentoring can work both ways.

Professional growth is a continuous journey. The right mentor can help us challenge our thinking, accelerate our learning and become more effective leaders.

Key references:

1. Eby et al. (2008) — Does Mentoring Matter? A Multidisciplinary Meta-Analysis Comparing Mentored and Non-Mentored Individuals.

2. Allen et al. (2004) — Career Benefits Associated with Mentoring for Protégés: A Meta-Analysis.

3. Elmi et al. (2026) — The Comprehensive Evidence on the Effectiveness and Experiences of Mentoring Programmes for Managers in Healthcare.

4. Nicolini and Korica (2024/2025) — Structured Shadowing as a Pedagogy.

5. National Academies of Sciences, Engineering, and Medicine (2019) — The Science of Effective Mentorship in STEMM.

6. Association for Project Management (2026) — Thinking About Finding a Mentor in the Project Profession?

7. UK Civil Service (2022) — Reverse Mentoring from Two Perspectives.

8. NASA APPEL Knowledge Services (2026) — PM Bridges Mentoring Program.

Delivering a project on time, within budget, and to the required quality does not necessarily mean it has achieved its intended benefits. Too often, organisations celebrate project completion without demonstrating whether the investment has delivered meaningful, measurable value.

In this episode of The Critical Path, we explore the importance of benefits realisation and why it should be a fundamental part of project governance, from the initial business case through implementation and beyond project closure.

Drawing on established project management frameworks, research, and real-world examples, we discuss the difference between outputs, outcomes, and benefits, the importance of establishing measurable baselines, assigning clear accountability, and monitoring performance after delivery.

We also examine why organisations struggle to realise promised benefits and share practical strategies to ensure projects deliver lasting improvements for businesses, stakeholders, and society.

Because project success isn't just about what we deliver. It's about the value we create.

Key references:

• APM — Benefits Management and Project Success (Body of Knowledge, 8th edition).

• National Audit Office — Delivering Value from Government Investment in Major Projects (2024).

• HM Treasury — The Green Book (2026), and Digital and Data Benefits Framework (April 2026).

• National Audit Office — Realising the Benefits of St Helena Airport: A Progress Update (February 2025).

• UK Government — Microsoft Copilot Cross-Government Findings (2025) and HMRC Evaluation (July 2026).

In Episode 40 of The Critical Path, we explore why emotional intelligence is such an important part of effective leadership.

Leadership is not only about making decisions, managing schedules, controlling risk or delivering results. It is also about understanding people, including yourself.

This episode looks at the key elements of emotional intelligence: self-awareness, self-management, empathy and relationship management, and how they influence the way leaders respond to pressure, conflict, bad news and difficult conversations.

We also explore the importance of creating an environment where people feel able to challenge decisions, raise concerns and communicate problems early.

Emotional intelligence does not replace technical competence, accountability or good judgement. Instead, it helps leaders use those capabilities more effectively.

The key message is simple: recognise your emotions, understand the emotions of others, and choose your response rather than simply reacting.

Key references:

1. Gerhardt, K., Bauwens, R., & van Woerkom, M. (2025). Emotional Intelligence and Leader Outcomes: A Comprehensive Review and Roadmap for Future Inquiry. Human Resource Development Review.

2. Paredes-Saavedra, M., Huanca-Cruz, J. M., Mamani-De la Cruz, Z. R., Calsin-Pacompia, J., & Morales-García, W. C. (2026). Emotional Intelligence, Transformational Leadership, and Team Effectiveness: A Systematic Review and Correlational Meta-Analysis. Administrative Sciences, 16(3), 116.

3. Gaur, V., & Vallabh, P. (2026). Emotional Contagion in Virtual Leadership: A Webcam-Based Study of Expressivity, Psychological Safety, and Team Output. Acta Psychologica, 264, 106488.P

4. Kawashima, T., Ota, Y., Aikawa, G., Watanabe, M., Ashida, K., & Sakuramoto, H. (2025). Effectiveness of Emotional Intelligence Training on Nurses' and Nursing Students' Emotional Intelligence, Resilience, Stress, and Communication Skills: A Systematic Review and Meta-Analysis. Nurse Education Today, 151, 106743.

5. Mayer, J. D., Salovey, P., & Caruso, D. R. (2004). Emotional Intelligence: Theory, Findings, and Implications. Psychological Inquiry, 15(3), 197–215.

6. Edmondson, A. C. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383.

7. Microsoft / Satya Nadella. Recommitting to Our Why, What, and How (2025), together with Microsoft's material on empathy and innovation.

In this episode of The Critical Path, we explore the role of lessons learned in project management and how they differ from individual feedback.

While feedback helps people improve, lessons learned operate at a wider level — helping teams, projects and organisations understand what worked, what did not, and what should change in the future.

The episode looks at why lessons-learned processes often fail, particularly when organisations wait until project closure, create environments where people are reluctant to speak openly, or simply document lessons without applying them.

We also explore the value of structured after-action reviews and the importance of asking four simple questions: What did we expect? What actually happened? Why was there a difference? And what should we do differently next time?

The central message is simple: a lesson is not truly learned until it changes future behaviour, decisions, processes or ways of working.

Key references:

1. Annabi, C. A., Badman, J. P. M., & Said, A. M. (2025). A Scoping Review on Project-Based Organization’s Knowledge Transfer Using the Systemic Lessons Learned Knowledge (Syllk) Model as an Interpretative Structural Model. Electronic Journal of Knowledge Management.

2. Tannenbaum, S. I., & Cerasoli, C. P. (2013). Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis. Human Factors, 55(1), 231–245.

3. Ajmal, M. M., & Koskinen, K. U. (2008). Knowledge Transfer in Project-Based Organizations: An Organizational Culture Perspective. Project Management Journal, 39(1), 7–15.

4. NASA — Lessons Learned Information System (LLIS).

5. NASA APPEL Knowledge Services — Lessons Learned.

6. NASA/JPL (2012). Closed-Loop Infusion of Lessons Learned into Center Procedures & Training. NASA Lesson Learned No. 6856.

7. U.S. Government Accountability Office (2010). Defense Acquisitions: Strong Leadership Is Key to Planning and Executing Stable Weapon Programs — GAO-10-522.

In Episode 38 of The Critical Path, we explore why honest, constructive feedback is one of the most important tools in leadership, project management and professional development.

Good feedback helps people identify blind spots, understand where performance can improve and turn experience into learning. But feedback is not automatically effective. Poorly delivered feedback can create defensiveness, while specific, timely and actionable feedback can help individuals and teams improve.

The episode looks at the difference between criticism and constructive feedback, why feedback should focus on behaviours rather than personality, and why leaders should create environments where people feel comfortable both giving and asking for feedback.

We also explore how feedback operates beyond the individual supporting stronger teams, better project delivery and organisational learning through practices such as debriefs and After Action Reviews.

The key message is simple: feedback should not be a judgement of who someone is. It should be useful information about where they can improve next.

Key references:

1. Anseel, F., & Sherf, E. N. (2025). A 25-Year Review of Research on Feedback in Organizations: From Simple Rules to Complex Realities. Annual Review of Organizational Psychology and Organizational Behavior, 12, 19–43.

2. Hao, S., Song, L. J., Mostafa, A. M. S., Han, P., & Wang, Q. (2026). When does negative feedback promote or undermine employee learning? The interpersonal mechanism of goal-driven help-seeking. Journal of Occupational and Organizational Psychology, 99(2), e70118.

3. Kluger, A. N., & DeNisi, A. (1996). The effects of feedback interventions on performance: A historical review, a meta-analysis, and a preliminary feedback intervention theory. Psychological Bulletin, 119(2), 254–284.

4. Edmondson, A. C. (1999). Psychological Safety and Learning Behavior in Work Teams. Administrative Science Quarterly, 44(2), 350–383.

5. Tannenbaum, S. I., & Cerasoli, C. P. (2013). Do Team and Individual Debriefs Enhance Performance? A Meta-Analysis. Human Factors, 55(1), 231–245.

6. Feedback Orientation: A Meta-Analysis (2023). Human Resource Management Review, 33(4), 100986. This meta-analysis included 46 independent samples and 12,478 workers.

7. U.S. Army Training Management Directorate (2025). TC 7-0.1: After Action Reviews.

Episode 37 of The Critical Path explores conflict management as a core leadership skill in complex organisations and programmes.

Conflict is normal wherever people have different responsibilities, priorities, incentives and perspectives. The episode explains the difference between task, process and relationship conflict, and why even useful technical disagreement can become damaging when it turns personal.

The central message is simple: don’t react immediately — read the conflict first.

Using the PAUSE framework — Pause, Assess, Understand, Select your response, Engage and close — the episode provides a practical method for handling difficult situations more deliberately. It also examines the importance of emotional regulation, active listening, psychological safety, clear decision rights and choosing the right conflict-management approach for the situation.

Using the Space Shuttle Columbia investigation as a real-world example, the episode highlights why organisations need environments where concerns can be challenged, escalated and resolved without allowing schedule pressure, hierarchy or poor communication to suppress important disagreement.

Ultimately, effective leaders do not try to eliminate conflict. They create the conditions for constructive challenge, better decisions and stronger working relationships.

Key references:

1. de Wit, F. R. C., Greer, L. L., & Jehn, K. A. (2012). The paradox of intragroup conflict: A meta-analysis. Journal of Applied Psychology, 97(2), 360–390. DOI: 10.1037/a0024844.

2. Yu, J., & Wei, X. (2025). Whether and when team task conflict and relationship conflict transform over time: A meta-analysis based on cross-lagged panel model. International Journal of Conflict Management, 36(2), 452–479. DOI: 10.1108/IJCMA-09-2024-0238.

3. Sawhney, G., McCord, M. A., Cunningham, A., Cook, P., Adjei, K., & Flinn, T. (2026). A meta-analytic review of 60 years of role stressor research. Journal of Vocational Behavior, 167, 104234. DOI: 10.1016/j.jvb.2026.104234.

4. Kluger, A. N., Lehmann, M., Aguinis, H., Itzchakov, G., Gordoni, G., Zyberaj, J., et al. (2024). A meta-analytic systematic review and theory of the effects of perceived listening on work outcomes. Journal of Business and Psychology, 39, 295–344. DOI: 10.1007/s10869-023-09897-5.

5. Frazier, M. L., Fainshmidt, S., Klinger, R. L., Pezeshkan, A., & Vracheva, V. (2017). Psychological safety: A meta-analytic review and extension. Personnel Psychology, 70(1), 113–165. DOI: 10.1111/peps.12183.

6. Diefendorff, J. M., Niven, K., & Ong, X. W. (2026). Emotion regulation at work: A social perspective. Annual Review of Organizational Psychology and Organizational Behavior, 14. DOI: 10.1146/annurev-orgpsych-040425-085347.

7. Fabiansson, E. C., & Denson, T. F. (2012). The effects of intrapersonal anger and its regulation in economic bargaining. PLoS ONE, 7(12), e51595. DOI: 10.1371/journal.pone.0051595.

8. Columbia Accident Investigation Board (2003). Columbia Accident Investigation Board Report, Volume I. Washington, DC: NASA/Government Printing Office.

Episode 36 of The Critical Path, “Leadership Lives Everywhere: Agile Leadership Beyond Command and Control,” explores what agile leadership really means in complex project environments.

The episode argues that agile leadership is not about removing leadership or giving teams unlimited freedom. Instead, it is about adapting leadership style to the situation, creating clear goals and boundaries, developing capable teams, and moving decision-making authority closer to the people with the best knowledge. It looks at the balance between autonomy and governance, the importance of transparency, accountability and psychological safety, and why leadership should emerge throughout an organisation rather than remain concentrated at the top.

Using Ericsson’s agile transformation as a real-world example, the episode shows that autonomy works best when supported by alignment, coaching and shared direction. The central takeaway is simple:

Don’t try to make every decision. Build an organisation capable of making good decisions without you.

Key refrences:

1. Agile Business Consortium — AgilePM®: Agile Project Management Reference Book, Version 3

2. Agile Business Consortium — The Nine Principles of Agile Leadership

3. Beck, K. et al. (2001) — Manifesto for Agile Software Development and its Principles

4. Schwaber, K. & Sutherland, J. (2020) — The Scrum Guide

5. Edmondson, A. C. (1999) — “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly, 44(2), 350–383.

6. Lee, A., Willis, S. & Tian, A. W. (2018) — “Empowering Leadership: A Meta-Analytic Examination of Incremental Contribution, Mediation, and Moderation,” Journal of Organizational Behavior, 39(3), 306–325.

7. Wang, D., Waldman, D. A. & Zhang, Z. (2014) — “A Meta-Analysis of Shared Leadership and Team Effectiveness,” Journal of Applied Psychology, 99(2), 181–198.

8. Paasivaara, M., Behm, B., Lassenius, C. & Hallikainen, M. (2018) — “Large-scale Agile Transformation at Ericsson: A Case Study,” Empirical Software Engineering, 23, 2550–2596.

9. Moe, N. B. et al. (2021) — “Finding the Sweet Spot for Organizational Control and Team Autonomy in Large-Scale Agile Software Development,” Empirical Software Engineering, 26.

In this episode of The Critical Path, we explore servant leadership in project management and why it should not be confused with passive or overly accommodating leadership.

A servant leader creates the conditions for the team to perform by providing clarity, removing obstacles, supporting effective decision-making and encouraging the early escalation of problems. Rather than becoming the centre of every decision, the project manager develops a team that can act with confidence, competence and accountability.

Using the leadership approach demonstrated by former US Navy captain David Marquet, the episode explains how authority can be moved closer to the people who hold the most relevant information.

Key references:

1. Greenleaf, R. K. (1970). The Servant as Leader. Robert K. Greenleaf Center for Servant Leadership.
2. Eva, N., Robin, M., Sendjaya, S., van Dierendonck, D. and Liden, R. C. (2019). ‘Servant leadership: A systematic review and call for future research’. The Leadership Quarterly, 30(1), pp. 111–132.
3. Nauman, S., Bhatti, S. H., Imam, H. and Khan, M. S. (2022). ‘How Servant Leadership Drives Project Team Performance Through Collaborative Culture and Knowledge Sharing’. Project Management Journal, 53(1), pp. 17–32.
4. Nauman, S., Musawir, A. U., Malik, S. Z. and Munir, H. (2022). ‘Servant Leadership and Project Success: Unleashing the Missing Links of Work Engagement, Project Work Withdrawal, and Project Identification’. Project Management Journal, 53, pp. 257–276.
5. Edmondson, A. C. (1999). ‘Psychological Safety and Learning Behavior in Work Teams’. Administrative Science Quarterly, 44(2), pp. 350–383.
6. Project Management Institute and Agile Alliance (2017). Agile Practice Guide. Project Management Institute.
7. Marquet, L. D. (2013). Turn the Ship Around! A True Story of Turning Followers into Leaders. Portfolio.
8. Madsen, S. (2020). ‘Is servant leadership relevant to project leaders today?’ Association for Project Management.
9. Project Management Institute. ‘Leadership Essentials for Project Management Professionals’.

This episode explores one of the most important leadership skills in complex project delivery: influencing people who do not report to you.

In major programmes, especially in defence, aerospace, infrastructure, and systems engineering, project managers rarely control all the people, budgets, suppliers, or technical decisions needed to deliver the outcome. Instead, they operate across a network of stakeholders, functions, and organisations.

The episode explains that influence without authority is built on credibility, alignment, framing, stakeholder strategy, and trust. Good project leaders do not simply escalate or push harder. They understand what others care about, connect requests to shared outcomes, and present clear options that help people make better decisions.

Using a real-world style example from a complex aerospace or defence integration programme, the episode shows how a project manager can influence a difficult design-change decision by bringing evidence, mapping consequences, and framing trade-offs around cost, schedule, safety, customer value, and technical risk.

The key message is that authority can create compliance, but influence creates commitment. In modern project environments, influence is not a soft skill, it is a core delivery skill.

Key references:

1. Cohen, A. R. & Bradford, D. L. — Influence Without Authority

2. French, J. R. P. & Raven, B. — “The Bases of Social Power”

3. Project Management Institute — “Influence Without Authority and Navigating Through Internal Politics”

4. Project Management Institute — “Techniques to Influence Others to Meet Project Goals”

5. Association for Project Management — Stakeholder Engagement

6. Association for Project Management — 10 Key Principles of Stakeholder Engagement

7. PMI — Stakeholder Analysis as a Pivotal Practice in Projects

8. Jääskeläinen, K. & Pau, L-F. — Internal Stakeholder Networks and Project Outcomes

In this episode of The Critical Path, we explore empathy as a serious leadership capability, not a soft personality trait. In complex projects and major programmes, leaders need more than schedules, dashboards, governance, and risk registers. They need to understand the human system behind delivery.

The episode explains that empathy helps leaders hear weak signals earlier, create psychological safety, improve stakeholder relationships, and separate genuine constraints from poor accountability. It does not mean lowering standards or avoiding difficult conversations. Instead, it allows leaders to diagnose problems more accurately and act with clarity.

Using Microsoft’s cultural shift under Satya Nadella as an example, the episode shows how empathy can support learning, collaboration, and adaptation. The key message is that empathy and accountability must work together. Empathy without accountability becomes over-accommodation; accountability without empathy creates fear.

The practical takeaway is simple: listen first, understand the pressure behind people’s behaviour, then make clear decisions. Empathy helps the truth travel faster than the problem.

Key references:

1. Center for Creative Leadership - Empathy in the Workplace

2. Google re:Work - Understand Team Effectiveness / Project Aristotle

3. Microsoft - Hit Refresh / Satya Nadella’s leadership philosophy

4. Microsoft Source - How Microsoft is using empathy to lead innovation

5. Ma, G. et al. - Empathetic Leadership and Employees’ Innovative Behavior, Frontiers in Psychology, 2024

6. Edmondson, A. C. - The Fearless Organization

7. Nadella, S. - Hit Refresh: The Quest to Rediscover Microsoft’s Soul and Imagine a Better Future for Everyone

8. Goleman, D. - Emotional Intelligence / Primal Leadership