Pilot Purgatory¶

Relocate the diagnosis of an initiative that keeps running successful pilots without ever scaling from 'weak evidence' to 'a missing transition mechanism' — the loop is sustained by each pilot's local success, and the fault sits one level up in the decision infrastructure.

Core Idea¶

Pilot purgatory is the organizational pathology in which an initiative repeatedly runs pilots or proofs-of-concept of the same intervention without an institutional path converting a successful pilot into adoption at scale. Each iteration produces favourable findings that do not propagate into a budget commitment, an operating-model change, or a procurement decision. The structural commitment is the absence of a transition mechanism linking demonstration to institutionalization: the pilot subsystem is operationally complete, but the escalation handoff to budget ownership or operational integration does not exist. The loop is sustained by each pilot's local success.

Scope of Application¶

Pilot purgatory lives across the sectors of organizational innovation-adoption where the system running pilots is structurally separated from the one that must absorb the scaled capability — four sectors of one substrate.

Manufacturing digitization / Industry 4.0 — where the term was coined; pilots without enterprise rollout.
Government technology and digital services — lab pilots that never reach procurement or appropriations.
Health-tech adoption — clinical pilots that never reach the EHR build or a reimbursement code.
Education reform — school pilots that never propagate district- or state-wide.
Research-into-practice translation — favourably evaluated demonstrations with a broken adoption pathway.

Clarity¶

Naming pilot purgatory corrects a misdiagnosis the pattern almost guarantees: the failure looks like insufficient evidence, so the reflex is another, better pilot. The label moves the question one level up — what is the path from a successful pilot to institutional adoption, and does it exist? That reframe is load-bearing because the loop is sustained by local success. The two diagnoses prescribe opposite work, and the label sharpens boundaries against sunk-cost, the valley of death, and analysis paralysis, each of which routes elsewhere.

Manages Complexity¶

A funder staring at a stalled initiative confronts a thicket of candidate explanations, re-litigated each cycle, with a built-in attractor toward "run another, better pilot." Pilot purgatory collapses the thicket to a single structural question one level above the pilot: does a transition mechanism exist? The analyst stops grading pilots and checks for the handoff, reading fate off whether the path exists. That installs a clean two-way branch — evidence problem versus transition-mechanism problem — that the misdiagnosis flattens.

Abstract Reasoning¶

The concept licenses a diagnostic reading a string of favourable-but-unscaled pilots as a missing transition mechanism, its tell being the favourability of the results. Interventionist reasoning predicts the reflexive fix fails and targets the specific absent link — stage-gate, adoption owner with budget, enterprise procurement. Boundary-drawing separates it from sunk-cost, valley of death, analysis paralysis, and pivot thrashing, each routing to a different fix. An order-of-events prediction shows the loop will not self-terminate.

Knowledge Transfer¶

Within organizational change and innovation-adoption practice the frame transfers as mechanism: the relocate-the-fault diagnosis and its toolkit are sector-indifferent, carrying intact across manufacturing, government, health-tech, education, and research translation — four sectors of one substrate. Off-substrate uses (a stalled research project, a perpetual prototype) are analogy. What genuinely travels is a conjunction of parents — local_optimum / goal_displacement (local success at the wrong level), interface_mismatch / seam (the missing transition), and path_dependence / equilibrium (cycle stability). The pilot-and-procurement cargo stays home.

Relationships to Other Abstractions¶

Current abstraction Pilot Purgatory Domain-specific

Parents (1) — more general patterns this builds on

Pilot Purgatory is a kind of Interface Mismatch Prime

Pilot Purgatory is the organizational interface mismatch in which a demonstration system's outputs do not satisfy the absorber system's adoption contract.

Hierarchy path (1) — routes to 1 parentless root

Pilot Purgatory → Interface Mismatch → Interface → Boundary

Neighborhood in Abstraction Space¶

Pilot Purgatory sits in a sparse region of the domain-specific corpus (93^rd percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Incident Command & Operational Tempo (10 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12