Capacity analysis reliably examines machines, labor, and materials. It reliably omits the variable that governs all three: the interval at which decisions are permitted to change. Gartner’s sense-and-respond planning model addresses this directly, treating the latency between sensing a demand signal and responding in execution as the primary constraint on planning performance, a reframing that moves the question from planning accuracy to planning cadence. In the throughput walk, planning and scheduling losses account for 15 of the 36 points lost between plan and ship, capacity forfeited to decision cadence rather than to any physical constraint.
Latency compounds across handoffs
Each system in the planning estate runs its own cycle. Demand refreshes weekly. MRP regenerates nightly. Purchase releases batch daily. Production scheduling locks against a frozen horizon. Each interval is individually defensible; composed, they mean the plant is executing against a demand signal that is structurally several days to several weeks old.
The compounding is the point. A forecast update that lands one hour after the MRP window waits a full cycle. A purchase release that misses the daily batch waits a day, then arrives after the scheduling freeze and waits a further period. No single delay is material, and the aggregate sets the ceiling.
The plant is not slow. It is building last month’s demand, perfectly, on time.
Why adding capacity does not lift it
When the constraint is decision cadence, additional physical capacity is scheduled at the same stale interval. The plant builds more of what was correct at the last refresh. Utilization metrics improve locally while enterprise throughput does not, which is precisely the pattern the throughput walk records between the 84.6% planning-stage yield and the 64.2% realized figure.
The horizontal chain
Demand Planning → Procurement → Production Execution. The time-delta between forecast refresh, purchase release, and production scheduling means the plant is always building last month’s demand, velocity lost not to capacity, but to latency between decisions.
Production → Warehouse → Customer Dock. Finished goods that beat their schedule then queue for waves, slots, and tenders set on their own independent cycles, surrendering at the dock what was won on the floor.
The control point
The correction is not faster batches. It is replacing scheduled synchronization with event-driven propagation, so that a change in demand, supply, or capacity moves through the estate when it occurs rather than when the next window opens. Rolling re-plan cadence keyed to live exception feeds converts a fixed interval into a variable one.
Batch processing was an accommodation to compute cost that has outlived the constraint that justified it, and it is now the most expensive assumption in the planning estate.