Do not rebaseline a story you have not tested

A troubled programme creates pressure for visible action. Leaders ask for a new plan, a revised date and firmer governance. Teams respond by compressing activities, adding resources and moving milestones. This can create temporary reassurance while preserving the same assumptions that caused confidence to fall.

Recovery starts with diagnosis. The programme needs a defensible view of scope, progress, remaining effort, dependencies, decisions, capacity and risk. It also needs an honest account of how the current position developed. Without that, a new baseline is simply a new promise built on old information.

The US Government Accountability Office describes a reliable integrated schedule as a model that connects all the activities required to achieve the programme's objectives. Its Schedule Assessment Guide sets out ten recognised practices, including sequencing all activities, assigning resources, establishing a valid critical path, conducting schedule risk analysis and updating actual progress using logic. These practices are not administrative detail. They make the recovery forecast testable.

Separate symptoms from causes

Late milestones, overspend and exhausted teams are symptoms. Root causes are more likely to include unstable scope, unrealistic sequencing, hidden dependencies, weak design authority, slow decisions, capability gaps or a governance model that reports risk without resolving it.

The diagnostic should follow the delivery chain. Start with the outcomes and scope. Test whether the plan contains all necessary work. Trace the critical and near-critical paths. Compare claimed progress with completed outputs. Examine the decisions that constrain delivery. Then test whether governance, leadership behaviour and capacity are capable of sustaining the revised route.

  • Reality: one agreed evidence base for actual progress, cost, scope and risk.
  • Route: an integrated plan with credible logic, resources, dependencies and contingency.
  • Rights: explicit decision ownership, escalation thresholds and design authority.
  • Rhythm: governance that turns evidence into timely decisions and tracks their effect.
  • Readiness: leaders and teams with the capacity and alignment to execute the recovery.

A recovery plan must change the management system

A plan alone cannot recover a programme. Recovery requires a different operating rhythm. Decision forums need clear purposes. Workstream reporting must connect to the integrated plan. Risks need quantified consequences and owners. Scope control must become real. Leaders must stop sending conflicting signals about priority, pace and acceptable trade-offs.

There is also a human limit to acceleration. Adding people can increase coordination demand, while repeated urgency can reduce judgement and hide emerging risk. A credible recovery distinguishes essential scope from deferrable scope, protects the work that drives the critical path and creates enough capacity for leaders to decide well.

The first measure of progress is not a green dashboard. It is whether management information becomes more reliable, decisions become faster and the forecast becomes more stable. Confidence returns when stakeholders can see that the programme is being managed from evidence rather than optimism.

Sources and further reading

Rooted's interpretation combines these published sources with practical transformation experience. Statistics and research findings are attributed to their original publishers.

All insights