Release Risk
Release Confidence Without Guesswork
8 April 2026 · 6 min read
Go-live decisions are too often made on sentiment. They can be made on evidence, using criteria agreed long before the date.
Agree the criteria before you need them
Release criteria written a week before go-live will always be negotiated down to whatever the project has achieved. Written at the start, they become a standard the project delivers against.
What has to be evidenced
Which business-critical scenarios have passed, in a production-like environment, with production-shaped data. What the open defect profile is by severity, with named acceptance of each deferral. That the cutover has been rehearsed end to end, including the timings. That the rollback path has been executed at least once, not just documented.
That operational readiness exists: monitoring, support rota, known-issue list, and a defined threshold for calling the release back.
Make the decision reversible
The strongest release position is one where going live is not a one-way door. Phased rollout, feature flags and a rehearsed rollback all convert a high-stakes bet into a manageable step.
If none of those are available, the go-live decision deserves far more evidence than a green dashboard.