Definition

The mechanical manifestation of The Operator’s Bottleneck — the rate at which the operator-as-bottleneck processes the work. The bottleneck is the noun, the constraint that exists; throughput is what the bottleneck does, the constraint’s output rate. Causality runs parent to child: working on the bottleneck changes throughput; working on throughput cannot change the bottleneck. Superseded an earlier, inverted version of this entry that positioned throughput as the parent axiom.

Explanation

The correction embedded in this entry’s own history is worth preserving because it’s instructive about a common reasoning trap. It’s tempting to treat throughput as the fundamental problem, since throughput is what’s visible and measurable — how much the operator can actually process in a given period. But throughput is downstream of something more fundamental: the operator’s own ceiling as the bottleneck constraining the whole system.

This is why interventions aimed only at throughput — working faster, cramming more into the same hours, optimizing personal efficiency — hit a hard limit that no amount of further optimization can push past. The ceiling itself, [The Operator’s Bottleneck], is the actual constraint. Real growth requires addressing the bottleneck directly, typically by delegating pieces of the constraint away from the operator entirely, rather than trying to squeeze more throughput out of an operator who remains the fixed ceiling on the whole operation.