Stage-Gate Review¶
Phase-gate protocol — instantiates Escalation Exit Gate
Places an authorized, independent gate at each phase boundary, so passage to the next phase is never automatic but re-earned against current evidence.
A Stage-Gate Review chops a project into phases and installs a decision point at every boundary, where an authorized gatekeeper — separate from the delivery team — decides whether current evidence justifies authorizing the next phase before any of its resources are released. Its defining move is phase-boundary authorization on a schedule: passage from one stage to the next is never automatic, and momentum from completed work never carries into the next phase by default; each crossing must be re-earned against forward criteria. It becomes an escalation exit gate — rather than a completion checklist — precisely when the gate holds real authority to withhold the next phase and when it tests continuation against present evidence instead of merely confirming that the previous phase's tasks were finished.
Example¶
A consumer-electronics company runs a new smart thermostat through a five-gate new-product-development process: Scoping, Business Case, Development, Testing, and Launch, with a gate before each. At Gate 3 — the point before the expensive Development phase — an independent gate board of product, quality, and finance leads who are not on the project team reviews the current evidence against criteria fixed in advance: validated demand, a bill of materials under the cost target, and no unresolved safety risks. Demand is strong, but the bill of materials sits 20% over target because a critical sensor is single-sourced at a premium.
The board does not cancel the thermostat, and it does not invent a new product. It withholds authorization for Development and returns the project to Scoping with one condition: re-source the sensor and re-present at the gate. The board's authority is the whole point — because it is independent and the criteria were set before anyone was invested in the outcome, "we've already cleared two gates" carries no weight against a bill of materials that misses the number. The review recurs at every phase boundary; the cadence simply is the product's lifecycle.
How it works¶
- Chop the project into phases with a gate at each boundary. Work advances in stages, and every boundary is a decision, not a formality.
- Set forward pass criteria before each phase. Each gate's criteria describe the evidence the phase must produce, not the tasks it must complete — evidence is what lets the gate deny a doomed but on-schedule project.
- Staff the gate independently. The gatekeeper is separate from the delivery team and holds the authority to withhold the next phase.
- Authorize or withhold at each gate. The outcome is passage to the next phase, or a withheld authorization that returns the work with conditions to re-present.
- Recur at every boundary. The gates are a standing sequence; the review rhythm is the lifecycle itself.
Tuning parameters¶
- Number and placement of gates — more gates give tighter control and catch drift early, but multiply overhead and slow the lifecycle.
- Criteria type — evidence-based versus completion-based. Evidence criteria are what make it an exit gate; completion criteria turn it back into a checklist that cannot deny a failing project.
- Gatekeeper independence — peer reviewers versus a body fully outside the sponsor chain. Deeper independence resists "we've come too far" but costs speed and context.
- Gate authority — advisory versus a binding power to withhold. Binding force is what stops the gate from being ceremonial.
- Conditional-pass allowance — hard pass/fail versus pass-with-conditions. Conditional passes handle near-misses gracefully but can become a soft way to wave everything through.
When it helps, and when it misleads¶
Its strength is that it converts a lifecycle into a series of earned authorizations, so escalation cannot ride momentum from one phase into the next: the independent gate is what defeats the "we're already three phases in" reflex, because the gatekeeper owes nothing to the phases already completed. The canonical form is Robert G. Cooper's Stage-Gate process for new-product development, which separates project stages with go/kill gates staffed by a cross-functional gatekeeping group.[n1]
Its central failure mode is the gate that degrades into a completion checklist — "did we finish the planned tasks?" — and rubber-stamps progression regardless of whether the evidence still supports the bet; a gate that has never withheld a phase is worse than none, because it dresses escalation in the appearance of discipline. A related failure is gatekeeper capture, a board that depends on the sponsor. The guarding discipline is to write gate criteria as forward evidence rather than deliverable completion, and to keep — and occasionally use — the authority to withhold.
How it implements the components¶
continuation_criteria— each gate carries pre-set forward criteria that the phase's evidence must clear to earn passage to the next phase.independent_review_gate— the gatekeeper is structurally separate from the delivery team and holds the authority to withhold the next phase.review_cadence— gates recur at every phase boundary, so the review rhythm is the project lifecycle and continuation is re-earned at each crossing.
It does not meter funding in tranches or fire a capital release/cut (stop_or_pivot_rule) — that action rule is Funding Tranche Review's, its nearest twin; nor does it inventory salvageable value (salvage_value_map) or plan the dignified wind-down (face_saving_exit_path), which are Independent Project Audit and Post-Investment Review. Its gate authorizes or withholds a phase; it does not run a stop/pivot/transfer action menu.
Related¶
- Instantiates: Escalation Exit Gate — supplies the standing, independent phase gate that keeps a project's next phase from being funded by default.
- Sibling mechanisms: Funding Tranche Review · Independent Project Audit · Pivot Gate · Post-Investment Review · Project Kill Criteria · Stop-Loss Rule
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Stage-Gate Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it places an authorized, independent gate at each phase boundary, so passage to the next phase is never automatic but re-earned against current evidence.
Independent corroboration: The frozen evidence defines Stage-Gate Review as 'Places an authorized, independent gate at each phase boundary, so passage to the next phase is never automatic but re-earned against current evidence', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Stage-Gate Review includes features of a bounded evaluation of existing evidence or work that produces a finding or disposition, but its defining operation is a case-specific gate, selection, routing, prioritization, or resource disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: Authorized independent review at phase boundaries is stage-gate governance.
Related originating lineages:
- Engineering & Design — Lifecycle reviews verify maturity.
- Innovation & Entrepreneurship — Innovation management and experimental venture practice supplies a parallel or contributing lineage for the mechanism's defining operation: places an authorized, independent gate at each phase boundary, so passage to the next phase is never automatic but re-earned against current evidence.
- Law & Governance — Passage requires legitimate authority and criteria.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: places an authorized, independent gate at each phase boundary, so passage to the next phase is never automatic but re-earned against current evidence.
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin disagreement, origin mode disagreement, encyclopedia synthesis disagreement. I preserve every independently explained alternate from both records rather than imposing a numeric cap. I retain convergent because the combined evidence shows independent disciplinary development. The broader reach of universal records portability separately from historical provenance; encyclopedia_synthesis=true preserves the affirmative synthesis judgment where either reviewer identified one.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] Robert G. Cooper's Stage-Gate is a widely used new-product-development framework that divides a project into stages separated by go/kill gates, at which a cross-functional gatekeeping group decides whether the project proceeds to the next stage. ↩