Friction
Carl von Clausewitz, the Prussian officer whose On War was published by his widow in 1832, gave a name to the thing that separates the plan from what actually happens. He called it friction. “Everything in war is very simple,” he wrote, “but the simplest thing is difficult.” Not because the plan was bad. Because reality is made of a thousand tiny, individually trivial frustrations — fatigue, weather, a garbled order, a wrong turn, fear, a wagon stuck in mud — that accumulate until even marching a column down a road on schedule becomes an achievement.
Friction, Clausewitz said, is the only concept that distinguishes real war from war on paper. On paper the units move where you put them. In reality, everything drags.
The crucial thing about friction is that it isn’t one big obstacle you can plan around. It’s the sum of countless small ones you can’t individually predict — each minor, each surprising, the combination unavoidable. You can’t eliminate it, because you can’t foresee which particular small things will go wrong; you can only build in the slack and the resilience to absorb them. This is why experienced commanders distrust elegant, tightly-coupled plans: the more steps that each have to go right, the more surface friction has to grab. A simple plan robustly executed beats a brilliant one that requires everything to cooperate.
It connects to Gall’s Law (complex systems that work grew from simple ones that worked) and to failure modes more broadly: friction is the ambient resistance that turns “obviously this will work” into “why is nothing working.” It’s the reason slack is productive rather than wasteful — the buffer is what friction eats instead of your whole plan.
Anyone who has run a project recognizes friction without the military vocabulary. The migration that should take an afternoon and takes a week. The launch where every individual task was easy and the whole thing was somehow agony. None of the delays were dramatic; each was a small thing — a missing credential, a meeting that slipped, a dependency nobody flagged — and together they were the project. The plan was never wrong. It just lived on paper, where the simplest thing is simple.
The practical posture Clausewitz points to is humility about plans and respect for execution. Assume friction. Pad the estimates not because you’re pessimistic but because you’re accurate. Prefer the robust simple plan to the fragile clever one. And treat the team’s ability to absorb small chaos — to keep moving when little things go wrong, which they will — as a real capability, not an afterthought. The difference between organizations is rarely the quality of their plans. It’s how much friction they can swallow and keep going.