Episode 32 - Firefighting Is Not Delivery

Episode 32 - Firefighting Is Not Delivery

In this episode, we explore why constant firefighting is not the same as sustainable project delivery. Every complex programme will face problems, but when an organisation is always in crisis mode, it usually points to deeper issues: weak front-end definition, poor systems integration, unclear governance, overloaded teams, optimistic reporting, or a culture that rewards heroics more than prevention. The episode explains how firefighting creates the illusion of progress. People are busy, decisions are urgent, and milestones may still be recovered, but the underlying delivery system often remains weak. Using the Crossrail programme as an example, we discuss how late integration, assurance complexity and unrealistic planning can turn delivery into recovery. The key message is that sustainable delivery requires prevention: clear scope, visible risks, honest project controls, early integration, protected capacity, and leadership that rewards early escalation and root-cause thinking. Firefighting may save a milestone, but it will not build a reliable delivery system. 1. Repenning, N. P. & Sterman, J. D. — “Nobody Ever Gets Credit for Fixing Problems that Never Happened” / capability trap research 2. Repenning, N. P. — “The Persistence of Firefighting in Product Development” 3. National Audit Office — “Lessons learned from Major Programmes” 4. National Audit Office — “Crossrail: a progress update” 5. National Audit Office — “Completing Crossrail” 6. PMI — “Pulse of the Profession 2018: Success in Disruptive Times” 7. ISO 31000:2018 — Risk Management Guidelines 8. INCOSE Systems Engineering Handbook / SEBoK reference

Episode 31 – Decision Latency: The Hidden Delay That Damages Projects

In this episode of The Critical Path Podcast, we explore decision latency: the delay between a project needing a decision and the organisation actually making one. The episode explains that slow decisions are often hidden behind more visible problems such as cost growth, schedule delay, rework, supplier issues and poor integration. In complex programmes, one delayed decision can affect requirements, design, procurement, testing, integration and entry into service. The core message is that not deciding is still a decision. When leaders wait for perfect information, avoid accountability or push decisions into another governance forum, the project continues to spend time and money while options reduce. Using Crossrail as a real-world example, the episode highlights how major projects can suffer when governance is not close enough to delivery reality and senior leaders do not receive clear, timely information. The episode concludes that good governance should reduce decision latency, not create it. Project teams should track important decisions like milestones, assign owners, set deadlines, define escalation rules and make the cost of waiting visible. Key takeaway: The critical path is not only made of activities and deliverables. It is also made of decisions and delayed decisions can quietly damage project performance. Key references: 1. National Audit Office. Governance and decision-making on mega-projects 2. National Audit Office. Crossrail – A progress update 3. National Audit Office. Crossrail progress update – press release 4. Flyvbjerg, B., Holm, M. S., & Buhl, S. What Causes Cost Overrun in Transport Infrastructure Projects? 5. Flyvbjerg, B., Holm, M. S., & Buhl, S. How common and how large are cost overruns in transport infrastructure projects? 6. PMI. Capturing the Value of Project Management Through Decision Making 7. PMI. Pulse of the Profession 2026: Driving Success in Complex Projects 8. Cantarelli, C. C., van Wee, B., Molin, E. J. E., & Flyvbjerg, B. Different Cost Performance: Different Determinants? The Case of Cost Overruns in Dutch Transportation Infrastructure Projects 9. Cantarelli, C. C., Molin, E. J. E., van Wee, B., & Flyvbjerg, B. Characteristics of Cost Overruns for Dutch Transport Infrastructure Projects and the Importance of the Decision to Build and Project Phases 10. UK Parliament / Public Accounts Committee. Governance and decision-making on major projects

Episode 30 - Delegation That Works: From Task Dumping to Real Accountability

In this episode of The Critical Path, we explore why delegation is not simply about giving tasks to others, but about creating ownership, accountability, and capability within project teams. The episode explains that effective delegation starts with clarity: people need to understand the outcome, the purpose behind the work, and what success looks like. It also highlights the importance of matching responsibility with authority. Delegation fails when someone is made accountable for an outcome but does not have the power, information, or access needed to influence it. The discussion also covers the role of guardrails, governance, and review rhythms. Good delegation does not mean disappearing; it means defining decision boundaries, escalation points, and support mechanisms without falling into micromanagement. Using examples from complex project environments, the episode shows how poor delegation can create integration failures, hidden risks, and bottlenecks. Strong delegation, by contrast, helps teams make faster decisions, surface problems earlier, and reduce dependency on one overloaded leader. The key message: don’t just delegate tasks, delegate outcomes, authority, and accountability with clear guardrails. Key references: 1. Project Management Institute — “Delegation and sharing of authority by the project manager” 2. Project Management Institute — “Management, leadership — delegation” 3. PMI / PMBOK concepts — Responsibility Assignment Matrix / RACI 4. Association for Project Management — APM Body of Knowledge 5. Association for Project Management — Project Governance 6. Harvard Business Review — “To Be a Great Leader, You Have to Learn How to Delegate Well” 7. Harvard Business Review — “When Delegating, Make Accountability Clear” 8. Atlassian — RACI Chart Guide 9. PMI — Project Governance: Critical Success 10. PMI — “Delegation”

Episode 29 - Change Is Inevitable. Chaos Is Optional.

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

Episode 28 - The Leadership Skill of Saying No - Managing Expectations Before They Manage You

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