A programme can be busy, well governed and extensively reported — and still fail to change anything that matters.

Transformation programmes generate a lot of work: workshops, boards, plans, reports, risk logs and papers. Some of it is necessary. But completing it does not mean the service is improving or the benefits are any closer.

Activity is visible; progress is harder to judge. A workshop has a date and an attendance list. A paper can be signed off. A milestone can turn green. Meanwhile, staff may still be working around the same broken process and customers may still be waiting just as long.

When the pressure rises, programmes often add more controls: more meetings, more reporting and more detailed plans. This can make delivery slower while giving leaders greater confidence that it is under control. Teams spend growing amounts of time describing the work and less time resolving what is stopping it.

Too much governance can mean there is no real governance at all. Duplicate boards and overlapping forums blur who has the authority to decide, create mixed messages and send programmes round the same issue repeatedly. Progress slows because nobody can secure a clear decision. In the worst cases, governance becomes an industry of highlight reports and dashboards: more effort goes into describing delivery than making the difficult, sometimes brave, decisions needed to deliver the right thing.

Measure movement, not motion

We keep bringing the programme back to one question: what is different in the service because of the work completed so far? We trace activity through to the deliverable, the change it enables and the benefit it is meant to realise. If that line cannot be drawn, the activity needs to be challenged.

Programme disciplines still matter, but they must earn their place. Governance should unblock decisions. Reporting should show where intervention is needed. Plans should expose dependencies and choices, not provide false certainty. Measures should tell leaders whether outcomes are changing, not simply whether tasks are complete.

We look behind the reassuring status report. Are the same issues carried forward each month? Has a milestone turned green only because its scope has narrowed? Are decisions recorded without an owner or deadline? Is one workstream producing something another cannot implement? These are early warnings, and we treat them as delivery issues to resolve — not observations to report again next month.

These are not minor programme-management concerns. They are signs that effort is being absorbed without enough progress being made.

What this changes

We create a direct line of sight from activity to outcome. Every significant piece of work needs a clear purpose, an owner and an observable effect on delivery. We strip out activity that adds no value and refocus effort on the decisions and deliverables that will move the service forward.

The programme usually becomes simpler. Meetings are shorter or stop altogether. Reports focus on decisions, dependencies and results. Teams spend less time servicing the programme and more time changing the service.

It also makes stalled delivery harder to hide — which is useful. Leaders can intervene while there is still time to recover, rather than discovering at the end that a completed plan has not produced a result.

Questions for leaders

• What has changed in the service — not just in the programme — over the last eight weeks?

• Is it clear which forum makes each critical decision — and can it make that decision quickly, even when the choice is difficult?

• Are milestones measuring completed activity or evidence of a better outcome?

The insight: Governance should accelerate decisions and delivery — not become a substitute for them.