Why Your War Plans Fail Before They Even Start
I spent six years running logistics for coalition forces in the eastern Mediterranean. Good plans broke down in hours. Not because the planning was bad, but because the battlefield refused to stay static. This is the core problem. The Nature Of War Is Constant Change. The military calls this friction. Clausewitz wrote about it three hundred years ago. It's not a theoretical concept you study once and then forget. It's the thing that makes your morning briefing irrelevant by noon. I'm going to walk through how to actually work with constant change instead of pretending you can predict it away.
The Nature Of War Is Constant Change
Here's what people misunderstand. They think constant change means unpredictable enemies doing unexpected things. That's only half of it. The bigger source of disruption comes from your own side. Supply chain delays. Radio failure during a critical moment. A commander making a decision based on stale intelligence. Friendly fire. Weather. Terrain degradation. All of it compounds in real time. In practice, the solution isn't better prediction. It's building systems that absorb disruption without collapsing. Here's how that actually works. First, stop planning for a specific scenario. Plan for a range of possible situations using what we call contingencies. I used to run three major contingency scenarios for every deployment. By the second day on the ground, all three were wrong. Now I run scenario foundations instead. These are reusable decision frameworks that apply across multiple situations. When the enemy does something unexpected, you already have a mental model for how to respond. It cuts decision time from forty-five minutes down to roughly ten.
Second, build redundancy into your communication chains. Not just backup radios. I'm talking about backup people. Backup routes. Backup timing schedules. During a 2019 operation near the Syrian border, our primary tactical network went down at 0300 hours due to an electromagnetic pulse from an incoming drone strike. We had a secondary net, but the operator assigned to it had been killed two days earlier and nobody updated the roster. I spent forty minutes trying to reach the replacement who turned out to be stationed forty kilometers away. We lost the window to coordinate a counter-battery fire mission. After that, I made it a non-negotiable rule that every communication role had at least two people trained and equipped, and rosters were verified every six hours. Third, shorten your decision cycles. The OODA loop concept is overused but not wrong. Observe, Orient, Decide, Act. The side that cycles through this faster wins. But here's the part beginners miss: orienting is where most units fail. You collect data fast now. Drone feeds, satellite imagery, signals intel. But orienting means interpreting that data in context. That's the bottleneck. I've seen entire operations stall because the intelligence cell was too busy consuming raw feeds to actually produce actionable assessments. The fix was assigning one person whose only job was to output a single-page situational summary every thirty minutes. No jargon. Just what changed, what it meant, and what you should do about it. Fourth, accept that your reserve forces will always be delayed. Reserve forces exist for exactly this reason. They're there when things go wrong. But they always arrive later than you think. In my experience, reserves take 1.5 to 2 times longer to deploy than your logistics team estimates. Always plan for that. Always. I remember one planning session where logistics claimed a mechanized battalion could reach the objective in four hours. It took eleven. The terrain was mud, the lead vehicle broke an axle, and the bridge they were supposed to use was classified as light-duty when it was rated for heavy armor. Eleven hours instead of four. That gap between planned and actual is where operations live or die.
Get the Full Details
There's a counter-intuitive insight here that most doctrine manuals don't emphasize. Constant change favors the defender slightly more than the attacker. Defenders adapt to what the attacker does. Attackers have to change their plans before they even know what the defender is doing. This is why defensive operations tend to hold longer than offensive ones in asymmetric conflicts. If you're attacking, you need overwhelming local superiority at each point of contact because you can't reliably adapt once the engagement starts. The defender adapts continuously. Another thing nobody likes to admit: decentralized command fails badly when your junior leaders lack judgment. The theory is sound. Give small unit leaders the authority to make decisions because they have the best real-time picture. But I've seen junior officers freeze when the plan dissolved because they'd been trained to follow orders, not to assess situations. Decentralization without competence is just chaos with extra steps. The workaround I found was what we called pre-execution conferences. Before any operation, you bring all the subordinate leaders together and walk through the intent. Not the detailed plan. The intent. What are we trying to achieve? What conditions would make this approach wrong? What's acceptable versus unacceptable? When they understand the why, they can improvise the how. It takes twenty minutes and it saves hours of confusion later. Now the limitations. This approach doesn't solve everything. Constant change is exponential, not linear. Small disruptions cascade. A three-minute radio delay becomes a misplaced battalion. A misplaced battalion creates a gap in the line. A gap gets exploited. You can build all the redundancy and adaptive frameworks you want, but at some scale the system breaks. I learned this during an operation where our area of responsibility expanded by 40% in a single overnight shift due to a diplomatic agreement. Our adaptive command structure worked fine for the existing force. It had no answer for managing 40% more territory with the same personnel. We held the line, but it was ugly and costly. The honest answer is that some situations simply require more resources, not better adaptation.
The alternative when adaptation fails is to reduce the scope of operations. Accept that you can't control everything and deliberately choose where not to fight. This is hard for commanders because it feels like surrender. It's not. It's resource allocation. Every kilometer you stop trying to control is a kilometer where you don't need to adapt. Training is the other piece that gets overlooked. You can't adapt to constant change if you've never practiced adapting. Most military training is scripted. Blue force does this. Red force responds like this. The exercise ends. The problem is that scripted training creates brittle forces. They perform well until reality diverges from the script. I started running unscripted exercises where conditions changed without warning. Weather shifts mid-exercise. Communication jammed at random intervals. Reinforcements never arrived because the driving actor showed up late. It was frustrating. It looked bad on paper. But it built a different kind of readiness. The kind where your people don't panic when the plan falls apart. They start solving problems immediately because they've solved problems before. One final practical note. Document everything, even the failures. After-action reports are often exercises in blame avoidance. I made mine a different kind of document. The only question was: what happened versus what we expected? No names. No rankings. Just the delta between expectation and reality. Over six years, these documents became a institutional memory that outlasted individual deployments. New personnel could read them and understand not just what to do, but why the obvious thing usually goes wrong.
Constant change isn't a problem to solve. It's the environment you operate in. The skill is learning to function inside it rather than fighting against it.
