Stage-Gate Activation Review¶
Governance protocol — instantiates Activation Energy Cost-Benefit Analysis
Divides activation investment into decision gates so commitment increases only when evidence about threshold distance, adoption, and benefit realization improves.
Even a barrier that is worth crossing rarely needs to be crossed in one leap. Stage-Gate Activation Review is the governance protocol that breaks a single large activation commitment into a sequence of funded stages separated by gates — and at each gate a predeclared advance / hold / kill decision releases the next tranche of money only if the evidence has actually improved. Its defining move is to refuse authorizing the whole activation budget at once: the organization buys the right to continue stage by stage, keeping a cheap exit at every gate. Where Barrier Height Estimation sizes the barrier and Break-Even Activation Model prices it, this mechanism governs how commitment escalates over time against that pricing — it is a decision architecture, not a calculation.
Example¶
A biotech holds a promising drug candidate. Taking it to market is an enormous activation barrier — years of work and a very large budget before any revenue. Rather than commit the full development cost on the strength of early lab data, the program is split into gates: preclinical, then a small first-in-human safety stage, then a mid-stage efficacy readout, then a large confirmatory stage, then filing. Each gate carries kill criteria fixed in advance — a toxicity signal, no efficacy trend, a competitor reaching market first. Capital flows only to candidates whose evidence keeps improving. When the mid-stage readout on this candidate shows no efficacy trend, the program is killed at a gate that cost a fraction of full development, and the freed budget is redeployed to the next candidate in the pipeline. The firm pays the full activation cost only for the survivors — the ones whose threshold-distance evidence held up gate after gate.
How it works¶
- Place gates at evidence milestones. Each stage is scoped to resolve one specific uncertainty (safety, adoption, unit economics), so passing a gate means something.
- Predeclare advance / hold / kill criteria before the stage runs — written down while judgment is cold, so a champion cannot rationalize a bad readout afterward.
- Fund only the current tranche. The next stage's money is contingent, never pre-authorized.
- Make exit the cheap default. A kill at an early gate is a designed outcome, not a failure of nerve.
- Redeploy on kill. Freed resources are explicitly routed to the next-best use rather than left to drift into the dead program.
Tuning parameters¶
- Gate count / granularity — more gates buy more option value and more chances to stop, but add review overhead and slow the program; too few gates and it drifts back toward all-or-nothing.
- Kill-criteria strictness — how bad a readout must be to stop. Strict criteria throttle escalation but can execute a slow-maturing initiative that was always meant to lag early.
- Tranche size — how much capital each gate releases; smaller tranches preserve optionality but raise the fixed cost of running gates.
- Gate-owner independence — whether the people who decide are separate from the program's champion. Independence hardens the discipline at the cost of speed and goodwill.
- Evidence-bar escalation — how much stronger the evidence each successive gate demands before releasing more money.
When it helps, and when it misleads¶
Its strength is structural: it converts an all-or-nothing bet into a series of small, reversible bets, and it throttles the escalation-of-commitment dynamic that makes activation spending so dangerous — you cannot pour the whole budget after sunk cost because the budget is not yours to pour until the next gate.
Its failure mode is that gates decay into rubber stamps. The classic misuse is a review board where nothing is ever killed because the champion dominates the room and each gate becomes a progress-reporting formality; the ritual runs while escalation of commitment survives it untouched.[n1] The opposite error is rigidity — mechanical gates that kill a genuinely slow-to-mature initiative whose value was always going to appear late. The discipline that guards against both is predeclared, independently owned kill criteria plus a nonzero kill rate tracked as a health metric: a gate process that never stops anything is not protecting anything.
How it implements the components¶
Stage-Gate Activation Review realizes the sequencing-and-governance side of the archetype — how commitment is released over time, not how it is sized or priced:
staged_probe_or_pilot_path— the gate sequence is the staged path; each stage is a bounded increment of activation that buys the right to the next.decision_and_stop_rule— the advance / hold / kill criteria at each gate are the stop rule, applied repeatedly rather than once.reversibility_and_exit_path— every gate is a predefined, low-cost exit point, so walking away is always an available and legitimate move.opportunity_cost_comparison— a kill frees the tranche for redeployment, and the gate decision makes that next-best use explicit at the moment of stopping.
The barrier-sizing components (activation_barrier_model, threshold_distance_estimate, activation_cost_inventory) belong to Barrier Height Estimation, and the benefit valuation (post_threshold_benefit_model, self_sustainability_condition) belongs to Break-Even Activation Model; this protocol governs commitment but neither sizes nor prices it.
Related¶
- Instantiates: Activation Energy Cost-Benefit Analysis — supplies the commitment-sequencing discipline the appraisal needs once a barrier looks worth staging.
- Consumes: Break-Even Activation Model sets the target condition each gate is testing progress toward; Barrier Height Estimation tells the designer which uncertainties each stage should resolve.
- Sibling mechanisms: Barrier Height Estimation · Break-Even Activation Model · Pilot Option Probe · Counterfactual Non-Activation Comparison · Sensitivity and Scenario Sweep · Post-Crossing Feedback Check · Activation Hurdle-Rate Rule
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Stage-Gate Activation Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it divides activation investment into decision gates so commitment increases only when evidence about threshold distance, adoption, and benefit realization improves.
Independent corroboration: The frozen evidence defines Stage-Gate Activation Review as 'Divides activation investment into decision gates so commitment increases only when evidence about threshold distance, adoption, and benefit realization improves', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Stage-Gate Activation 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: Innovation & Entrepreneurship
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Increasing investment only at evidence-bearing gates is Cooper's named Stage-Gate innovation process. His original product-innovation research defines stages separated by go/kill resource decisions; management later broadens application.
Related originating lineages:
- Economics & Finance — Tranches preserve option value.
- Engineering & Design — engineering_design contributes engineering design, reliability, and systems-safety practice to this mechanism's defining operation—Divides activation investment into decision gates so commitment increases only when evidence about threshold distance, adoption, and benefit realization improves—without displacing the selected primary historical lineage.
- Operations Research — operations_research contributes operations research, optimization, and queueing analysis to this mechanism's defining operation—Divides activation investment into decision gates so commitment increases only when evidence about threshold distance, adoption, and benefit realization improves—without displacing the selected primary historical lineage.
- Organizational & Management Science — Organizational design, management, and operational governance supplies a parallel or contributing lineage for the mechanism's defining operation: divides activation investment into decision gates so commitment increases only when evidence about threshold distance, adoption, and benefit realization improves.
Review resolution: The blind reviewers disagree on primary lineage (organizational_management versus innovation_entrepreneurship). Authoritative or primary research supports innovation_entrepreneurship as the best historical origin: Increasing investment only at evidence-bearing gates is Cooper's named Stage-Gate innovation process. His original product-innovation research defines stages separated by go/kill resource decisions; management later broadens application. The cited Cooper, Third-Generation New Product Processes; Cooper, The Stage-Gate Idea-to-Launch Process directly supports the mechanism's defining operation. All independently supported contributing domains are retained without an arbitrary cap. origin_mode=single_lineage records lineage, while domain_reach=multi_domain records later applicability separately from provenance.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Researched adjudication after independent review; high confidence.
Sources consulted:
Notes¶
A gate is not a milestone. A milestone reports that progress happened; a gate can stop the program. Teams that convert their gates into milestone reviews keep the ceremony and lose the mechanism — the whole value of the protocol is the standing possibility of a kill.
[n1] Stage-Gate — Robert G. Cooper's new-product-development framework, in which projects pass through gates carrying explicit go / kill decisions. Its intended discipline is a nonzero kill rate; when gates never kill, the framework's protection against escalation of commitment is lost and only its overhead remains. ↩