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