Modern culture treats efficiency as inevitable. Give smart people incentives, add technology, wait…and productivity appears!
Brian Potter’s The Origins of Efficiency dismantles this assumption. The book’s central claim is that efficiency is not a default outcome of markets or technology, but a historically rare achievement that requires deliberate intent and execution.
Efficiency emerges only when a specific set of conditions align, often over decades. Where those conditions are absent, even advanced societies stagnate.
Efficiency Is an Emergent Property
Potter treats efficiency as a property of systems rather than individuals, firms, or technologies. Improvements depend on whether a system can reliably convert inputs into outputs at scale, not on isolated acts of ingenuity.
This perspective explains why:
* Societies with sophisticated tools can remain inefficient
* Early industrial firms were often chaotic and wasteful
* Some modern sectors show little productivity growth despite heavy investment
Efficiency requires coordination across many actors and time periods, which makes it difficult to achieve without supporting institutions.
Efficiency is not something a system can simply “adopt.” It is an emergent property that appears only when multiple layers reinforce one another.
Four conditions recur throughout Potter’s historical analysis:
* Legibility: the system can be measured and compared over time
* Repeatability: work can be standardized and reproduced reliably
* Energy: power is cheap, predictable, and abundant
* Authority: someone has the right to change how work is done
Remove any one of these layers and optimization collapses. This is why pre-industrial societies stagnated despite ingenuity, why early factories were chaotic and wasteful, and why modern sectors like construction and healthcare remain stubbornly inefficient.
Efficiency is not a trait of people or machines. It is a property of systems that can see themselves clearly and act on that information.
The Continuous Flow Process
The Core Mechanism Behind Sustained Efficiency
One of Brian Potter’s most important frameworks in The Origins of Efficiency is his emphasis on the continuous flow process as the foundation of durable productivity gains. Rather than treating efficiency as a general outcome of industrialization, Potter shows that it depends on a specific way of organizing work.
What Are “Continuous Flow Processes”?
A continuous flow process is one in which:
* Work moves through a system in a steady, predictable sequence
* Tasks are decomposed into discrete, repeatable steps
* Inputs arrive at a regular rate and outputs leave continuously
* Interruptions, batching, and handoffs are minimized
The defining feature is not speed, but regularity. The system is designed so that work rarely stops, accumulates, or resets.
This contrasts with:
* Craft production
* Project-based work
* Batch-and-queue systems
In those systems, work advances in bursts, with frequent pauses and reconfiguration between stages.
Why Continuous Flow Enables Efficiency
Potter argues that continuous flow is the organizational precondition for sustained efficiency improvements. It enables several reinforcing mechanisms.
First, it makes processes measurable. When work proceeds in a stable flow, it becomes possible to observe throughput, identify bottlenecks, and compare performance over time. Without flow, variation dominates the signal.
Second, it enables learning-by-doing. Small improvements compound only when the same process is repeated continuously. If each unit of output is produced differently, lessons do not accumulate.
Third, it supports standardization. Continuous flow requires consistent inputs, fixed task sequences, and controlled variability. These constraints are what allow systems to improve incrementally rather than reset with each job.
Fourth, it lowers coordination costs. Instead of relying on ad hoc human judgment to manage transitions, the system itself governs timing and handoffs.
Why Some Sectors Resist Continuous Flow
Potter uses continuous flow to explain persistent productivity gaps across sectors.
Continuous flow is difficult where:
* Outputs are highly customized
* Work is site-specific
* Demand is irregular
* Responsibility is fragmented across firms
* Regulation constrains process redesign
Construction is the canonical example. Each project resets the process, preventing stable flow and cumulative learning. As a result, productivity improvements remain local and temporary.
Continuous Flow vs. Optimization
A key point in the book is that continuous flow often precedes formal optimization.
Flow creates the conditions under which optimization becomes meaningful:
* Stable baselines
* Repeated cycles
* Observable effects of changes
Attempts to optimize before flow exists usually fail because variation overwhelms improvement signals.
Efficiency, in this framework, is not achieved by better decisions within chaotic systems, but by reducing chaos first.
Thanks for reading SLASOG: Leaders are Readers! Subscribe for free to receive new posts and support my work.
Share the post with someone who will benefit from it.
Subscribe here to to be first to know when the next episode drops: https://www.youtube.com/@SLASOG
For more of my thoughts, follow me on LinkedIn.
Get my book Data Impact for a pragmatic take on data-driven value creation for business.
Thanks for reading SLASOG: Leaders are Readers! Subscribe for free to receive new posts and support my work.
This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit thesystemgambit.substack.com
