Plan-Execute Gap¶

The pathology in which a coarse-grained planning artefact cannot be enacted because the execution layer faces binding fine-grained constraints the planning model never represented — so the fix is constraint propagation and feedback, never a better forecast.

Core Idea¶

The plan-execute gap is the pathology in which a prescriptive planning artefact — a master schedule, S&OP plan, Gantt, or dispatch — cannot be enacted because constraints binding at execution time were abstracted away when the plan was built. The mechanism is a layered information asymmetry: the execution layer holds detailed constraint knowledge the planning layer does not model, yet the plan holds coordination authority. Execution reconciles in-place with no feedback channel, so plan and reality diverge and improvisation hardens from exceptional to structural.

Scope of Application¶

Lives across the operations-management and prescriptive-planning subfields that share the plan/execution layering — a coarse directive handed to an execution layer holding finer binding constraints.

Manufacturing S&OP — a monthly plan un-sequenceable against changeovers and maintenance windows.
Healthcare operations — surgical schedules broken by tray readiness and prior-case overrun.
Construction project planning — a master schedule the field cannot honour and re-sequences on site.
Software delivery — sprint plans broken by incidents, dependency blocks, and integration outages.
Emergency logistics — contingency plans overtaken by post-disaster road, fuel, and personnel realities.

Clarity¶

Naming the gap separates two failure modes identical in outcome but demanding opposite correctives. Plan failure means the plan was wrong about the world — fix the forecast. The plan-execute gap is the other case: a reasonable abstraction the execution layer cannot enact, because constraints binding at execution time were never modelled. It also reframes shop-floor improvisation from indiscipline into a signal — information that needs to flow back into the next plan rather than be absorbed silently.

Manages Complexity¶

The execution layer's binding constraints are an endless facility-specific list. The concept compresses that variety by asserting what matters is not any constraint's identity but its location relative to two layers. The planner then tracks a few quantities — the granularity gap, the replanning cadence, the presence of a feedback channel — and reads the trajectory off them. A missed plan splits first on cause; only the constraint-blindness branch is the gap, and the reflexive fix (tune the forecast) is precisely wrong.

Abstract Reasoning¶

A diagnostic move reads improvisation as evidence of unmodeled constraints and splits a miss into forecasting error versus constraint-blindness by asking which fix would have helped. An interventionist move names the corrective family (propagate constraints up, shorten cadence, reclassify schedule-to-direction) with specific predictions, and a strong negative prediction that tuning the forecast moves nothing. A boundary move marks the compounding regime and where no gap exists. An order-of-events move locates the missing return channel in the loop.

Knowledge Transfer¶

Within operations management the gap transfers as mechanism across its sub-fields, because they share the plan/execution layering — the diagnostic split, corrective family, and toolkit (finite-capacity scheduling, rolling horizons, plan-versus-actual telemetry) carry intact from S&OP to healthcare to construction to software to emergency logistics, and the negative prediction ports with equal force. Beyond operations the honest reading is shared abstract mechanism via a conjunction of parents: abstraction of a prescriptive artefact, local_versus_global_information, and inter-layer feedback failure carry the cross-domain weight, while the planning-artefact arrangement and its calibrated interventions stay home.

Relationships to Other Abstractions¶

Current abstraction Plan-Execute Gap Domain-specific

Parents (2) — more general patterns this builds on

Plan-Execute Gap is a kind of Procedure-Work Mismatch Prime

Plan-execute gap is procedure-work mismatch specialized to a planning directive whose coarse model cannot be enacted under the fine constraints of actual operations.
Plan-Execute Gap presupposes Information Locality Prime

Plan-execute gap presupposes that execution holds criterion-relevant constraint information the planning level lacks.

Hierarchy paths (4) — routes to 4 parentless roots

Plan-Execute Gap → Procedure-Work Mismatch → Formal vs. Informal Structures → Formalization → Representation → Abstraction

Show alternative paths (3)

Neighborhood in Abstraction Space¶

Plan-Execute Gap sits in a moderately populated region (48^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Unclustered & Miscellaneous (309 abstractions)

Nearest neighbors

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