RC-401i · Module 4

The Go/No-Go Framework: How to Make the Launch Decision

5 min read

The go/no-go meeting is not a deliberation. By the time the go/no-go meeting occurs, the domain reviews are complete, the conflicts are resolved, and the blocker status is documented. The meeting is a decision ratification, not a discovery session. If material new information surfaces in the go/no-go meeting that changes the risk picture, that is a failure of the review process — the domain reviews did not surface something they should have. Call a timeout, investigate, and reconvene when the information is complete. Do not make a go-live decision in a meeting that has just received unexpected material information.

The go/no-go framework has three possible outcomes: Go (all four domains green, all blockers resolved, post-launch commitments documented and owned), Conditional Go (no go-live blockers remain, one or more yellow items accepted with documented risk acceptance and post-launch remediation committed), and No-Go (one or more go-live blockers remain unresolved). Each outcome is documented. The documentation is retained.

Do This

  • Make the go/no-go decision based on documented domain findings with current resolution status
  • Document risk acceptance decisions with the name of the authority who accepted the risk
  • Require all four domain clearances before a Go or Conditional Go decision
  • Treat No-Go as a process success — the review worked
  • Set a specific date for re-evaluation when issuing a No-Go decision

Avoid This

  • Allow the go/no-go meeting to become a negotiation over the go-live date
  • Issue a Conditional Go without documented owners for each post-launch commitment
  • Override a No-Go recommendation without a documented written risk acceptance from C-level authority
  • Treat No-Go as a failure of the review team rather than a success of the process
  • Proceed without all four domain sign-offs because one domain was "mostly done"
  1. Go/No-Go Meeting Agenda (90 minutes maximum) Fifteen minutes: review owner presents the deployment readiness summary dashboard. Thirty minutes: each domain lead presents their status in ten minutes — green items confirmed, yellow items explained, blockers resolved or escalated. Fifteen minutes: cross-domain conflict status — all conflicts resolved or escalated to risk acceptance. Twenty minutes: risk acceptance decisions for any yellow items the organization chooses to accept. Ten minutes: final decision, documentation of outcome, post-launch commitment assignments. The meeting ends with a written decision record signed by the deployment authority.
  2. Risk Acceptance Protocol Risk acceptance is a formal act, not a verbal agreement. For each yellow item the organization accepts: the risk is described in one paragraph in plain language, the potential impact if the risk materializes is quantified, the authority accepting the risk is named (this must be a named individual, not a team or a committee), and the post-launch remediation timeline is committed in writing. Risk acceptance without a named individual is not risk acceptance. It is risk diffusion — nobody is accountable when the risk materializes.
  3. No-Go Documentation A No-Go decision is documented with: the specific blockers that prevented clearance, the domain lead responsible for each blocker, the remediation actions required, the estimated timeline for remediation, and the date of the re-evaluation meeting. No-Go is not indefinite. It has a specific re-evaluation date and a specific list of conditions that must be met for reconsideration. The project lead owns tracking remediation progress against the committed timeline.