5 early warning signs a programme is drifting

Programmes rarely fail overnight. They drift. Each slipped date or deferred decision looks small on its own, so it is easy to dismiss as normal delivery noise. The pattern is what matters. These five signs are worth acting on early, because each has a simple response if caught in time.

1. Reports are green, but the team feels amber

When the official status says ‘on track’ but the people doing the work are anxious, the reporting is measuring activity rather than progress. Action: ask each workstream lead for a confidence rating alongside status, and track milestones by evidence of completion, not by effort spent.

2. Decisions are revisited rather than made

If the same topic appears on agenda after agenda, the decision either lacks a clear owner or lacks the information needed to make it. Action: keep a decision log with an owner, a deadline and the options on the table. Escalate anything that misses its date.

3. Dependencies live in people’s heads

When the plan cannot show what is waiting on what — between teams, systems or suppliers — delays appear without warning. Action: map the critical dependencies on one page and review them weekly with the people on both sides of each one.

4. Risks are logged but never owned

A long risk register that rarely changes is a sign of a ritual, not a control. Action: limit active attention to the top risks, give each one a named owner and a next action, and check at every review whether that action happened.

5. Stakeholders hear about problems late

If senior sponsors learn about issues from outside the programme, trust erodes quickly. Action: agree a simple rule — significant issues are raised within days, with a proposed response — and make it safe for the team to do so.

A typical scenario

In an illustrative case, a programme reports green for three months while design sign-off is quietly postponed twice. Adding a confidence rating to the weekly report shows two workstreams at low confidence. The sponsor sets a decision deadline, the design is signed off within ten days, and the plan is adjusted by a fortnight rather than the three months that would otherwise have surfaced later.

Quick self-check

• Would the delivery team describe progress the same way the reports do?
• How many decisions have been waiting more than two weeks?
• Can you see the critical dependencies on a single page?
• Does each top risk have an owner and an action this month?
• When did the sponsor last hear bad news first-hand?

Two or more ‘no’ answers is a good reason for a short, independent health check. Catching drift early costs days; catching it late costs months.