The point at which a program hands over to operations is not the end of the governance challenge. It is the point at which the consequences of every governance decision made during acquisition finally become visible and attributable. For the program owner, transition is where the record of how the program was governed is read back, in public, against the capability that was actually delivered.
Most discussion of program performance concentrates on acquisition: budget approvals, milestone achievement, schedule, and contractor delivery. These are legitimate concerns, and they are where governance attention naturally pools, because they are where the gates sit. But they obscure a harder truth that every program director learns eventually. Operational value is not realised at delivery. It is realised or lost in sustainment. And whether a program can sustain its capability is determined not at handover, but by the governance and technical decisions taken years earlier, under acquisition pressure, often by people who will have moved on before the consequences land.
This pattern repeats across maritime, joint, and land domains with a consistency that should concern anyone accountable for a program approaching transition. The transition to sustainment is the moment when what was deferred becomes undeferrable. And by the time it does, the options for structural intervention have narrowed to the few that remain expensive, visible, and late.
The transition does not create the problem — it reveals it
Transition is among the most underestimated phases in any Defence or complex program the point at which delivery milestones give way to operational reality, and at which accountability for the capability shifts decisively toward the Commonwealth owner.
Across major programs, a consistent pattern emerges at this point. Governance pressure intensifies precisely where governance capacity is most stretched. The technical debt accumulated during acquisition deferred decisions, configuration drift, incomplete qualification evidence, fragmented institutional knowledge surfaces at operational handover, not before it. It surfaces there because that is the first moment the system is asked to perform without the delivery organisation holding it together.
This is not coincidence, and it is not bad luck. It is the consequence of a governance culture that has treated sustainment planning as a downstream activity rather than a core design consideration carried from the outset. Where that culture prevails, the transition event does not reveal new problems. It reveals problems that were always present deferred from earlier phases into a context where they are structurally harder, and considerably more expensive, to resolve. The uncomfortable implication for the program owner is that the integrity of the transition is largely set before they inherit it.
The independent audit record publicly available, and spanning nearly two decades of major-program oversight documents this pattern with consistent specificity. The evidence is there for any governance body willing to examine it before the transition rather than after. Program-specific references are available on request.
Why this is a governance integrity problem, not a handover problem
Framing transition as a handover challenge documentation, knowledge transfer, workforce readiness is necessary but not sufficient. It treats transition as a boundary event to be project-managed, rather than as the culmination of a process that either preserved or eroded the conditions required for effective sustainment. The distinction matters because the two framings lead to different interventions: one produces a handover plan, the other produces an honest read of whether the program is actually ready to be sustained.
Research into why complex programs fail identifies five integrity domains that together determine whether a program remains genuinely capable of achieving its intended outcomes. Transition is the one event that stress-tests all five at once:
- Governance effectiveness — does the accountability structure survive the handover, or does transition open a gap in which no single party is genuinely responsible for the capability?
- Delivery system health — has the technical debt accumulated during acquisition been resolved, or has it been quietly transferred into the sustainment baseline, where it will cost considerably more to address?
- Engineering integrity — does genuine technical authority transfer with the capability, or does handover mark the point at which engineering authority reverts to the contractor by default?
- Organisational integrity — is the sustainment workforce genuinely able to absorb the capability, or has transition been planned against an optimistic resourcing model the operational environment will not support?
- Adaptive integrity — does the sustainment organisation have the governance sensitivity to detect emerging conditions before they embed — or has the institutional knowledge required for that sensing already departed with the delivery team?
When these degrade simultaneously which the audit record documents as a recurring condition in programs experiencing significant transition difficulty the result is not a handover problem that a better handover document can fix. It is a systemic integrity failure that was set in train long before the handover date.
The question worth asking before the date is set
For the program owner approaching transition, the practical value is not in recognising this pattern after the fact. It is in testing for it early enough that intervention is still cheap, still quiet, and still within their control. That requires a read of the program that traditional delivery controls are not designed to give an independent, evidence-based assessment of whether the governance, technical authority, and institutional knowledge required for sustainment have actually been built, or merely assumed.
The reforms now reshaping Defence delivery have named this problem explicitly: on-time, on-budget delivery, and the governance that produces it, are the express object of the new arrangements. For those of us who will be accountable for capability under them, the question is no longer whether the pattern is real the audit record settled that but whether we will test for it in time.
Chris Lindemann is the developer of the Program Integrity Method: a predictive systems-assurance methodology designed to identify the systemic conditions that historically precede delivery and sustainment failure in complex Defence and infrastructure programs.
So, the question I would put to any program owner approaching transition is this: do you have independent, evidence-based assurance that the conditions for effective sustainment have genuinely been built into your program — or are you trusting that the problems deferred during acquisition will not surface on your watch?