This episode explores why change management and change control are essential in every project. Change is unavoidable: requirements, priorities, budgets, technology, suppliers, and stakeholder expectations will evolve. The real challenge is not preventing change, but managing it in a structured and transparent way.

The episode explains that a good change control process protects the project baseline while still allowing the project to adapt. Every proposed change should be clearly described, assessed for impact, approved or rejected by the right authority, and then reflected in the project baseline if accepted.

A key message is that changes should never be assessed in isolation. A small technical change can affect cost, schedule, procurement, testing, safety, contracts, documentation, risks, and stakeholder commitments. This is why change control must involve project management, engineering, commercial, finance, risk, and delivery teams.

The episode also highlights the danger of informal change: small requests, undocumented decisions, and “can you just add this?” moments that slowly create scope creep. Mature projects surface change early, assess it honestly, make clear decisions, and update the baseline properly.

The main takeaway: change is not the enemy. Uncontrolled change is. Strong change control helps projects adapt without descending into chaos.

1. Association for Project Management – APM Body of Knowledge, 8th edition

2. APM – “The basics of change control and its importance”

3. Project Management Institute – PMBOK Guide / Integrated Change Control

4. PRINCE2 – Issue and Change Control / Issue Management Approach

5. NASA Systems Engineering Handbook

6. Earned Value Management guidance / PMBOK project controls principles

7. General lessons from major infrastructure and defence programmes

In this episode of The Critical Path, we explore why managing expectations is one of the most important leadership skills in complex project environments.

The episode explains that saying yes too quickly can create hidden delivery risk, especially when scope, cost, schedule, quality, safety, and technical performance are treated as if they are independent. In reality, every additional request creates a trade-off.

The core message is that saying no is not about being negative or unhelpful. It is about protecting credibility, delivery confidence, and organisational trust. Strong project leaders make constraints visible early, explain the consequences of decisions, and turn vague pressure into clear choices.

The episode uses the example of a major defence programme preparing for a critical design review, where adding a new capability without proper impact assessment creates downstream problems across engineering, suppliers, testing, safety evidence, cost, and schedule.

The key takeaway is simple: trust is not built by saying yes to everything. Trust is built by telling the truth early, offering options, and helping stakeholders make informed decisions before unrealistic expectations become delivery failures.

Key references:

1. Association for Project Management — APM Body of Knowledge, 8th Edition

2. APM / RICS — Stakeholder Engagement, 1st Edition

3. Project Management Institute — PMBOK Guide

4. PMI — Requirements Management: A Core Competency for Project and Program Success

5. PMI — Requirements Management Report

6. INCOSE — Systems Engineering Handbook

7. INCOSE — Requirements Management and Systems Engineering Guidance

8. INCOSE — Systems Integration Guidance

9. APM — Governance and Stakeholders

10. William Ury — The Power of a Positive No

11. Roger Fisher, William Ury and Bruce Patton — Getting to Yes

12. Chris Argyris — Organisational Learning and Defensive Routines

13. Bent Flyvbjerg — Megaprojects and Risk / How Big Things Get Done

14. Eliyahu M. Goldratt — Critical Chain

In this episode of The Critical Path, we explore why high performance in complex projects is not simply the result of talented individuals working harder. In aerospace, defence, nuclear, infrastructure, and other regulated environments, performance is shaped by the system around the team.

Leaders create high performance by designing the right conditions: clear priorities, honest communication, focused execution, strong accountability, and governance that enables decisions rather than creating bureaucracy.

The episode highlights that psychological safety and accountability are not opposites. High-performing teams need both: the confidence to raise bad news early and the discipline to own risks, decisions, interfaces, and outcomes.

Using the Boeing 787 Dreamliner programme as a real-world example, the episode shows how complexity, supplier dependency, unclear integration ownership, and optimistic schedules can undermine performance when the environment is not properly designed.

The key message is simple: leaders do not create high performance by demanding heroics. They create it by removing friction, making complexity visible, protecting focus, and building an environment where capable people can do their best work consistently.

• Amy C. Edmondson – The Fearless Organization
• Google re:Work – Project Aristotle / Team Effectiveness
• Project Management Institute – PMBOK® Guide and Project Management Principles
• ISO/IEC/IEEE 15288 – Systems and Software Engineering: System Life Cycle Processes
• NASA Systems Engineering Handbook
• Andy Grove – High Output Management
• Boeing 787 Dreamliner Programme Case Studies
• INCOSE / Systems Engineering Standards
• Marte Pettersen Buvik & Anastasiia Tkalich – Psychological Safety in Agile Software Development Teams
• Boeing 787 FAA Certification and Programme Context

In this episode of The Critical Path, we explore why complex projects and programmes require leaders who can adapt their style to the situation, rather than relying on one fixed leadership approach.

Situational leadership is about understanding what a person, team or challenge needs at a specific moment. In complex environments such as defence, aerospace, nuclear, infrastructure and major technology delivery, different situations demand different responses. Sometimes the leader must provide clear direction, especially during high-risk or urgent issues. At other times, the right approach is to coach, support or delegate.

The episode explains why both extremes can be damaging. Too much control can become micromanagement and reduce ownership. Too little involvement can become abandonment, leaving teams “empowered” but unsupported.

Using the example of a delayed systems integration programme, the episode shows how a situational leader can provide structure, clarify decision rights, support teams under pressure and delegate where capability is strong.

The key message is simple: effective leadership in complex environments is not about having one style. It is about having range, judgement and the discipline to diagnose the situation before deciding how to lead.

Key references:

1. Hersey, P. & Blanchard, K. H. — Management of Organizational Behavior

2. The Center for Leadership Studies — Situational Leadership® Model

3. Yukl, G. — Leadership in Organizations

4. Snowden, D. J. & Boone, M. E. — A Leader’s Framework for Decision Making, Harvard Business Review

5. Edmondson, A. C. — Psychological Safety and Learning Behavior in Work Teams

6. Edmondson, A. C. & Harvey, J-F. — Extreme Teaming

7. Fiedler, F. E. — A Theory of Leadership Effectiveness

In this episode of The Critical Path, we explore the paradox of energy in project management and leadership: project leaders often need to give energy to the system before they receive any back.

Complex projects rarely fail only because of poor plans, missed risks, or technical issues. They often lose momentum because the human energy behind delivery gradually drains away. Teams become tired, decisions slow down, meetings become repetitive, governance consumes time without creating movement, and suppliers or stakeholders become defensive.

The episode explains that leadership energy is not about false positivity or motivational speeches. It is about creating clarity, reducing confusion, making progress visible, and helping the system move again. Good leaders generate energy by clarifying priorities, removing blockers, making trade-offs visible, and turning effort into tangible progress.

A key message is that energy is lost at interfaces: between teams, suppliers, functions, and governance layers. Integration is therefore not only a technical discipline, but also an energy discipline. When integration works, effort flows toward outcomes. When it fails, teams can work hard in isolation while the programme remains stuck.

The episode also highlights how poor governance drains energy when it demands updates but avoids decisions. Good governance, by contrast, creates confidence because it enables decisions, supports escalation, and removes constraints.

The practical takeaway is to review your project through the lens of energy. Identify where energy is being created and where it is being drained. Then take one action: remove an unnecessary meeting, clarify one priority, escalate a blocked decision, or recognise genuine progress.

The central conclusion: energy is not a soft leadership concept. In complex projects, it is a delivery asset.

Key references:

• Schwartz, T. & McCarthy, C. — “Manage Your Energy, Not Your Time”, Harvard Business Review, 2007
• Project Management Institute — Pulse of the Profession 2023: Power Skills, Redefining Project Success
• Project Management Institute — Pulse of the Profession 2025
• Project Management Institute — Capturing the Value of Project Management Through Decision Making, 2015
• Association for Project Management — APM Body of Knowledge, 8th Edition
• Association for Project Management — What is Systems Thinking?
• Harvard Business Publishing — 2024 Leadership Development Report: Time to Transform
• Harvard Business Review — “When You’re Worn Down—and Your Team Is Too”, 2026
• McKinsey & Company — People & Organizational Performance Consulting
• PMI — The Future of Project Work: Pulse of the Profession 2024

A well-implemented project management methodology is not bureaucracy, it’s a performance enabler. In this episode, we explore how structured approaches improve clarity of roles, decision-making, risk management, and overall predictability in complex projects. Rather than slowing teams down, the right methodology reduces ambiguity, prevents “decision debt,” and ensures issues are identified early. Using a real-world defence programme example, we show how the absence of integration discipline led to delays and rework—and how introducing a structured methodology restored control.

Methodology doesn’t create complexity, it helps you manage it.

Key References:

• Project Management Institute – A Guide to the Project Management Body of Knowledge (PMBOK® Guide)

• AXELOS – PRINCE2® (Projects IN Controlled Environments)

• Scrum Alliance & Scrum.org – Scrum Guide (by Ken Schwaber and Jeff Sutherland)

• Scaled Agile, Inc. – SAFe (Scaled Agile Framework)

• Standish Group – CHAOS Reports

• McKinsey & Company & University of Oxford – “Delivering Large-Scale IT Projects on Time, on Budget, and on Value” (Flyvbjerg et al.)

• Bent Flyvbjerg – How Big Things Get Done / megaproject research

• Daniel Kahneman – Thinking, Fast and Slow

• Barry Boehm – Spiral Model / Risk Management research

• Donella Meadows – Thinking in Systems

• NASA – NASA Systems Engineering Handbook

• UK Infrastructure and Projects Authority – Project Delivery Functional Standard

• Association for Project Management – APM Body of Knowledge

Why do projects fail so often, even when the tools, processes, and reporting all seem to be in place? In this episode, we unpack the five most evidence-backed reasons projects fail: unclear objectives, poor requirements and scope control, weak sponsorship and stakeholder alignment, unrealistic planning driven by optimism bias, and weak communication across interfaces. The episode explains how these issues build slowly, often long before a project is visibly in trouble, and why failure is usually the result of tolerated drift rather than one dramatic mistake. Using a real-world style example, it also explores what leaders can do differently to reduce failure risk and improve delivery outcomes.

Key references:

• PMI — Pulse of the Profession 2017: Success Rates Rise: Transforming the High Cost of Low Performance
• Association for Project Management (APM) — Overcoming the barriers to successful project delivery
• Bent Flyvbjerg — What You Should Know About Megaprojects and Why: An Overview
• McKinsey — Capital investment is about to surge: Are your operations ready?

In this episode of The Critical Path, we explore one of the hardest leadership challenges in complex environments: collaborating with people you do not trust, do not like, or do not agree with. True collaboration is not tested when relationships are easy. It is tested when incentives conflict, pressure is high, and trust is limited. The episode unpacks how strong leaders move beyond personalities and focus on interests, structure, evidence, and decision-making processes. Using a real-world style programme example, it shows how to turn friction into progress, manage disagreement without paralysis, and lead effectively across difficult boundaries. Collaboration is not softness. It is disciplined leadership under tension.

Key references:

• Roger Fisher, William Ury, and Bruce Patton — Getting to Yes: Negotiating Agreement Without Giving In.

• Douglas Stone, Bruce Patton, and Sheila Heen — Difficult Conversations: How to Discuss What Matters Most.

• Kerry Patterson, Joseph Grenny, Ron McMillan, and Al Switzler — Crucial Conversations: Tools for Talking

• Patrick Lencioni — The Five Dysfunctions of a Team.

• Adam M. Brandenburger and Barry J. Nalebuff — Co-opetition.

• Yves L. Doz and Gary Hamel — “Collaborate with Your Competitors—and Win”.

• Amy Edmondson and Diana McLain Smith — “Want Collaboration? Accept—and Actively Manage—Conflict”.