An Army Marches on Its Stomach

Transfers

Attributed to Napoleon (and sometimes to Frederick the Great), this aphorism encodes the military discovery that logistics determines strategy. An army’s fighting capability is not primarily a function of its soldiers’ courage, its officers’ tactics, or its weapons’ quality. It is a function of whether those soldiers ate today, whether those weapons have ammunition, and whether the supply chain connecting the rear echelon to the front line is intact. The stomach — the least glamorous organ of war — is the binding constraint.

The metaphor is now dead in most business contexts. “Infrastructure” and “logistics” have become standard organizational vocabulary, and few speakers consciously invoke the military source when they argue for investing in supply chains, tooling, or operational support. But the structural insight remains sharp.

Key structural parallels:

• The binding constraint is unglamorous — in the military source, generals want to discuss maneuver, envelopment, and decisive battle. Napoleon’s aphorism redirects attention to flour, fodder, and road conditions. The metaphor imports this structure: in any organization, the constraint that actually limits performance is usually the one that leaders find boring. In software engineering, the binding constraint is rarely the algorithm and usually the deployment pipeline, the monitoring system, or the on-call rotation. In healthcare, it is rarely the surgeon’s skill and usually the scheduling system, the sterilization turnaround, or the bed management process.

• Logistics fails silently until it fails catastrophically — a well-supplied army feels no different from a lucky army. The supply chain is invisible when it works. Only when it breaks does its centrality become apparent, and by then the damage is done. Napoleon’s own Russian campaign of 1812 is the canonical illustration: the Grande Armée began with over 600,000 troops and adequate supplies, but the supply chain could not sustain an advance of 600 miles into hostile territory. By the time the logistical failure was undeniable, the army was already deep in Russia with no way to recover. This maps directly to organizational contexts where infrastructure investment is deferred until a crisis reveals its absence — the server that was never redundantly provisioned, the documentation that was never written, the succession plan that was never created.

• Amateurs study tactics; professionals study logistics — this corollary (attributed to various military historians) extends the metaphor’s structural claim. The tactical moment — the battle, the product launch, the quarterly earnings call — is what outsiders see and what leaders celebrate. But the outcome of that moment was largely determined by the logistical preparation that preceded it. In organizational terms, the company that invests in developer tooling, onboarding processes, and internal documentation will outperform the company that invests in heroic product launches, because the former builds sustainable capability while the latter depends on repeated peak performance.

• Supply lines are attack surfaces — in military doctrine, the supply chain is the adversary’s preferred target because it is long, distributed, and lightly defended. Cutting a supply line degrades the entire force without engaging its strongest elements. This transfers to competitive strategy (attacking a competitor’s distribution channel rather than their product), cybersecurity (targeting the software supply chain rather than the application), and organizational politics (undermining a team’s budget or headcount rather than challenging their ideas directly).

Limits

• Military logistics is binary; organizational logistics is a gradient — soldiers either have food or they do not. There is no “somewhat fed.” But most organizational infrastructure degrades gradually. A slow CI pipeline does not stop development; it makes it 25% slower. A mediocre onboarding process does not prevent hiring; it extends ramp-up time. The military metaphor’s drama — starvation, collapse, rout — overdramatizes what is usually a performance curve, not a cliff. This can lead to “everything is on fire” rhetoric about infrastructure investment that loses credibility through overstatement.

• The metaphor centers material inputs — food, ammunition, fuel. This biases organizational thinking toward tangible infrastructure (servers, tools, office space) and away from informational infrastructure (clear requirements, decision-making processes, feedback loops). Many organizational failures that look logistical are actually communicational: the team had the tools but did not know what to build.

• It imports top-down provisioning — in a military supply chain, logistics is planned by generals and delivered to soldiers. The troops do not provision themselves. This maps poorly to modern organizations where teams are expected to be self-sufficient: choosing their own tools, managing their own cloud resources, writing their own documentation. The metaphor can justify centralized infrastructure teams that become bottlenecks rather than enablers.

• Napoleon himself violated the principle — the most famous proponent of logistical thinking repeatedly launched campaigns that outran his supply capacity, culminating in the catastrophic Russian campaign. The gap between Napoleon the aphorist and Napoleon the practitioner suggests that articulating the importance of logistics does not prevent leaders from ignoring it when ambition beckons. Organizations that repeat “we need to invest in infrastructure” while consistently prioritizing feature work are performing the same contradiction.

Expressions

• “An army marches on its stomach” — the standard English form, attributed to Napoleon though the precise origin is disputed
• “C’est la soupe qui fait le soldat” — French form: “It’s the soup that makes the soldier”
• “Amateurs talk strategy; professionals talk logistics” — modern military corollary, sometimes attributed to Omar Bradley
• “Logistics is the ball and chain of armored warfare” — Heinz Guderian’s reformulation for mechanized war, where fuel replaced food as the binding constraint
• “Developer experience is the new supply chain” — contemporary software engineering usage that maps Napoleon’s insight to tooling and CI/CD infrastructure
• “You can’t sprint on an empty stomach” — agile-era adaptation used in engineering management to argue for infrastructure investment between feature sprints

Origin Story

The attribution to Napoleon is traditional but uncertain. Frederick the Great made similar observations, and the insight is as old as organized warfare itself — Xenophon’s Anabasis (4th century BC) is essentially a logistics narrative. What Napoleon contributed was not the insight but the epigrammatic form and the dramatic illustration: his campaigns in Italy (1796-1797) succeeded partly because he solved supply problems his predecessors had not, and his Russian campaign (1812) failed catastrophically when the same logistical discipline broke down over greater distances.

The aphorism’s modern prominence in business and technology discourse dates from the supply-chain management revolution of the 1990s and the DevOps movement of the 2010s. In both cases, organizations discovered that the constraint on performance was not talent or strategy but the infrastructure that connected intent to execution. Amazon’s famous “two-pizza team” structure, Netflix’s investment in internal tooling, and Google’s development of Borg (later Kubernetes) are all practical instantiations of Napoleon’s principle: build the supply chain first, and the army will march.

References

• Napoleon Bonaparte. Military Maxims (various editions) — the traditional source, though the exact wording varies
• Van Creveld, M. Supplying War: Logistics from Wallenstein to Patton (1977) — the definitive military history of logistics as strategy
• Forsgren, N. et al. Accelerate (2018) — empirical evidence that software delivery infrastructure predicts organizational performance
• Xenophon. Anabasis (c. 370 BC) — the earliest detailed logistics narrative in Western literature