Stage Gate Process¶

Prime #: 1204
Origin domain: Business Management
Subdomain: new product development → Business Management
Aliases: Phase Gate Process, Stage Gate Model

Core Idea¶

A stage-gate process partitions a long-horizon commitment into stages separated by go/no-go gates, each gate requiring evidence from the prior stage and licensing escalated commitment for the next. It expects most candidates to die at gates — the attrition funnel is a feature. Its force rests on two facts: gates carry explicit kill criteria, and gate-keepers are independent of the executors.

How would you explain it like I'm…

Checkpoint Gates

Imagine a big adventure split into steps, with a checkpoint gate after each one. At each gate you look at what you've learned so far and decide: keep going, or stop here. The further you go, the more you spend, so each gate asks for better proof before you're allowed through. It's totally fine — even expected — for lots of adventures to stop at a gate.

Go Or Stop Gates

A stage-gate process breaks a big, long commitment into stages, with a go/no-go decision gate between each one. At every gate you check the evidence gathered in the stage just finished and decide whether to keep going or kill the project. Each new stage costs more and locks you in more, so each gate demands stronger proof before letting you advance. This way you never bet the whole budget on early, weak evidence — you commit a little at a time. The funnel where most projects die at gates is the point of the design, not a failure of it.

Evidence Gated Funnel

A stage-gate process is a designed sequence in which a long-horizon commitment is partitioned into stages separated by go/no-go decision gates, where each gate requires evidence accumulated in the prior stage and licenses escalated resource commitment for the next. It has three parts: a sequence of stages, each producing evidence about whether the underlying bet is working; gates at the stage boundaries where an evidence-conditional go/no-go decision is taken; and escalating commitment, where each later stage costs more, locks in more, and demands more decisive evidence. The pattern expects most candidates to die at gates — the funnel is a feature, not a bug. Its core move is separating evidence generation from commitment escalation: you never commit the full budget on early evidence, because the gates let you commit incrementally, in proportion to what you have learned. A real gate differs from a mere check-in by having explicit kill criteria, not just go criteria, and gate-keepers independent of the people executing the stage.

A stage-gate process is a designed sequence in which a long-horizon commitment is partitioned into stages separated by go/no-go decision gates, with each gate requiring evidence accumulated in the prior stage and licensing escalated resource commitment for the next. The structural commitment is a triple: a sequence of stages, each producing a body of evidence about whether the underlying bet is working; gates at the stage boundaries at which an evidence-conditional go/no-go decision is taken; and escalating commitment, where each subsequent stage costs more, locks in more, and demands more decisive evidence to justify. The pattern expects most candidates to die at gates; the funnel is a feature, not a bug. What it makes visible is the separation of evidence generation from commitment escalation: the actor never has to commit the full project budget on initial-stage evidence, because the gate structure permits incremental commitment proportional to accumulated evidence. The total budget is decomposed into a sum of stage-conditional commitments rather than a single up-front bet, and the project decision is decomposed into a sequence of gate decisions. The intervention space is correspondingly rich: gate criteria, kill criteria, per-stage evidence requirements, advance-commitment levels, gate-keeper composition, and the option to revert a candidate to an earlier stage rather than killing it outright. The pattern's force depends on two facts that distinguish a real gate from a check-in: each gate has explicit kill criteria, not just go criteria, and the gate-keepers are independent of the stage executors; an instance lacking either is gate-shaped but missing the structural force.

Broad Use¶

New product development (canonical): discovery, scoping, business case, development, testing, and launch separated by go/no-go gates.
Pharmaceutical development: Phase 0 through IV, with evidence packages between phases and heavy attrition before approval.
Military acquisition: milestone decision points gated by review boards with evidence packages.
Venture capital: pre-seed through later rounds, each committing more capital and demanding more evidence.
Software releases: alpha, beta, release candidate, and general availability, each with explicit exit criteria.
Academic credentialing: coursework, qualifying exam, proposal and dissertation defences, each licensing escalated committee resources.
Real estate development: feasibility, entitlement, design, construction, and lease-up, each escalating capital.

Clarity¶

It exposes three things non-staged commitment hides: advance commitment is sliced, not all-or-nothing; the option to kill is built in and "no-go" is a normal outcome; and evidence requirements are stage-specific. It makes attrition explicit and acceptable.

Manages Complexity¶

It compresses an open-ended commitment problem into a sequence of design choices — stage scope, exit criteria, gate evidence package, commitment escalation — and organizes role specialization between executors and adjudicators.

Abstract Reasoning¶

It supports information-commitment matching (commit proportional to evidence), kill-criterion design, option value (staging is a sequence of real options), and a catalogue of failure modes (bureaucratised gates, kill-avoidance, gate-explosion).

Knowledge Transfer¶

Portfolio management: kill-criterion discipline ports as one question — "what would kill this candidate?" — to any staged investment.
Organizational design: gate-keeper independence ports as a rule — those who decide to advance should not be those whose work is judged.
Finance: real-option valuation ports into staged R&D budgeting, connecting valuation theory to organizational practice.
Selection frames: attrition-as-design ports as the view that high attrition is the signature of a well-tuned funnel, not failure.

Example¶

An oncology drug advances through microdosing, single-arm safety, mid-stage efficacy, and large-scale efficacy gates — each producing evidence that licenses the next commitment, each with explicit go and kill criteria, with roughly one in ten Phase-I candidates reaching approval by design.

Relationships to Other Primes¶

Parents (1) — more general patterns this builds on

Stage Gate Process is a kind of, typical Sequencing — Stage-gate is a sequence of precedence-ordered, evidence-conditional stages with escalating commitment — a specialization of sequencing (deliberate ordering of steps under precedence). The gate-decision chain is the load-bearing structure; sequencing is the genus.

Children (1) — more specific cases that build on this

Decision decompose Stage Gate Process — Each gate is a decision (resolve advance/terminate/revert); the prime is the structured sequence of gate decisions. The file: a decision is the 'building block' of which stage-gate is a sequence.

Path to root: Stage Gate Process → Sequencing → Dependency

Not to Be Confused With¶

Stage Gate Process is not Escalation of commitment because escalation is the pathology where sunk cost biases toward "go," whereas stage-gate is the designed defence against it — and a stage-gate exhibiting escalation has failed.
Stage Gate Process is not Prioritization because prioritization ranks candidates by value at one time, whereas stage-gate sequences and kills them across time against absolute evidence thresholds.
Stage Gate Process is not a Decision because a decision resolves alternatives at a point, whereas stage-gate is a sequence of evidence-conditional decisions with escalating commitment between them.