Staged Expansion Review¶
Staged expansion review — instantiates Defensible Foothold Expansion
A recurring deliberative forum that weighs the evidence for each expansion stage, names who is accountable for it, and checks whether real support capacity exists before authorizing the move.
A gate can say no on a rule, but someone still has to exercise judgment about messy evidence, own the consequences, and confirm the organization can actually staff the next move. Staged Expansion Review is that recurring forum. Stage by stage, it convenes the people who can weigh base health, transfer evidence, and adjacency quality against each other, decides whether to advance, deepen, pause, or pivot, and — its two defining outputs — assigns a named owner accountable for the stage and confirms the support capacity to run it exists before the move is authorized. Where the Scale Gate is a fixed rule and the Base Health Dashboard is a running instrument, this is the deliberation: the human judgment that reads the whole picture and puts a name and a capacity check behind the go.
Example¶
A community-health nonprofit runs three neighbourhood clinics and plans to expand to a fourth, then a fifth. Rather than approve the whole rollout at once, its board holds a Staged Expansion Review before each new site. The review convenes clinic directors, finance, and operations to look across the evidence: are the existing clinics still hitting their patient-retention and wait-time commitments, or is quality slipping under load? Did the transfer of the care model to clinic three actually work, or did it need constant rescue? Is the target neighbourhood a genuine adjacency? Then it asks the two questions the review exists to answer: who owns clinic four — a named director with the authority and bandwidth to stand it up — and is there real capacity to support it: trained staff to hire from, a supervising clinician with room to mentor, IT and billing that can absorb another site.
At the review before clinic five, the existing clinics are healthy and the model transfers cleanly, but the operations lead is already stretched across four sites and no deputy exists. The review does not reject clinic five; it pauses it and makes building support capacity the explicit precondition, assigning that task to a named owner with a date. The move waits not on a rule but on the forum's judgment that the base could not yet carry it.
How it works¶
What distinguishes the review is that it is a recurring, evidence-weighing forum that assigns ownership and capacity, not a fixed rule and not a dashboard:
- Convene per stage. Before each expansion move, the people who can see base health, transfer evidence, resource availability, and adjacency quality meet to weigh them together rather than in isolation.
- Decide among more than go/no-go. The review's verdict space includes deepen, pause, pivot, or abandon — a judgment about the best next action, not a binary pass.
- Assign an accountable owner and map the support capacity. Every authorized stage leaves with a named person answerable for it and an explicit check that the staffing, systems, and support to run it actually exist.
The review supplies judgment and ownership; the fixed pass/fail conditions it consults, and the continuous data it reads, are held by other mechanisms.
Tuning parameters¶
- Review cadence — how often the forum meets, or whether it is triggered per stage. Frequent reviews catch drift early but tax attention; per-stage-only reviews are lean but can miss a base eroding between moves.
- Authority of the forum — whether the review recommends or decides. A deciding review moves fast and owns outcomes; an advisory one preserves executive control but can be overridden into irrelevance.
- Evidence bar — how much proof a stage must show before authorization. A high bar protects the base; too high and the review becomes a bottleneck that outpaces the opportunity.
- Owner-accountability strength — how much real authority and consequence attach to the named stage owner. Strong accountability drives follow-through; nominal ownership makes the assignment ceremonial.
When it helps, and when it misleads¶
Its strength is that it supplies what a rule cannot: judgment over ambiguous evidence, a single accountable owner per stage, and an honest capacity check that stops a foothold from authorizing growth it has no one to run. By re-deciding each stage on current evidence, it also keeps expansion from becoming an open-ended march that no one is empowered to halt.
Its failure modes cluster around commitment and capture. The sharpest is escalation of commitment — approving the next stage to justify the resources already sunk into the last, so the review rubber-stamps momentum rather than testing it.[n1] A review can also become theatre, ratifying decisions already made elsewhere; diffuse ownership can let a stage pass with no one truly answerable; and an optimistic capacity check can wave through a move the base cannot actually staff. The discipline that keeps it honest is to judge each stage on forward evidence rather than sunk cost, to insist every authorization carry a named owner and a concrete capacity map, and to keep genuine pause, pivot, and abandon on the table — not just go.
How it implements the components¶
Staged Expansion Review fills the deliberation-and-ownership subset of the archetype's machinery — what a recurring judgment forum produces:
accountable_scale_owner— each authorized stage leaves the review with a single named person answerable for standing it up and for protecting the base while doing so.support_capacity_map— the review's capacity check assembles an explicit picture of the staffing, systems, and support available to run the next stage before it is approved.
It does not hold the fixed pass/fail conditions it applies — the readiness and base-protection thresholds (scale_readiness_criteria, base_protection_rule) live in the Scale Gate — and it does not continuously monitor the base (self_sustainability_test), which is the Base Health Dashboard's role. The review reads those instruments and rules; its own contribution is judgment, ownership, and the capacity check.
Related¶
- Instantiates: Defensible Foothold Expansion — the review is the per-stage forum that authorizes expansion while protecting the base.
- Consumes: Scale Gate — the review invokes the gate's fixed criteria; Base Health Dashboard and Adjacency Mapping Workshop supply the base-health and adjacency evidence it weighs.
- Sibling mechanisms: Scale Gate · Base Health Dashboard · Land-and-Expand Playbook · Adjacency Mapping Workshop · Reference Case Program · Focused Vertical Launch · Anchor Customer or Anchor Tenant Strategy · Beachhead Selection Scorecard · Customer Segmentation Model · Market and Competitor Scan
Editorial Notes¶
Form Classification¶
Form family: Assessment, Review & Assurance
Rationale: Staged Expansion Review operates as a bounded evaluation of existing evidence or work that produces a finding or disposition because it a recurring deliberative forum that weighs the evidence for each expansion stage, names who is accountable for it, and checks whether real support capacity exists before authorizing the move.
Independent corroboration: The frozen evidence defines Staged Expansion Review as 'A recurring deliberative forum that weighs the evidence for each expansion stage, names who is accountable for it, and checks whether real support capacity exists before authorizing the move', so its operative form is Assessment, Review & Assurance.
Nearest alternative: Organization, Role & Governance — Staged Expansion Review includes features of an enduring role, team, authority, channel, or governance body that allocates responsibility, but its defining operation is a bounded evaluation of existing evidence or work that produces a finding or disposition.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Convergent development
Present-day reach: Universal
Rationale: A recurring forum authorizing growth from evidence and support capacity is expansion governance.
Related originating lineages:
- Law & Governance — Authority and accountability legitimize approval.
- Operations Research — Capacity evidence bounds feasible expansion.
- Systems Thinking & Cybernetics — Systems thinking, feedback control, and cybernetics supplies a parallel or contributing lineage for the mechanism's defining operation: a recurring deliberative forum that weighs the evidence for each expansion stage, names who is accountable for it, and checks whether real support capacity exists before authorizing….
Review resolution: The blind reviewers agree that organizational_management is the primary origin and differ only on alternate origin 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; medium confidence.
Notes¶
The division of labour with its two closest siblings is deliberate. The Base Health Dashboard shows the base's condition continuously; the Scale Gate rules on fixed conditions; the Staged Expansion Review judges — reading both, applying discretion no rule can encode, and attaching a name and a capacity check to every stage it lets through. Collapsing the three into one loses either the impartial rule, the live data, or the accountable judgment.
[n1] Escalation of commitment — the documented tendency to keep investing in a failing course of action to justify resources already spent. It is the specific bias a stage review must resist when a stage's real case is weak but abandoning it would mean writing off prior investment. Named here as the hazard the review guards against, not as a cited result. ↩