Here is something that happens every time a warehouse gets a faster scanner or a new WMS: pick rates go up, labor hours go down, and within six months, the new rate is the standard. Nobody planned for the time savings to disappear. They just did. The system absorbed the gain and restructured around it. What was surplus became floor.
That is not a complaint about operations management. It is a description of how systems work.
When a process gets faster or cheaper, the organization adjusts its expectations, its staffing models, and its throughput targets to absorb the new capacity. The gain does not pool at the top as slack. It flows through the system and raises the baseline. Economists name part of this the Jevons paradox — the observation that efficiency gains in resource use tend to increase total consumption rather than reduce it, because the system recalibrates demand upward to match the new capacity. Fuel-efficient engines did not reduce fuel consumption. They made driving cheaper, so people drove more.
What Richard Wrangham argues in Catching Fire: How Cooking Made Us Human is that the mechanism is older than industrial economics, and more structural than most versions of the story acknowledge. Cooking increased the caloric yield of food by a measurable amount. When protein is cooked, the digestive system absorbs roughly 78% more of it than it would from the raw equivalent. Cooked eggs yield 91% of available energy to digestion; raw eggs yield around 51%. That gap is not small. And the human body did not bank the difference as reserve energy. It spent it. The gut shrank. The brain grew. The morphology of the species changed to reflect the new energy budget. The gain became structure.
The parallel in logistics is not metaphorical. It is a description of the same mechanism running through a different system at a different speed.
When a distribution center moves from paper pick lists to RF scanning, the first visible thing is accuracy: error rates drop, pick times improve. The second thing is invisible until it is already done. The operation recalibrates. The labor model adjusts. The headcount-per-unit calculation changes. The new throughput rate becomes the budgeted rate. Within a cycle or two, the old rate is no longer even a reference point. The system has restructured around the gain, and the gain has disappeared as surplus.
This is not a failure. It is the system working correctly. Systems allocate efficiency gains toward the next constraint. That is the mechanism. The problem is that the restructuring often happens faster than the dependency becomes legible. By the time anyone asks what happens if the scanner network goes down, the workflow that existed before the scanner no longer exists. The workaround has been trained out. The documentation is gone. The people who knew the old process have turned over. The operation cannot revert to what it was before the improvement, because the improvement has been spent on a new version of the operation that requires it.
Wrangham's account of cooking runs the same way. The caloric gain from cooked food did not make early humans better-fed raw-food eaters. It made them something else: a species whose gut had downsized to redirect energy to the brain, and whose brain then required cooked food to sustain itself. The dependency was not a byproduct of the efficiency gain. It was the efficiency gain, restructured into anatomy. The human brain now uses 25% of caloric intake. The body sustains that allocation by running a smaller digestive system. Those two facts are not coincidental. They are co-dependent.
I want to name the problem this creates, because it is not a problem of the efficiency gain being bad.
The gain was real. The extra calories were real. The brain expansion was real. The cultural consequences of cooking — the social meal, the division of labor around the evening fire, what Wrangham argues may be the beginning of culture itself — were real and significant. None of that is in dispute.
The problem is irreversibility. Once the body restructured around cooking, the option to return to raw food as a full-time diet was gone. Not culturally gone. Anatomically gone. There is no diet of raw food that sustains modern human brain function at the level the brain now requires. The gut that could have processed it no longer exists. The efficiency gain was spent on a body plan that required the gain to continue. The system that benefited from cooking became dependent on cooking.
In operational systems, this tends to show up as fragility that is invisible until it fails. The warehouse optimized around RF scanning does not know it has lost the ability to function without RF scanning until the network goes down at peak. The supply chain built for just-in-time delivery does not know how dependent it is on transit time stability until a port closes. The efficiency is real. The dependency that follows the efficiency is also real. The dependency just does not appear in the efficiency analysis, because the efficiency analysis is measuring the gain, not the restructuring.
Wrangham argues that cooking probably began because the caloric gain was immediate and visible. That seems right. The restructuring that followed was not planned. It was not even visible to the organisms undergoing it. Selection pressure does not ask whether the dependency is acceptable before it runs toward what works.
What changes once you see this clearly: efficiency gains are not additions to a static system. They are inputs that a system responds to by changing shape. The shape that results is calibrated to the gain. The gap between what the system was and what it became is a structural dependency, not a preference.
This changes how you evaluate an operational improvement. The question is not only how much this helps. It is what the system looks like after it restructures around the help. Those are different questions. The first is about the gain. The second is about what you give up the option to do once the gain has been absorbed.
A gain that restructures a system toward irreversible dependency is not automatically a bad gain. Sometimes the restructuring is worth it. The brain was worth it. But the dependency needs to be legible before it is locked in, not after. The time to ask what happens without the scanner is before the operation has been rebuilt around the scanner. By the time the failure reveals the dependency, the system has already restructured around it. The question becomes not whether to accept the dependency, but how to manage it — which is a harder problem with fewer options.
The kitchen is not a convenience. It is infrastructure. It has been infrastructure for long enough that the anatomy built around it is now the baseline. Calling it optional is not wrong in any local sense. In any systems sense, it is not coherent.
The gain and the dependency arrive together. The gain is visible immediately. The dependency takes longer. That gap is not a design flaw. It is the timeline.