Go-live is not a project milestone to be achieved by momentum. It is a business decision that transfers technology risk into live operations. This anonymised scenario-based case study combines recurring delivery conditions observed by Enigma’s senior practitioners across public and private-sector programmes. It does not describe or identify a single client engagement.
The situation
A major system implementation was approaching its planned production cutover. Testing was substantially complete, migration rehearsals had been performed and operational teams were preparing for launch. The programme faced the familiar pressure created by fixed dates, supplier mobilisation, business communications and accumulated cost.
The assurance problem
No single readiness indicator could justify the decision. Test completion did not prove acceptable residual risk. A successful migration rehearsal did not prove production reconciliation. A cutover plan did not prove that dependencies, rollback decisions and operational support arrangements were executable. The programme board needed an integrated assurance view across all of them.
The independent assurance approach
Enigma assessed the evidence supporting the go-live decision across functional and non-functional testing, unresolved defects, data migration and reconciliation, interfaces, security, operational readiness, support, cutover sequencing, rollback criteria, business readiness, known risks and decision ownership. Evidence was assessed for sufficiency, not merely existence.
This reflects Enigma’s Independent Go-Live Assurance service, supported by Quality and Test Assurance and Data Migration and Cutover Assurance.
What the evidence showed
The strongest areas had demonstrable completion criteria and traceable evidence. The weakest areas depended on judgement, verbal confirmation or closure actions that had not yet been independently verified. Crucially, not every open issue was a blocker, but every material issue required an explicit treatment: resolve, mitigate, accept or prevent go-live.
The governance intervention
The programme moved from a broad readiness conversation to a decision-condition model. Conditions were linked to evidence and closure authority. Residual risks were made explicit. The board could therefore see which risks were understood and consciously accepted and which still lacked sufficient evidence for progression.
The governance treatment aligns with Enigma’s Decision Condition Framework and Evidence Sufficiency Standard.
Why this mattered
This approach does not make the decision for the accountable executive. It makes the basis of that decision defensible. Where a programme proceeds, the organisation knows which risks it is accepting. Where it delays, the delay is tied to explicit evidence gaps rather than general unease.
The lesson
A defensible go-live decision is not ‘all tests passed’ or ‘the supplier is ready’. It is a reasoned judgement that the remaining risk is understood, evidenced and acceptable to the people who carry the operational consequence.