The Early Warning Signs of Program Drift in Complex Programs

After more than two decades working across Defence acquisition, sustainment, systems engineering, and capability assurance programs, I’ve become increasingly convinced of one thing:

Most major Defence programs do not fail because the technology is impossible. They fail because governance progressively loses the ability to control complexity.

In several large Defence programs I’ve supported—spanning integrated tactical data networks, maritime capability systems, and complex ISR and sensor environments—the technology challenges were significant, but manageable.

The real problems emerged elsewhere.

Program drift often begins long before the organisation recognises it.

Forums continue to meet.

Reports continue to be produced.

Compliance activities continue to occur.

Yet the mechanisms intended to preserve engineering integrity gradually lose their ability to influence outcomes.

The warning signs are often subtle:

• Engineering review boards become reporting forums rather than decision forums
• Technical authorities become advisory rather than authoritative
• Risk registers become repositories rather than management tools
• Schedule pressure begins overriding engineering evidence
• Compliance activities become performative rather than assurance-driven
• Governance focuses increasingly on narrative management rather than technical reality

At that point, the organisation begins to lose technical control of the program.

One of the clearest indicators is when teams stop discussing engineering margin and start discussing how to explain emerging problems.

I’ve seen highly capable engineering teams working extraordinary hours while governance structures quietly drift away from the disciplines that maintain program integrity:

• Systems engineering discipline
• Configuration integrity
• Certification traceability
• Safety assurance
• Technical decision accountability
• Transition and sustainment governance

Eventually, the technology itself becomes unstable—but by then the drift has already occurred.

The most effective recovery activities I’ve experienced were not driven by introducing more process.

In many cases, the organisation already had plenty of process.

Recovery came from restoring:

• Clear technical authority
• Disciplined engineering governance
• Accountable decision-making
• Independent assurance
• Configuration control
• Leadership willing to confront uncomfortable technical realities early

Good governance is not bureaucracy.

In complex Defence capability environments, governance is the mechanism that preserves engineering integrity under pressure.

Technology rarely collapses suddenly.

More often, organisations experience a gradual loss of program integrity.

Governance drifts from assurance toward administration.

Engineering authority becomes diluted.

Decision-making becomes disconnected from evidence.

By the time technical failure becomes visible, the underlying drift has often been present for years.

That is usually where program failure truly begins.