Program Rescue · Field Notes
Quiet isn't stable. Why a silent program is more at risk, not less.
Three weeks before go-live, the project plan still said "on track."
I'd been brought in a month earlier to help stabilize a robotics fulfillment rollout, and on paper, nothing looked wrong. Every task on the board was green. What I actually found, once I started asking questions in person instead of reading status reports, was that the integration team and the operations team hadn't spoken directly in eleven days. Each side had quietly decided the other's silence meant there were no open issues.
That's the pattern I look for now, more than any red flag on a Gantt chart. A program that's genuinely healthy is loud. People escalate. They push back in standups. They ask uncomfortable questions out loud, in front of everyone, because they expect an answer. When that noise disappears, it doesn't mean the problems went away. It usually means they stopped being reported, right around the time they started getting expensive to fix.
The data backs up the pattern
This isn't just anecdotal. The scale of quiet, undetected failure across the industry is well documented:
Only 31% of projects succeed outright. The Standish Group's CHAOS research puts the 2020–2024 success rate at 31%, with 50% "challenged" (late, over budget, or reduced in scope) and 19% failed outright. Large projects fare far worse: fewer than 10% succeed, compared to roughly 90% for small ones.
Half of large IT projects blow their budgets. A McKinsey and University of Oxford study of over 5,400 IT projects found that large projects (initial budgets above $15 million) run 45% over budget and 7% over schedule on average, while delivering 56% less value than predicted. Only 1 in 14 is delivered both on time and on budget. 17% become "black swan" projects severe enough to threaten the company itself.
Poor performance wastes roughly $2 trillion a year globally. PMI's 2025 Pulse of the Profession puts the average waste at 11.4 cents of every project dollar spent.
None of these programs failed in a single dramatic moment. They drifted, quietly, while the reporting stayed calm. That's the mechanism worth paying attention to: the failure isn't sudden, but the moment status stops reflecting reality often is.
What to actually check
If you manage or sponsor a program, here's what I look for in the first week of any engagement, and what you can check yourself before you need to call someone like me:
- When did two teams that depend on each other last disagree out loud? Not in a hallway conversation, in a meeting, on record. If neither side can point to a recent instance, that's not alignment. It's disengagement.
- Does the weekly status report read differently from four weeks ago? If the language, the risks listed, and the tone are identical week over week, someone stopped updating it honestly.
- Who would raise their hand if the plan is wrong? If you can't name a specific person who owns that responsibility and has done it recently, no one currently will.
If your program has gone quiet lately, don't read that as calm. Go find out why, before the silence is the only warning you get.
Keep Reading
Tell me where your program stands.
A short conversation is enough to know if this is a fit. I work with organizations across supply chain, robotics, SaaS, and public-sector systems on program rescue and fractional delivery leadership.
Prefer email? oded@libi-tech.co