Why Project Programmes Stop Being Honest (And What to Do About It)

Every project has a moment where the programme becomes fiction. Here’s what causes it — and what the professionals who catch it early actually do differently. Programmes don’t fail because planners are bad at scheduling software. They fail because pressure replaces realism at every review meeting. The pattern is consistent across sectors, project types, and geographies. A programme is created with genuine intention. It reflects a realistic path to delivery. Then it meets the real world. Ground conditions turn out to be different from what the survey suggested. Lead times from suppliers are longer than budgeted. Ecology surveys reveal constraints that weren’t in the risk register. Planning conditions haven’t been discharged. The float that was built in has already been used. At this point, a decision is made — not explicitly, but collectively. The programme gets updated rather than rebaselined. The new dates look reasonable if everything from here goes perfectly. The client sees green. And here is the problem: everything from here rarely goes perfectly. The professionals who break this cycle don’t have better tools. They have a different conversation — one that happens earlier, is framed around outcomes rather than blame, and gives leadership the honest picture before the damage compounds. That conversation is what Chapter 10 of the book covers in full. The language that works. The moment to say it. The rebaselining approach that protects the project and the professional who raises it. Get the book at linktr.ee/Week3fire — ebook and paperback available.