The Anatomy of Program Drift

In Defence, delivery failure is rarely technical — it’s structural.

One of the most persistent challenges in complex Defence capability programs is not catastrophic failure — it is gradual, almost imperceptible drift.

Program drift rarely begins with a major event. It starts quietly:

• Engineering decisions deferred “temporarily”
• Governance forums becoming administrative rather than authoritative
• Transition activities compressed to protect milestones
• Safety, human factors, and test evidence accepted with increasing assumptions
• Technical debt accumulating faster than it is retired

Over time, the program slowly separates from its original engineering intent.

Across several major Defence acquisition and sustainment programs I’ve supported over the last decade, I’ve observed that drift typically emerges when three conditions begin to align:

1 – Delivery pressure overtakes engineering discipline

Schedule urgency gradually displaces structured technical assurance. Engineering reviews become “tick-and-flick” activities rather than genuine risk controls.

2 – Governance loses technical authority

When governance forums stop making hard engineering decisions and become reporting mechanisms, technical baseline integrity begins to erode.

3 – Organisations confuse activity with progress

Large programs can appear extremely busy while quietly accumulating unresolved integration, certification, sustainment, and operational risk.

Interestingly, the most effective recoveries I’ve seen were not driven by heroic effort. They were driven by restoring fundamentals:

• Clear technical authority
• Disciplined systems engineering
• Accountable governance
• Traceable safety and certification evidence
• Empowered engineering leaders
• Honest conversations about risk

In one multi-domain sustainment environment, simply re-establishing engineering review discipline, systems safety governance, and configuration control significantly improved delivery performance and stakeholder confidence without major structural change.

In another complex acquisition program, the turning point came when engineering governance regained authority over transition and certification decisions rather than allowing schedule pressure to dominate technical acceptance.

Program drift is rarely solved through more reporting.  It is usually solved by restoring engineering integrity.

For senior engineering and program leaders, one of the most important questions we can ask is:

“Are we still governing the system we intended to build and sustain — or merely managing the consequences of drift?”