Statistical Fluctuations and Variance
also Variance · Random variation
The unavoidable variation in real processes, where a step averaging 30 units per hour does 20 in one hour and 50 in another, so nothing runs exactly to plan.
Statistical fluctuations are the inherent variation in any real process: a workstation, programmer, or sales channel that produces some amount on average will run above and below that average from hour to hour and day to day. Goldratt’s The Goal dramatizes this with the matchstick-and-dice game. CF treats fluctuations as a stand-in for a more general fact — errors happen, things never go perfectly to plan — and uses them as a foundation for its anti-perfectionist stance on design and decision making.
The decisive point is that variance combined with dependencies (one step feeding the next) is what makes a balanced plant fail. When steps depend on each other, a slow hour upstream starves the next step, while a fast hour upstream just piles up unprocessed work — positive variance rarely makes up for past negative variance, so output drifts below the nominal average. The remedies are a buffer in front of the constraint and excess capacity at non-constraints to refill that buffer after bad luck. Fluctuations are best handled at the most aggregated level, since independent ups and downs partly cancel; this is why drum-buffer-rope buffers the system, not every station.
CF generalizes this to thinking. Because variance is unavoidable, robustness beats fragile optimization: build good-enough margins around the few factors that matter and let everything else carry slack, rather than tuning every factor to a knife-edge. “Improving” a factor that already has enough excess capacity wastes effort; CF holds that changes in excess capacity usually aren’t important, precisely because a resilient system should stay insensitive to small fluctuations.