Go / No-Go Review¶
Decision review — instantiates Stage-Gate Progression
Convenes a single synchronized decision event where designated authorities poll launch criteria and render one committing verdict — go, hold, or no-go — before a high-exposure action.
A Go / No-Go Review collapses progression into a single synchronized decision event: at a fixed moment, just before a committing or high-exposure action, designated authorities are polled in turn against launch criteria, and the review renders one verdict — go, hold, or no-go. Its defining idea is the decision rule enacted as a live poll: every responsible party must affirmatively say "go," any one can say "no-go" or "hold," and progression happens only on unanimous readiness at that instant. It is not a rolling review or a document that accretes approvals over weeks; it is a convened event whose whole purpose is to force a clean, attributable, all-hands verdict at the last responsible moment before the boundary is crossed and the action becomes hard to recall.
Example¶
A launch team is minutes from committing a rocket to flight. The launch director runs the go/no-go poll: propulsion, guidance, range safety, weather, flight dynamics, and the payload customer are each called by name and must answer "go" or "no-go" for launch. The evidence each speaks from — telemetry, the weather picture, tank pressures — has been assembled and is current at the moment of the poll. Weather reports a violated constraint: upper-level winds are out of limits. That single "no-go" ends the poll; the count holds. Nothing about the vehicle's own readiness overrides it, because the rule is that anyone can stop and everyone must clear. The team holds for the window to improve rather than proceeding on the majority's confidence, and the verdict — who said what — is on the record for the flight readiness process that governs the event.[1]
How it works¶
The review's distinctive machinery is the synchronized, unanimous-to-proceed poll:
- One event, one moment. Readiness is judged all at once, at the last responsible moment, so the verdict reflects the state of the world now rather than a stale approval collected earlier.
- Each authority is polled by name against its own criteria. Every responsible discipline speaks for its domain, so the "go" is the sum of specific competent affirmations, not a single manager's overall impression.
- The decision rule is asymmetric. Proceeding requires all-go; any one participant's "no-go" or "hold" stops the count. The rule deliberately privileges stopping over launching.
- The verdict is bounded to this crossing. A "go" authorizes this action under these conditions; it is not standing approval, and a material change reopens the poll.
Tuning parameters¶
- Poll membership — which disciplines get a vote. Broad membership catches more failure modes but slows the poll and dilutes accountability; narrow membership is decisive but can miss a blind spot.
- Decision rule — unanimous-to-go versus a designated authority who can override a lone objection. Strict unanimity maximizes safety and can also enable a single hold to stall; a weighted rule restores momentum at some risk.
- Timing before commit — how close to the action the poll sits. A late poll reflects the freshest state but leaves little room to react to a "hold"; an early one buys reaction time on staler evidence.
- Evidence currency requirement — how fresh each participant's data must be at poll time, so no one votes "go" on yesterday's reading.
- Escalation path for a hold — whether a "hold" pauses for a recycle or hands the call up the chain; determines how a stopped poll resolves.
When it helps, and when it misleads¶
Its strength is forcing a clean, attributable commitment decision at the moment it matters, with every responsible party on record and a structural bias toward stopping when anyone is not ready. It is the right instrument precisely when the action is committing or exposing and a diffuse, rolling approval would let readiness erode unnoticed until it is too late to stop.
Its failure mode is normalization of deviance: when a criterion is violated but "we launched fine last time," the poll can drift into ratifying a risk that has quietly become routine, so the event certifies a "go" the evidence does not support.[2] A related misuse is the poll run under schedule pressure as theater, where a "no-go" is socially impossible and everyone says "go" to avoid being the one who scrubbed. The discipline that guards against it is to make objecting cheap and legitimate — protecting the lone "no-go," treating any override of an objection as a logged, justified exception, and reviewing scrubbed-versus-proceeded outcomes so the poll's criteria stay honest rather than eroding toward whatever the schedule wants.
How it implements the components¶
Go / No-Go Review fills the decision-event side of the archetype:
stage_gate— the imminent committing action (launch, deployment, mission start) is the boundary the review guards at the last responsible moment.progression_decision_rule— the asymmetric poll (all-go to proceed, any one can stop) is the explicit rule mapping readiness into a verdict; the mechanism's anchor.gate_authority— each polled discipline is a named authority whose affirmative "go" is required for its domain.evidence_packet— the current telemetry, conditions, and status each participant speaks from at the moment of the poll.
It does not permit a staged or conditional rollout — the verdict is binary at one instant (conditional_progression_clause — that is Release Readiness Review) — and it does not route a failed item into rework or remediation (rollback_or_return_path — that is Manufacturing Inspection Point); a go/no-go review renders one synchronized commit-or-hold decision.
Related¶
- Instantiates: Stage-Gate Progression — the review is the gate compressed into a single synchronized decision event.
- Sibling mechanisms: Clinical Clearance Protocol · Compliance Signoff · Educational Mastery Assessment · Manufacturing Inspection Point · Release Readiness Review · Quality Gate · Approval Workflow
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Go / No-Go Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it convenes a single synchronized decision event where designated authorities poll launch criteria and render one committing verdict — go, hold, or no-go — before a high-exposure action.
Independent corroboration: The frozen evidence defines Go / No-Go Review as 'Convenes a single synchronized decision event where designated authorities poll launch criteria and render one committing verdict — go, hold, or no-go — before a high-exposure action', so its operative form is Decision, Gate & Allocation.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Aviation & Aeronautics
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Flight Readiness Reviews are the direct institutional lineage for the committing verdict.
Related originating lineages:
- Engineering & Design — Systems assurance contributes readiness evidence and independent technical authority.
Review outcome: Independent reviewer agreement; high confidence.
References¶
[1] National Aeronautics and Space Administration. "Launch Services Program Pre-Launch Readiness Reviews (NPD 8610.24C)". NASA Online Directives Information System, 2005. Requires a Go statement from every party polled before terminal count and requires records of the prelaunch readiness-review process. registry ↩
[2] Vaughan, Diane. The Challenger Launch Decision: Risky Technology, Culture, and Deviance at NASA. University of Chicago Press, 1996. Documents how repeated acceptance of anomalous evidence normalized deviance in NASA’s Challenger launch decision. registry ↩