Phase-Gate Resolution Review¶
Stage-gate review — instantiates Sequential Local Superiority
A go/no-go gate that refuses to advance the sequence until the current segment is stably resolved and the next segment is still the right next segment.
The most reliable way to lose a sequential campaign is to move on from a segment that only looks finished. Phase-Gate Resolution Review is the checkpoint that stands between one segment and the next and refuses passage on two questions at once: is this segment actually stable? and is the planned next segment still the right one, given what we now know? It is a mid-sequence decision ritual — a scheduled go / hold / re-order moment — whose distinctive move is coupling a stabilization test to a re-validation of the order. It does not fold the resolved segment back into the wider system; it only decides whether the sequence may take its next step. Passing the gate is permission to advance, nothing more.
Example¶
A state education agency is turning around a set of chronically underperforming school districts, cluster by cluster. The first cluster — four districts sharing a regional service center — has hit its visible targets: new leadership installed, reading scores up a term. Before crews rotate to the next cluster, the phase-gate review convenes. The stabilization test asks the awkward questions: are the gains holding for two consecutive reporting cycles, or is this a first-quarter bump? Is there a named local owner who will sustain it without the turnaround team? Are the dependencies — funding, staffing pipeline — controlled rather than propped up by temporary attention?[n1] The order-revalidation half then asks whether cluster two is still the right next move, given that the turnaround revealed the real bottleneck is a shared HR system none of the clusters control. The gate holds the advance, redirects the next step to the HR dependency, and only then releases the team — preventing exactly the failure where a "won" cluster regenerates the moment attention leaves.
How it works¶
- Run the stabilization test first. Advance is blocked unless the current segment meets an explicit, pre-agreed condition for "resolved and staying resolved" — durable metrics, a named owner, controlled dependencies — not a one-time win.
- Re-validate the order, don't assume it. The gate re-asks whether the next-planned segment is still the best next move given what this resolution just taught, and re-orders if not.
- Force an explicit verdict. The output is go, hold, or re-sequence — a decision on the record, with the missing conditions named when it is a hold.
- Keep it scheduled and independent. The review is a standing gate the sequence cannot skip, chaired by someone other than the team eager to move.
Tuning parameters¶
- Stabilization bar height — how much durable evidence "resolved" requires. A high bar prevents regeneration but slows the whole sequence; a low bar keeps momentum but lets fragile wins through.
- Re-order openness — how readily the gate rewrites the remaining order. High openness keeps the plan honest but can churn; low openness is decisive but risks marching to a stale sequence.
- Gate cadence — one review per segment versus multiple interim checks. More gates catch drift earlier at the cost of overhead.
- Verdict strictness — whether a "hold" fully stops advance or permits conditional progress while a gap is closed.
When it helps, and when it misleads¶
Its strength is that it institutionalizes patience at the exact point where teams are most impatient — the moment a visible win tempts them to declare victory and rotate. By testing durability and re-checking the order in one gate, it defends against both premature movement and marching on autopilot toward a next segment that stopped being right.
Its failure mode is the gate that becomes theater: a checklist rubber-stamped because everyone already wants to move, its stabilization bar quietly lowered to whatever the current segment happens to have achieved. A gate that always says "go" is worse than none, because it lends the appearance of rigor to a decision made on momentum. The classic misuse is letting the team being reviewed set its own passing conditions. The guarding discipline is a pre-committed stabilization bar owned by someone other than the advancing team, and a standing willingness to record "hold" — a gate that never holds is not a gate.
How it implements the components¶
stabilized_resolution_condition— the gate's first test is the stabilization condition, made explicit and enforced as the price of advance.decisive_sequence_order— the order-revalidation half re-confirms or rewrites the engagement order at each step, keeping the sequence live rather than fixed at planning time.
It does not implement post_sequence_reintegration_plan — folding a resolved segment back into the whole system belongs to Reintegration Checkpoint, its nearest twin; the phase gate authorizes *moving on within the sequence, not reunifying the segment with the wider system at the end. Nor does it implement segment_learning_capture, which After-Action Sequence Update fills — the gate uses lessons to decide go/hold, but harvesting and recording them is the after-action's job.*
Related¶
- Instantiates: Sequential Local Superiority — supplies the advance-control gate that keeps the sequence from moving on unstable ground.
- Sibling mechanisms: Reintegration Checkpoint · After-Action Sequence Update · Segment Priority Matrix · Recombination Risk Register
- Compare: Phase-Gate Review — the separating dimension is what the gate tests: the resolution review re-orders the remaining sequence and tests segment stabilization (is the next segment still next?), whereas a phase-gate review is a threshold check against fixed readiness criteria for a fixed next phase.
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Phase-Gate Resolution Review operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it a go/no-go gate that refuses to advance the sequence until the current segment is stably resolved and the next segment is still the right next segment.
Independent corroboration: The frozen evidence defines Phase-Gate Resolution Review as 'A go/no-go gate that refuses to advance the sequence until the current segment is stably resolved and the next segment is still the right next segment', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Assessment, Review & Assurance — Phase-Gate Resolution 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: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Phase-Gate Resolution Review is rooted in innovation and entrepreneurship: Cooper's Stage-Gate product-development method supplies the go-kill decision structure between sequential segments.
Related originating lineages:
- Engineering & Design — Systems engineering supplied readiness evidence and sequence-dependent technical exit criteria.
- Organizational & Management Science — Organizational and management science materially shaped Phase-Gate Resolution Review through coordination, organizational learning, performance, and change practice. Go/no-go phase gates are established program and product-development management practices.
Review resolution: Light authoritative-source research resolves the primary-origin disagreement in favor of innovation and new-product-development practice. Robert G. Cooper: The Stage-Gate Model directly documents the defining practice or theory described in the selected origin rationale. Other listed domains are retained only where the blind reviews identify material co-development or translation; broader adoption remains separate as domain_reach=multi_domain.
Attribution caveat: The boundary with organizational and management practice is real because that field materially developed or translated the practice, but the cited provenance places the defining form in innovation and new-product-development practice.
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¶
[n1] The scheduled go/kill decision point between phases of an effort is the Stage-Gate method formalized by Robert G. Cooper for product development — a real, named process. This mechanism adapts its logic to a resolution sequence: the gate's kill/continue question becomes "is this segment stable, and is the next one still next?" ↩