Stage Gate Process¶
Core Idea¶
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 stage-gate 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 structural 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.
How would you explain it like I'm…
Checkpoint Gates
Go Or Stop Gates
Evidence Gated Funnel
Structural Signature¶
the long-horizon commitment to be partitioned — the ordered sequence of evidence-producing stages — the gate as evidence-conditional go/no-go boundary — the escalating-commitment ladder — the kill-criterion alongside the go-criterion — the executor/adjudicator independence invariant — the attrition funnel as expected output
A configuration exhibits the stage-gate pattern when each of the following holds:
- A partitionable commitment. There is a single high-uncertainty, long-horizon bet whose total cost can be decomposed into a sequence of smaller, conditionally-incurred commitments rather than a lump up-front outlay.
- An ordered sequence of stages. Each stage is a bounded segment of work whose product is a defined body of evidence about whether the underlying bet is working. Stages are ordered, and evidence accumulates across them.
- Gates at the stage boundaries. At each boundary an explicit decision is taken, conditioned on the evidence produced so far, that resolves to advance, terminate, or (optionally) revert. A gate is a decision moment, not a check-in.
- Escalating commitment. Each successive stage costs more, locks in more, and demands stronger evidence to justify; the commitment authorised by a gate-pass must be matched to the strength of the evidence behind it.
- Paired go and kill criteria. A genuine gate carries explicit thresholds for termination, not only for advancement; "no-go" is a designed, normal outcome. Absent kill criteria, the gate degenerates into a rubber-stamp.
- Adjudicator–executor independence. The party deciding whether to advance is structurally distinct from the party whose work is being judged; without this separation the go/no-go decision loses its honesty.
- An attrition funnel. Most candidates are expected to die at gates; high attrition is the signature of a well-tuned selection mechanism, not a string of failures.
Composed, these turn one irreducible project decision into a chain of evidence-conditional gate decisions, and a single bet into a sum of staged, revocable commitments whose funnel of kills is the intended product.
What It Is Not¶
- Not a
decisiontaken at one moment. Adecisionresolves an alternative at a point; stage-gate is a sequence of evidence-conditional decisions with escalating commitment between them, so the unit of analysis is the chain, not the gate. - Not
escalation_of_commitment. That pathology is the failure of a stage-gate — sunk cost biasing the gate toward "go"; the prime's kill criteria and adjudicator independence exist precisely to resist it, so the two are antagonists, not synonyms. - Not
precedent_stare_decisis. Precedent binds a present decision to a past one by analogy; a gate conditions advancement on freshly produced evidence about this bet, with no claim that prior cases govern. - Not
prioritization. Prioritisation ranks candidates by value at one time; stage-gate sequences and kills them across time as evidence accumulates, and high attrition is its intended output, not a ranking artefact. - Not
local_autonomy_tiered_escalation. That routes a decision upward by severity; a gate is a forward checkpoint that the same candidate must clear to proceed, independent of any authority hierarchy. - Not mere
monitoring. Monitoring observes without a designed branch point; a gate is a decision moment with paired go/kill criteria — a check-in that cannot terminate the candidate is gate-shaped but lacks the structural force. - Common misclassification. Calling any phased plan with review meetings "stage-gate." If the reviews lack explicit kill criteria and the reviewers are the executors themselves, the gates are rubber-stamps; the diagnostic is whether any candidate has actually been killed at a late gate.
Broad Use¶
- New product development (canonical): staged sequences of discovery, scoping, business case, development, testing, and launch, separated by idea screens and go-to-development, go-to-testing, and go-to-launch gates.[1]
- Pharmaceutical development: Phase 0 through Phase IV, with evidence packages required between phases and heavy attrition between early phases and approval.[2]
- Military acquisition: milestone decision points (technology development, engineering and manufacturing, production) gated by review boards with evidence packages.[3]
- Venture capital: pre-seed through later rounds, each committing more capital, requiring more evidence, and applying explicit gate criteria.
- Software releases: alpha, beta, release candidate, and general availability, each with explicit exit criteria and an escalation in user exposure.[4]
- Academic credentialing: coursework, qualifying exam, proposal defence, dissertation defence, and publication, each gate licensing escalated commitment of advisor and committee resources.
- Real estate development: site identification, feasibility, entitlement, design, construction, and lease-up, each escalating capital and requiring evidence (zoning, permits, pre-leasing).[5]
- Aerospace systems engineering: the design-review sequence, each gate requiring evidence packages and licensing escalated commitment.
In each substrate the same triple recurs — sequenced stages producing evidence, gates resolving evidence into go/no-go, and escalating commitment — independently rediscovered because the underlying decision-economics recur.
Clarity¶
Naming a process as stage-gate exposes three things non-staged commitment hides. The advance commitment is not all-or-nothing at project start; it is sliced into incremental commitments, each licensed by accumulated evidence. The option to kill is built into the structure — gates are decision moments, not check-ins, and "no-go" is a normal outcome rather than a failure of the stage. And the evidence requirements are stage-specific: an early stage needs feasibility or safety evidence, a late stage needs efficacy evidence at scale, and mismatching evidence to stage — demanding scale-level proof at the first gate — is a common pathology.
The pattern also makes attrition explicit and acceptable. A funnel in which nine of ten candidates die at an intermediate gate is not broken; it is working as designed. This reframing is itself clarifying: it converts what looks, under a non-staged frame, like a string of failures into the expected operation of a well-designed selection mechanism, and it redirects attention from "why do so many die?" to "are the gates killing the right candidates at the right stages?"
Manages Complexity¶
Stage-gate compresses an open-ended, high-uncertainty commitment problem into a tractable sequence of design choices: choose the stage scope, define the stage exit criteria, define the gate evidence package, and define the commitment escalation per gate-pass. The decision problem becomes a sequence of gate decisions rather than a single irreducible project decision, and the budget becomes a sum of conditional commitments rather than a lump bet.
It also organises role specialisation. Stage executors and gate adjudicators are different roles — and should be, since gate-keepers who also execute stages carry a conflict of interest — and evidence assemblers differ from evaluators. The gate structure thereby provides natural handoff points and review rituals, distributing a complex commitment across clearly separated responsibilities. This separation is not incidental decoration: it is what keeps the go/no-go decision honest, because the person deciding whether to advance is not the person whose work is being judged.
Abstract Reasoning¶
The frame supports reasoning about commitment under uncertainty, attrition, and option value. Information-commitment matching: at each gate the commitment for the next stage should be matched to the strength of evidence from the prior stage, and over-committing on weak evidence — pouring late-stage budget into a candidate with a weak earlier signal — is a classic failure. Kill-criterion design: gates need explicit thresholds below which a candidate is killed; without them, gates degenerate into rubber-stamps. Option value: the staged structure is equivalent to a sequence of real options, and the value of preserving optionality grows with downstream uncertainty. Stage-skipping and reverting: strong early evidence can support skipping a stage, and a late-stage failure can support reverting rather than killing, so the graph is not strictly linear. And a characteristic catalogue of failure modes falls out of the structure: bureaucratised gates that become compliance checks, evidence-quality drift where stages produce evidence shaped to pass rather than to inform, kill-avoidance where no candidate ever fails, gate-explosion that produces paralysis, and the urgency-override that skips a gate without evidence.
Knowledge Transfer¶
The roles map across substrates: the stage is a bounded segment of work producing a defined evidence package; the gate is the evidence-conditional go/no-go at the boundary; the escalation is the increase in committed capital, exposure, or lock-in that each gate-pass authorises; the go and kill criteria are the conditions for advance and termination; the gate-keeper is the decision-maker structurally independent of the executors; and the attrition profile and optionality value are the portfolio-level quantities the structure exposes. The intervention vocabulary ports surgically, in part because the pattern has been independently codified in multiple high-stakes domains, each refining a different aspect — one domain best at evidence packages, another at round economics, another at gate-keeper independence, another at gate-process design.
Concrete transfers are well attested. Gate-criteria design ports from venture-capital term sheets to regulatory evidence packages to acquisition milestone reviews, each substrate having learned conventions for adequate per-stage evidence. Kill-criterion discipline ports as a single diagnostic question — "what would kill this candidate?" — applicable to any staged investment. Information-commitment matching ports as a portfolio rule: commit proportional to evidence quality. Gate-keeper independence ports as an organisational-design rule: the people who decide to advance should not be the people whose work is judged. Attrition-as-design ports as a portfolio frame in which high attrition is the signature of a well-designed funnel. And real- option valuation ports from finance into staged R&D budgeting, connecting formal valuation theory to organisational practice.[6] A single worked instance shows the substance: an oncology drug advancing through microdosing, single-arm safety, mid-stage efficacy, and large-scale efficacy gates, each producing evidence that licenses the next-stage commitment, each with explicit go and kill criteria, the total commitment sliced rather than committed up front, and roughly one in ten Phase-I candidates reaching approval — by design, not by failure.[7] The same structure, with the same intervention vocabulary, governs a venture portfolio, an aerospace design review, and a doctoral programme.
Examples¶
Formal/abstract¶
Sequential hypothesis testing as a multi-stage decision problem instantiates the stage-gate structure formally. Consider a candidate treatment whose true effect \(\theta\) is unknown. The partitionable commitment is the full trial-and-approval budget; the ordered stages are a sequence of experiments of increasing size \(n_1 < n_2 < n_3\), each producing an evidence statistic \(T_k\) (an estimated effect with shrinking confidence interval). At each gate, a decision rule compares \(T_k\) against two thresholds: a go boundary above which the candidate advances and an explicit kill boundary below which it is terminated — the classical Wald sequential probability ratio test structure, where between the boundaries you keep sampling and outside them you stop.[8] The escalating commitment is exact: each stage's sample size, and hence cost, grows, so the evidence bar to license the next stage rises with it. The attrition funnel is the prior-weighted fraction of candidates whose \(T_k\) falls below the kill boundary at each gate — and the design optimises expected total cost by killing weak candidates cheaply and early. The adjudicator independence invariant maps to a pre-registered, blinded analysis: whoever ran the experiment cannot move the boundary after seeing \(T_k\). This shows the intervention space directly — set kill thresholds to control false-advance rate, set stage sizes to match commitment to evidence quality, and read the attrition profile as a tuning diagnostic rather than a failure log.
Mapped back: The sequential-test gates, go/kill boundaries, escalating sample-size commitment, and pre-registration independence are the prime's stages, paired criteria, escalation ladder, and adjudicator-independence invariant rendered as a formal decision rule.
Applied/industry¶
Venture-capital financing rounds run the stage-gate pattern at portfolio scale. The partitionable commitment is the total capital a startup would need to reach profitability; instead of writing one cheque, investors slice it into pre-seed, seed, Series A, B, and C stages, each a bounded segment of company-building that produces evidence — a working prototype, then early users, then revenue retention, then unit economics, then scalable growth.[9] Each gate is a financing decision conditioned on the prior stage's metrics, and the escalation is steep: a Series B round commits far more capital and demands far stronger evidence than a seed round. The kill criterion is the down-round-or-no-round outcome, a designed and normal event — most seed-funded companies never raise a Series A, and that high attrition funnel is the signature of a working selection mechanism, not a string of disasters.[9] The adjudicator–executor independence invariant appears as the investment committee and new lead investors who are structurally distinct from the founders being judged. The pattern diagnoses two classic pathologies: over- committing on weak evidence (a hot seed market pouring growth-stage money into companies with no retention signal) and kill-avoidance (insiders bridging a failing company round after round rather than letting the gate do its work). A parallel applied instance is software release management: alpha, beta, release candidate, and general availability are stages with explicit exit criteria, the escalation is user-exposure rather than capital, and a feature killed at beta is the gate operating as designed.
Mapped back: Financing rounds and release tiers are stages; the funding decision and the GA cutover are gates with paired go/kill criteria; the rising cheque size and widening user exposure are the escalation ladder; and the high fraction of startups and features that die between stages is the intended attrition funnel.
Structural Tensions¶
T1 — Evidence Generation versus Commitment Escalation (scopal). The structure separates producing evidence from committing resources, but the two cannot be fully decoupled: late-stage evidence is often only generable by making the late-stage commitment (you learn whether a drug scales by running the scale trial). The prime's clean "commit proportional to evidence" rule stops being the whole story precisely when evidence is endogenous to commitment. Failure mode: gating on evidence that the prior stage structurally cannot produce, freezing genuinely promising candidates at a gate that demands proof only the next stage could yield. Diagnostic: ask whether the gate's evidence requirement is producible within the prior stage's budget, or whether it presupposes the very commitment it gates.
T2 — Kill Discipline versus Sunk-Cost Drift (temporal). Kill criteria are set ex ante, but they are applied after resources, reputations, and careers have been invested — and the accumulated stake biases the adjudicator toward "go." The gate's honesty decays over time precisely as the candidate progresses, because each surviving stage raises the cost of killing. Failure mode: kill-avoidance, in which no candidate ever fails a late gate because terminating it would indict prior gate decisions — the funnel silently flattens into a conveyor. Diagnostic: check whether any candidate has actually been killed at the late gates, or only at the cheap early ones; an all-pass late funnel is the signature.
T3 — Adjudicator Independence versus Adjudicator Competence (coupling). The prime demands that gate-keepers be structurally distinct from executors to keep the decision honest — but the people most competent to judge the evidence are often the executors themselves, who hold the domain knowledge. Independence and competence pull in opposite directions. Failure mode: an independent gate populated by adjudicators who cannot actually read the evidence, so the gate degenerates into a procedural rubber-stamp that looks honest while rubber- stamping. Diagnostic: ask whether the gate-keepers could articulate the specific technical reason a candidate should be killed, or only whether the paperwork is complete.
T4 — Funnel Attrition versus Pipeline Starvation (scalar, local vs global). High attrition is locally healthy — the signature of a well-tuned selection mechanism — but globally, a too-aggressive funnel can starve the portfolio of survivors, killing candidates that would have succeeded given more stages. The gate that optimises per-candidate evidence quality can degrade portfolio yield. Failure mode: tuning kill thresholds to maximise the purity of survivors while the absolute number of approved outputs collapses below what the enterprise needs. Diagnostic: monitor not just the kill rate but the end-of-funnel throughput; rising attrition with falling final yield signals over-selection, not discipline.
T5 — Sequential Gates versus Irreversible Lead Time (temporal/coupling). The staged structure assumes commitment can be deferred until evidence licenses it — but some commitments have lead times longer than the stage that would justify them, forcing pre-commitment before the gate. Where long-lead procurement, hiring, or capacity must begin before its gate, the gate becomes a formality ratifying a decision already made. Failure mode: the urgency-override, where a gate is skipped or pre-empted "because we had to order the long-lead item anyway," quietly converting a real gate into theatre. Diagnostic: identify any stage whose enabling commitments must begin before the prior gate closes — those gates are structurally compromised.
T6 — Evidence Fidelity versus Gameable Metrics (measurement). Gates condition on evidence, but evidence is produced by the executors who benefit from passing — so the measured evidence drifts toward what passes the gate rather than what informs the decision. The prime's reliance on evidence-conditional gating presumes the evidence is honest; when the metric becomes a target, it ceases to measure. Failure mode: evidence-quality drift, where stages optimise the gate statistic (enrolment numbers, demo polish, vanity metrics) while the underlying bet's true signal is unmeasured. Diagnostic: ask whether the gate criterion has remained a leading indicator of downstream success, or whether candidates that sailed through later failed in the field — a sign the metric has decoupled from reality.
Structural–Framed Character¶
Stage-gate sits at the upper edge of the mixed-framed band on the structural–framed spectrum. Underneath there is a genuine relational skeleton — a long bet decomposed into a sequence of evidence-conditional branch points with escalating commitment — but the prime is bound to organisational decision-making tightly enough that invoking it imports a managerial frame rather than merely recognising a pattern already wired into a physical system.
Two diagnostics drive the grade hardest. Institutional origin and human-practice-bound both read fully framed: every native instance — FDA Phase 0–IV packages, DAB milestone reviews, venture financing rounds, software release tiers, doctoral qualifying exams — presupposes an institution that codifies stages, convenes gate-keepers, and authorises budget. The load-bearing structural facts the Core Idea insists on, paired kill criteria and adjudicator–executor independence, are not features of any physical substrate; they are governance arrangements that only exist where there are roles, parties, and decision rights. There is no thermostat or chemical network that "kills a candidate at a gate." The remaining diagnostics sit at the middle: the vocabulary travels only partly — "stage," "gate," "go/no-go," "kill criterion," "funnel" carry a project-management home lexicon that each domain must adopt rather than retell freely — and invoking the prime half-imports an evaluative posture (high attrition is good, kill-avoidance is bad), so it is not value-neutral until you specify what it does.
The honest concession is that the relational core is real, and the formal Wald sequential-test example shows the gate/escalation/attrition triple can be written as a pure decision rule. But that formal rendering is the exception that proves the framing: it must strip away the institutional machinery (committees, evidence packages, role separation) that constitutes stage-gate in every working instance. With institutional origin and human-practice-bound both pinned high and the rest at the middle, the aggregate sits at 0.7 — the top of the mixed-framed band — matching the assigned grade.
Substrate Independence¶
Stage-gate is a strongly substrate-independent prime within its band — composite 4 / 5 on the substrate-independence scale. Its domain breadth is wide (4 / 5): the same triple of evidence-producing stages, evidence-conditional gates, and an escalating-commitment ladder was independently rediscovered in pharmaceutical development (Phase 0–IV with attrition between phases), military acquisition (milestone decision boards), venture capital (pre-seed through Series C financing rounds), software release management (alpha, beta, release candidate, general availability), academic credentialing (qualifying exam, proposal defence, dissertation defence), and real-estate development (feasibility, entitlement, construction, lease-up). The structural abstraction is real but not maximal (3 / 5): the relational skeleton — slice a long bet into revocable, evidence-licensed increments — is medium-neutral, yet the load-bearing facts the Core Idea insists on (paired kill criteria, adjudicator–executor independence) are governance arrangements that presuppose roles, parties, and decision rights, so no thermostat or chemical network "kills a candidate at a gate." That ceiling is what holds the composite below the top: every working instance is a human project. What lifts it to a 4 is exceptionally strong transfer evidence (5 / 5) — the pattern has been formally codified in domain after domain, each refining a different facet (evidence packages, round economics, gate-keeper independence), with the Wald sequential-test rule showing the gate/escalation/attrition triple as a pure decision rule and real-option valuation porting from finance into staged R&D budgeting.
- Composite substrate independence — 4 / 5
- Domain breadth — 4 / 5
- Structural abstraction — 3 / 5
- Transfer evidence — 5 / 5
Relationships to Other Abstractions¶
Current abstraction Stage Gate Process Prime
Parents (1) — more general patterns this builds on
-
Stage Gate Process is a kind of, typical Sequencing Prime
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 Prime decompose Stage Gate Process
Each gate is a
decision(resolve advance/terminate/revert); the prime is the structured sequence of gate decisions.a decision is the 'building block' of which stage-gate is a sequence. After the cognitive_science frame is stripped away, the retained structural roles are those of Stage Gate Process: Partition a long commitment into evidence-gated stages with escalating commitment and a funnel of kills. Decision adds the local frame and commitments expressed in its identity: Committing to one alternative from a set under uncertainty and trade-off, collapsing open deliberation into a chosen path and foreclosing the others. The parent pattern remains recognizable without that vocabulary, while the child is the framed realization of it. That preservation test establishes decomposition rather than taxonomic subsumption.
Hierarchy paths (3) — routes to 3 parentless roots
- Stage Gate Process → Sequencing → Optimization
- Stage Gate Process → Sequencing → Dependency
- Stage Gate Process → Sequencing → Time
Neighborhood in Abstraction Space¶
Stage Gate Process sits among the more crowded primes in the catalog (9th percentile for distinctiveness): several abstractions describe nearly the same structure, so a description that fits it will tend to fit its neighbors too — transporting it usually means disambiguating within this family rather than landing on it exactly.
Family — Event Phases & Staged Recovery (10 primes)
Nearest neighbors
- Funnel Analysis — 0.80
- Evidence-Latency Window — 0.76
- Optimal Stopping Rule — 0.76
- Decision — 0.75
- Decision Cycle Subordination — 0.74
Computed from structural-signature embeddings · 2026-09-10
Not to Be Confused With¶
The sharpest confusion is with escalation_of_commitment. The two share
the vocabulary of staged investment and sunk cost, but they are structural
opposites in their stance toward continuation. escalation_of_commitment is
the pathology by which prior investment biases a decision-maker toward
throwing good resources after bad — the more committed, the harder to quit.
Stage-gate is the designed defence against exactly that bias: it inserts
gates with explicit kill criteria and adjudicators independent of the
executors, so that continuation must be re-earned on fresh evidence rather
than inherited from past spending. The relationship is therefore adversarial,
not equivalent — and the clean diagnostic is that a stage-gate process which
exhibits escalation of commitment (no candidate ever killed at a late gate)
is a stage-gate that has failed at its core purpose. A practitioner who
conflates them will treat the funnel's high attrition as the disease when it
is the cure.
A second confusion is with prioritization. Both winnow a population of
candidates, but prioritisation operates at a single time-slice — it ranks
available options by value or urgency and allocates scarce resource to the
top of the list. Stage-gate operates across time and commitment levels: a
candidate is not ranked against peers but advanced or killed against an
absolute evidence threshold appropriate to its stage, with the commitment
ladder rising at each pass. A prioritised list can be re-ranked freely as
values shift; a stage-gate candidate that fails a kill criterion is removed,
not demoted. The distinction matters because the interventions differ — to
fix a prioritisation failure you change the ranking function, whereas to fix
a stage-gate failure you change the gate criteria, the kill thresholds, or
the adjudicator's independence.
Finally, stage-gate is distinct from decision simpliciter. A decision
is the atomic act of resolving among alternatives at a point; it is the
building block of which a stage-gate process is a structured sequence. The
prime's contribution is everything that surrounds the individual gate
decisions — the ordered stages that produce the evidence each decision
conditions on, the escalating commitment that makes later decisions costlier,
and the attrition funnel that is the sequence's intended product. Treating a
stage-gate as a single big decision collapses precisely the structure
(decomposition into revocable, evidence-licensed increments) that gives the
prime its force, and forfeits the option value the staged form preserves.
Solution Archetypes¶
Solution archetypes in the catalog that build on this prime — directly (this prime is a source ingredient) or as a related prime.
Built directly on this prime (6)
- Adaptive Opponent Rehearsal: Rehearse a plan against an adaptive opponent before commitment so hidden assumptions surface as the opponent moves, counters, exploits, and changes the state of play.▸ Mechanisms (10)
- Adversarial Scenario Sprint — A single-sitting, time-boxed run of one adversarial scenario that stands up a quick opponent and harvests the plan's hidden assumptions before the clock runs out.
- After-Action Learning Review — A structured group retrospective that maps the causes of a completed effort across the whole team and feeds the lessons forward through a mentor channel.
- Cyber Range or Simulated Adversary Exercise — An instrumented, isolated replica of a real system in which a live or emulated adversary attacks while defenders respond, so the plan meets a technically faithful opponent instead of a talked-through one.
- Decision Wargame Workshop — A facilitated workshop built around one pending decision, playing the plan against competitor countermoves and feeding what breaks straight into a go/adjust/hold commitment gate.
- Escalation Ladder Exercise — Plays a plan up a pre-defined ladder of increasingly severe moves and counter-moves, scoring the regret at each rung to find where control is lost and de-escalation stops being available.
- Inject Deck — A pre-authored set of scripted events, messages, and complications released on cue during an exercise, so the plan meets new information and pressure it can't rehearse around.
- Matrix Game — A lightweight game in which players propose an action plus reasons it should succeed, and an adjudicator rules on the outcome by weighing the arguments — strategic interaction approximated by argument, not simulation.
- Move-Countermove Playbook — A durable, living reference that maps the opponent's likely moves to your pre-worked counters and their counters-to-your-counter, distilled from rehearsals so the interaction can be prepared rather than improvised.
- Red Team / Blue Team Session — An exercise built around an independent, protected challenger team chartered to defeat the plan while the plan's owners defend it, with a facilitator keeping the attack rigorous but safe.
- Tabletop Wargame — The canonical seated exercise: players take turns moving a plan and an adjudicated opponent across a shared map or board, logging each move and countermove, then harvest the revisions.
- Decision Commitment and Closure: Close deliberation responsibly by naming the choice, authority, evidence threshold, reversibility, forgone alternatives, execution handoff, and conditions for reopening.▸ Mechanisms (10)
- Decision Brief
- Decision Clock — Makes the closure deadline, elapsed deliberation time, delay cost, and pending prerequisites visible while the decision is still open.
- Decision Record Log — Preserves why a decision was made — its rationale, assumptions, recorded dissent, and the strongest rejected alternatives — so later reviewers can reconstruct and calibrate.
- Execution Handoff Checklist — Confirms a closed decision reaches an accountable executor with resources, a start condition, first actions, dependencies, and communication in place.
- Go/No-Go Commitment Gate — Tests closure readiness, authority, reversibility, and execution capacity at a defined decision event and issues a single binding go or no-go.
- Option Comparison Matrix — Arrays the live options against declared criteria to compress evidence into a side-by-side comparison, without implying the weights are objective facts.
- Precommitment Challenge Session — Gives a designated challenger or affected party a bounded, licensed opportunity to attack the leading option's assumptions and resurface alternatives before closure.
- Reopen Trigger Monitor — Tracks the assumptions, thresholds, safety boundaries, and external changes that were pre-declared as grounds to reopen a closed decision.
- Reversibility and Exit Check — Classifies reversal costs, locates points of no return, and confirms a rollback path and the emergency authority that can invoke it before commitment.
- Signed Commitment Authorization — Provides explicit, traceable evidence that the authorized actor or body actually closed the decision and bound the system to one option.
- Defensible Boundary Retreat: Withdraw deliberately from an increasingly indefensible position to a safer boundary before rising hold costs, forced displacement, or irreversible lock-in remove the option to move well.▸ Mechanisms (8)
- Asset Decommissioning and Salvage Runbook — Retires, salvages, or safely quarantines what is left behind and books the surviving obligations, so the abandoned position stops silently consuming resources or leaking liability.
- Hold-vs-Retreat Scenario Stress Test — Projects the hold-cost curve forward under several plausible futures and compares the net value of holding against retreating, so the case to withdraw rests on staying losing across a range of scenarios rather than on a single gloomy forecast.
- Managed Retreat Trigger Review — Sets evidence-based retreat triggers in advance and reviews them on a standing cadence against the rising hold-cost curve and the reversibility horizon, so withdrawal is decided by proof rather than nerve.
- New Boundary Stabilization Review — Verifies after the move that the new boundary actually holds under real load — capacity, defenses, funding, and governance in place — before the retreat is declared complete.
- Old-Position Sunset Clause — Puts a fixed expiry on the commitment to hold a position so it must be actively renewed to continue, flipping the default from indefinite holding to scheduled retreat unless the case to stay is remade on the record.
- Phased Relocation Plan — Sequences the withdrawal as a staged, partly reversible ladder of moves rather than a single leap, so functions keep running while the old position is relinquished piece by piece.
- Receiving Boundary Readiness Assessment — Tests whether the receiving boundary is genuinely more defensible and can actually absorb what is being moved to it, before anyone commits to leaving the old position.
- Retreat Compensation and Continuity Package — Bundles the compensation, bridging services, and participation guarantees owed to the people a retreat displaces, so withdrawal is a governed transfer of support rather than an abandonment.
- Enforceable Obligation Architecture: Make commitment reliable by bundling parties, obligations, breach tests, remedies, and an accepted enforcement regime before performance begins.▸ Mechanisms (9)
- Arbitration or Forum-Selection Clause — Names in advance which forum and rule-set will hear any dispute — an arbitral panel or a chosen court — so disagreements route to an agreed, enforceable venue instead of a jurisdictional fight.
- Automated Execution or Smart Contract — Encodes the agreement as self-executing code that reads a condition and fires the consequence automatically — releasing payment or applying a penalty the moment its triggers are met, with no human in the loop.
- Contract Management Register — A living inventory of every active agreement — parties, signed copies, renewal and exit dates — so obligations and deadlines never fall through the cracks across a portfolio.
- Cure Notice and Period — Formally notifies a party of a specific breach and grants a defined window to fix it before any remedy applies, converting a default into a last chance rather than an instant termination.
- Escrow or Holdback — Places the deal's value with a neutral custodian who releases it only on performance, so neither side can grab it early or withhold it at will.
- Performance Bond or Deposit — Makes a promise of restraint credible by putting the promiser's own value at stake — forfeited on breach — so credibility no longer has to be bought by raising shared catastrophe risk.
- Service-Level Agreement — Pins a delegated service to measurable targets — response times, uptime, quality — with remedies the provider owes when the targets are missed.
- Standard Contract Template — A pre-drafted, reusable master agreement whose vetted boilerplate — duties, liability, indemnity, audit rights — is filled in per deal, so every contract starts from a known, defensible baseline.
- Statement of Work — Specifies the concrete deliverables, scope boundaries, and milestone schedule for one engagement, pinning exactly what will be delivered, by when, and what counts as acceptance.
- Funnel Attrition Localization: Represent an ordered process as denominator-preserving stages, measure where the population is lost, and prioritize the stage whose repair most improves final yield.▸ Mechanisms (11)
- Cohort Transition Table — Follows fixed cohorts stage by stage over a stable window, keeping each cohort's own starting count as the denominator so drop-off is never blurred by mixing arrivals from different periods.
- Conversion Funnel Dashboard — A single standing panel showing entry counts, per-stage conversion and drop-off, and final yield against target across the ordered funnel — the shared at-a-glance read of where the funnel stands.
- Denominator Reconciliation Checklist — A pre-analysis gate that verifies each stage's counts agree across systems, definitions, time windows, filters, and de-duplication rules before anyone trusts the funnel.
- Event Instrumentation Specification — The upfront design document that fixes the funnel's stages and defines the exact events, identifiers, and transition rules to log — so the data is interpretable before it is collected, not after.
- Event Trace Process Mining — Reconstructs the actual paths people took from raw event logs, exposing the loops, skips, back-steps, and side-routes that a clean linear funnel silently assumes away.
- Funnel Experiment Backlog — Turns prioritized loss hypotheses into a running queue of tests, redesigns, and repairs — each sized by the yield it could recover and closed only when remeasurement confirms the gain.
- Loss Pareto Review — Ranks the funnel's stages by how much final yield each one actually costs and how tractable its fix is, so effort goes to the stage that returns the most recoverable yield per unit of work — not merely the biggest visible drop.
- Segment Funnel Comparison — Re-runs the same funnel separately within meaningful slices — channel, device, region, cohort, access group — to reveal whether a whole-funnel drop is really one segment collapsing at one stage.
- Stage Conversion Anomaly Alert — Watches each stage's live conversion against a validated baseline and fires the moment a rate breaches its control limit, catching a drop-off shift as it happens instead of at the next review.
- Stage Drop-Off Waterfall — Renders the population cascading from the initial cohort down to final yield one stage at a time, so the size and exact location of every loss is read off a single denominator-preserving chart.
- Survivorship Bias Audit — Tests whether a funnel that looks healthy among the people it measures is quietly ignoring those excluded, abandoned, refused, or dropped before they were ever counted.
- Refinement Timing Guardrail: Delay costly local refinement until the global structure, real bottlenecks, and reversibility conditions are known enough to spend optimization effort well.▸ Mechanisms (9)
- Architecture Skeleton or Walking Skeleton — Stands up a thin end-to-end version of the whole system first — every layer wired, nothing polished — so its real integration structure is visible before any local part is refined.
- Decision Record with Deferred Refinement — Writes down, for a single decision, which refinement is being deliberately postponed, what lock-in that avoids, and under what exception it could still proceed early.
- Local–Global Metric Trace — Instruments a local metric and the whole-system outcome it is supposed to serve on the same chart, so a polished local number can't be mistaken for real value.
- Optimization Backlog with Trigger Conditions — Keeps deferred optimizations in a visible list, each tagged with the measurable condition that should fire it — so good ideas are neither forgotten nor done too early.
- Pre-Optimization Review Ritual — A recurring, short team meeting where any proposed optimization must be argued aloud before work starts — turning 'should we polish this now?' into a collective, evidence-checked decision.
- Refinement Readiness Checklist — A fixed list of pass/fail criteria every proposed refinement must satisfy before it is allowed to proceed — the gate rendered as an explicit, repeatable checklist.
- Representative Workload Profiling — Runs the system under a load that mirrors real usage and measures where time and resources actually go — so refinement aims at the true bottleneck, not the suspected one.
- Reversibility Tag or Feature Flag — Wraps an early refinement behind a switch that can turn it off or back it out cleanly, so the change stays removable while the surrounding system is still uncertain.
- Timeboxed Optimization Spike — Spends a fixed, small budget of time on an optimization purely to learn whether it would pay — with a hard stop and no commitment to keep the code.
Also a related prime in 18 archetypes
- Accountable Gatekeeping Design: Design choke-point selection so passage decisions use explicit criteria, bounded discretion, traceable reasons, review paths, and distribution audits rather than opaque gatekeeper preference.
- Attrition Contest Exit Design: Turn a costly “who can endure longer” contest into a bounded decision with visible burn rates, exit criteria, settlement channels, and face-saving off-ramps.
- Cohort-Structured Replenishment Stabilization: Do not govern a replenished stock from its current total alone; track the cohorts that will become tomorrow’s stock and buffer the echoes of unlucky entry windows.
- Constraint-Guided Backtracking: Solve a constrained, path-dependent problem by extending a partial solution, testing it early, and undoing the latest failed commitment while preserving still-valid prior work.
- Critical Juncture Path Stewardship: Steer high-leverage branching moments by making divergent paths, small levers, lock-in mechanisms, and reversibility limits explicit before commitment hardens.
- Decision-Tempo Decoupling: Prevent a slower actor from being governed by a faster actor’s cadence by classifying response obligations, buffering tempo shocks, preauthorizing bounded action, and deliberately choosing when to ignore, delay, automate, delegate, or shift the contest.
- Event-Script Structuring: Encode a familiar situation as an expected role-and-event sequence so people or systems can recognize the situation, know what normally comes next, and notice meaningful deviations.
- Eventual-Occurrence Containment Design: When a harmful outcome retains nonzero probability across many opportunities, design as though it will occur within the relevant horizon: keep reducing risk, but also cap impact, isolate propagation, detect quickly, and prove recovery.
- Fast/Slow Path Routing: Route routine cases through a cheap, safe fast path while sending exceptional, ambiguous, risky, or high-value cases to a deliberately resourced slow path.
- Intermediate-State Throughput Control: Treat a named transient state as a controllable intervention surface: regulate how fast it forms, how long it persists, how its quality changes, and how reliably it converts into the desired next state.
References¶
[1] Cooper, Robert G. "Stage-Gate Systems: A New Tool for Managing New Products." Business Horizons, vol. 33, no. 3 (1990): 44–54. Introduces the Stage-Gate model: staged new-product development separated by go/no-go evidence gates. registry ↩
[2] U.S. Food and Drug Administration. "Step 3: Clinical Research." The Drug Development Process. FDA, 2018. Defines Phase 0–IV clinical trial phases with evidence packages required between phases and heavy attrition before approval. registry ↩
[3] U.S. Department of Defense. Operation of the Adaptive Acquisition Framework, DoD Instruction 5000.02. Washington, DC: DoD, 2020. Establishes milestone decision points (Milestones A, B, C) gated by review boards with evidence packages. registry ↩
[4] Humble, Jez, and David Farley. Continuous Delivery: Reliable Software Releases through Build, Test, and Deployment Automation. Boston: Addison-Wesley, 2010. Codifies the staged software deployment pipeline (build, test, release stages) with explicit exit criteria and escalating exposure from internal testing through release to production. registry ↩
[5] Miles, Mike E., Gayle Berens, Mark J. Eppli, and Marc A. Weiss. Real Estate Development: Principles and Process, 4th ed. Washington, DC: Urban Land Institute, 2007. Lays out the staged development pipeline—feasibility, entitlement, design, construction, lease-up—each escalating capital against evidence. registry ↩
[6] Dixit, Avinash K., and Robert S. Pindyck. Investment under Uncertainty. Princeton: Princeton University Press, 1994. Real-options valuation, porting from finance into staged R&D budgeting where staged commitment is a sequence of options. registry ↩
[7] DiMasi, Joseph A., Henry G. Grabowski, and Ronald W. Hansen. "Innovation in the Pharmaceutical Industry: New Estimates of R&D Costs." Journal of Health Economics, vol. 47 (2016): 20–33. Documents the cost-staging and roughly one-in-ten Phase-I-to-approval attrition of oncology and other drug development. registry ↩
[8] Wald, Abraham. Sequential Analysis. New York: John Wiley & Sons, 1947. Introduces the sequential probability ratio test: continue sampling between two boundaries, stop (advance or terminate) outside them—the formal gate/kill decision rule. registry ↩
[9] Gompers, Paul A. "Optimal Investment, Monitoring, and the Staging of Venture Capital." Journal of Finance, vol. 50, no. 5 (1995): 1461–1489. Establishes staged venture financing as evidence-gated escalating commitment with high inter-round attrition. registry ↩a ↩b