Commanding the Critical Path

Most programmes don’t fail suddenly.

They drift.

The milestones are still there. Reports are still produced. Governance meetings still take

place. But something feels slightly off. Decisions take longer. Dependencies aren’t

completely clear. Risks are discussed, but not truly owned.

That quiet drift is usually when I’m asked to step in.

Over the past twenty-five years ,I’ve worked across Central Government, the NHS, aviation,

utilities, media and digital health. The sectors change. The scale changes. The underlying

pattern rarely does.

Delivery problems are seldom about capability. More often, leaders simply can’t see clearly enough what really determines completion.

The critical path becomes something people assume they understand, rather than

something that is properly evidenced and shared.

I saw this clearly during a major release at Eurocontrol, which manages European airspace.

The technical expertise was exceptional. The environment was complex and multinational.

What wasn’t fully embedded was consistent planning discipline across the organisation.

Teams understood their own workstreams well, but system-wide dependencies were less

visible.

Nothing was collapsing. But the programme wasn’t fully steerable.

The shift came when we returned to basics. Planning was aligned across workstreams.

Programme controls were applied consistently. Governance decisions were reflected

immediately in updated plans. Variance became visible earlier, while it was still

manageable.

Alongside that, we supported a move toward higher process maturity, not as a

compliance exercise, but to reduce unpredictability and build confidence in delivery.

Once leaders could see the real interdependencies and the genuine critical path,

conversations changed. Decisions became clearer. Interventions happened sooner. The

atmosphere steadied.

I’ve seen the same dynamic in very different environments.

During the pandemic at Prenetics EMEA, we were mobilising testing facilities, deploying

rapid response teams within 48 hours, and operating under intense scrutiny. Speed was

essential. But speed without structure creates fragility.

So the focus stayed practical: centralised planning, clearly defined roles, governance that

resulted in action, and reporting executives could rely on. When information is trusted,

leadership becomes calmer. And when leadership is calmer, programmes move with more

certainty.

Across government transformation, NHS recovery, enterprise technology change and

operational mobilisation, the principle has remained consistent.

Programme leadership isn’t about adding layers of process.

It’s about making complexity navigable.

That means keeping a clear line of sight on:

• Clear ownership.

• Visible interdependencies.

• Early risk visibility.

• A critical path grounded in fact.

When those are in place, even demanding programmes regain their footing.

And with that footing, progress follows.

About the Author:

Stan Tang is an MDIS Associate with more than 25 years’ experience leading complex

portfolio, programme and PMO delivery across Central Government, the NHS, aviation

(including Eurocontrol), utilities, media and digital health. His work has included

establishing centralised PMO capability within the Department of Health, leading the BBC’s

organisation-wide SAP transformation, mobilising operational delivery during the Covid-19

pandemic at Prenetics EMEA, and supporting mission-critical releases within European

airspace management.