Schedule Assurance
Why Recovery Programmes Fail
A recovery programme is a promise to leadership that lost time will be regained. Most break that promise — not because recovery was impossible, but because the plan was never actually deliverable.
Compression is not recovery
The commonest failure is cosmetic: durations squeezed and bars overlapped until the finish date returns to plan, with nothing in the real world changed to justify it. If the resources, sequence and constraints are identical, a shorter programme is not a recovery — it is the same delay, hidden.
The constraints that caused the delay are still there
A credible recovery names the cause and changes something about it — more resource, a different sequence, an unblocked approval, a released interface. A plan that leaves every original constraint in place is asking to fail the same way twice.
Optimism compounds
Recovery plans tend to stack best-case assumptions: peak productivity, no weather, instant approvals, perfect logistics. Each is plausible alone; together they are fiction. A recovery that only works if everything goes right will not work.
How to test one
Ask three questions: what specifically has changed since the delay; is the changed sequence physically and contractually buildable; and does the resource histogram the plan implies actually exist? If the answers are vague, the programme is a wish. A real recovery survives those questions — and is worth monitoring weekly against them.