THE STARTING POINT
Review software release readiness across key workflows, integrations, deployment, recovery and ownership. Agree the evidence needed for a launch decision.
Check complete user journeys.
A feature may work in isolation while the wider journey still fails. Review tasks from entry through confirmation, including permissions and incomplete information. Use examples that represent the intended audience. Record the expected outcome so stakeholders can distinguish a successful check from a visually convincing demonstration.
Prepare the operating environment.
Confirm configuration, required integrations and the people responsible for deployment. Discuss how issues will be detected and communicated. The release checklist should include support instructions and recovery decisions, not only the work required to copy application files into place.
Make the go-live decision explicit.
Review open issues, their impact and the agreed acceptance criteria with the decision owner. Document any limitations that users need to understand. A release decision should consider the application’s intended use and support readiness rather than treating every unresolved issue as equally important.
Run a release decision meeting around evidence
Describe exactly what is changing: application code, configuration, data, permissions or interfaces. Identify the affected workflows and agree checks for both normal and exceptional behaviour. Assign owners to deployment, observation and recovery, including a deputy where needed.
Rehearse in an appropriate environment and record results. Confirm that the team can detect a problem after deployment, not only before it. Discuss staged exposure where the system supports it, and agree the conditions for pausing or recovering. At the decision meeting, review unresolved issues and dependencies explicitly. Keep the release approval tied to a particular version and configuration so later changes do not inherit approval automatically.
A practical go/no-go record
Use this record to support a decision; it should not become a set of unchecked boxes copied from a previous launch.
- Release identity: version, configuration, included changes and affected systems.
- Verification evidence: critical journeys, integration checks, accessibility review and unresolved defects.
- Deployment ownership: responsible person, schedule, dependencies and communication plan.
- Observation: health signals, logging, business checks and the period of active review.
- Recovery: pause conditions, rollback or forward-fix decisions and data implications.
- Approval: named decision-maker, accepted limitations and the exact approved release.
A working demonstration does not cover the release
A demo may omit permission changes, unavailable dependencies, background jobs or production configuration. Review those elements alongside visible features. Check that the team can explain a failure and access the information needed to respond.
Avoid a recovery plan that has never been exercised. Some data changes cannot be reversed by redeploying old application code. Discuss those limits and the treatment of transactions during an incident before deciding that a release is ready.
Must every release use the same checklist?
Keep a common set of responsibilities, but adapt verification to the actual change and its consequences. A content correction and a database migration require different evidence. Record why a check is relevant or omitted, and keep approval proportionate to the release being made.
ILLUSTRATIVE PLANNING EXAMPLE
Example: releasing a payment-related update
Alongside the normal success journey, test a cancelled payment, a delayed response and a repeated notification in the provider’s test environment. Confirm that the user sees a useful status and that the team can reconcile the transaction. Review configuration and recovery responsibilities with the people supporting the release.
Keep a release checklist with evidence links, outstanding issues and named decision owners. Launch approval should reflect agreed criteria rather than a demonstration of one happy path.
TAKE THE NEXT STEP
Your discovery checklist
- Review complete user journeys and permission scenarios.
- Confirm deployment, support and recovery responsibilities.
- Agree the acceptance criteria and open-issue decision.
FURTHER READING
Official resources to explore
Explore the related official guidance below. The templates and examples are practical starting points to adapt to your own project.