Framework Deep Dives

Military strategy frameworks applied to modern decisions: Clausewitz, Eisenhower, Grant and the documented doctrine

Friction and fog of war, coalition leadership and simple orders, explained through the actual doctrine and campaign records, with no glorification of the wars themselves.

By Gareth Hoyle·24 August 2026·8 min read

Military strategy is among the oldest continuously studied bodies of writing on coordinated action under severe uncertainty, and this guide treats it exactly that way, as a documented discipline worth studying for its reasoning, not as an endorsement of the wars in which that reasoning was applied. Carl von Clausewitz gave the field its clearest vocabulary for why plans degrade in execution. Dwight Eisenhower coordinated a coalition of allies with genuinely competing interests into a single functioning campaign. Ulysses S. Grant issued orders clear enough to survive an entire chain of command intact. This guide takes the collection's signature frameworks in turn, with the documented doctrine or correspondence behind each, before addressing directly why studying this category requires more caution than most.

The frameworks below are drawn from officers who wrote or were extensively documented specifically explaining their reasoning, not simply from whoever won a given campaign; the goal is the documented thinking behind coordinated action under uncertainty, a problem that recurs well outside any battlefield, examined with the moral seriousness the actual subject matter demands.

Why this category earns more scrutiny than most

Unlike a coaching or business framework, where a bad application mostly costs a game or a quarter, the frameworks below were developed to coordinate lethal force, and the historical record of their application includes serious moral failures alongside genuine strategic insight. This guide separates the two deliberately throughout: the reasoning is presented because it survived consequence and is still studied by militaries and strategists today, not because the wars themselves were just.

Friction and fog of war

Clausewitz's On War introduced friction as the accumulation of countless small factors, exhaustion, weather, miscommunication, chance, that separate a plan on paper from the same plan under actual execution. His documented argument treats friction not as an occasional failure to be engineered away but as a permanent condition of complex coordinated action, meaning a good plan is one that has built in slack for the friction that will inevitably occur, not one that assumes a clean execution.

A worked example: a military campaign plan that assumes supply lines will function exactly as scheduled, communications will arrive without delay, and units will move at the planned pace is, in Clausewitz's framework, not accounting for friction at all; a plan that instead builds in redundant supply routes, communication delay tolerance and buffer time between phases is designed around the expectation that something will go wrong, without knowing in advance exactly what.

Where it fails: building excessive slack into every plan to account for friction can itself become a source of sluggishness that costs the tempo advantage a faster, tighter plan would provide; the discipline requires judgement about how much friction to plan for, and Clausewitz's framework describes the phenomenon more precisely than it prescribes exactly where that balance sits for a given situation.

Coalition leadership

Eisenhower's documented role coordinating the Allied invasion of Europe required managing genuinely competing national interests and strong personalities, including British and American commanders with differing strategic priorities, without the kind of unified command authority a single national military structure would have provided. Historians consistently credit his diplomatic skill at maintaining a functioning coalition as at least as central to the campaign's success as any specific tactical decision.

A worked example: Eisenhower's documented handling of disagreements between commanders including Montgomery and Patton, each publicly advocating for different strategic approaches at various points in the campaign, required him to repeatedly reinforce the shared objective that made continued cooperation rational, rather than resolving the disagreement by simply overruling one party, which risked fracturing the coalition his authority actually depended on.

Where it fails: coalition leadership of this kind requires the coalition's members to share a strong enough common objective that continued cooperation remains more valuable to each of them than defection or open conflict, a condition that doesn't hold in every coalition; the framework offers less guidance for a coalition where the underlying interests have genuinely diverged past the point diplomacy can bridge.

Simple orders

Grant's documented military correspondence throughout the American Civil War is notable for its clarity and brevity relative to many contemporaries, giving subordinate commanders unambiguous objectives rather than elaborate, contingency-heavy instructions. His approach reflected a documented belief that complexity introduced at the top compounds into confusion by the time an order reaches the units actually executing it.

A worked example: Grant's orders during several documented campaigns specified a clear objective and the general approach, while leaving tactical execution detail to the commanders on the ground closest to the actual conditions, a delegation of judgement within a clear overall intent that historians contrast with more prescriptive, detail-heavy command styles used by some other generals of the same era.

Where it fails: simple orders require subordinate commanders capable of exercising sound judgement within the latitude the simplicity creates; the approach transfers poorly to a command structure with inexperienced or unreliable subordinates who need more explicit direction, where the same brevity that worked for Grant's proven commanders would produce dangerous ambiguity instead.

Strategic patience

Musashi's Book of Five Rings, documenting decades of undefeated duelling experience near the end of his life, emphasises adaptability and reading an opponent's timing and psychological state over reliance on any single fixed technique, a strategic patience distinct from passivity: waiting for the position and the opponent's state to develop before committing decisively.

A worked example: Musashi's documented emphasis on varying rhythm and timing to disrupt an opponent's expectations, rather than relying on a single dominant technique repeated regardless of context, reflects a strategic patience aimed at letting the opponent reveal their pattern first, then exploiting the specific opening that pattern creates.

Where it fails: strategic patience assumes the situation is genuinely still developing and that waiting produces better information rather than simply losing initiative to an opponent who is using the same time productively; the discipline requires judgement about when patience has become the situation's genuine strategic requirement versus when it has become an excuse for indecision.

Operational tempo

The doctrine of moving faster than an opponent's decision-and-response cycle, documented across multiple campaigns including Rommel's rapid North African advances, treats speed as a strategic weapon in itself: an opponent perpetually responding to your prior position, rather than your current one, is an opponent who has effectively already lost the initiative regardless of the raw numbers on either side.

A worked example: Rommel's documented rapid advances in North Africa repeatedly outpaced Allied commanders' ability to gather accurate intelligence and respond, forcing them to react to positions Rommel's forces had already moved beyond, a tempo advantage credited across multiple campaign accounts with offsetting a real disadvantage in overall force numbers and supply.

Where it fails: sustained operational tempo requires logistics and command capacity able to keep pace with the speed of movement, a documented vulnerability in Rommel's own campaigns, where supply lines repeatedly failed to keep up with the advance, eventually constraining operations that tempo alone could not sustain once logistics became the binding constraint.

Lead from the front

Rommel's documented practice of positioning himself close to the front line during his North African campaigns, personally observing terrain and unit conditions rather than directing exclusively from rear headquarters, reflected a belief that tactical improvisation required first-hand information no report delivered to a distant command post could fully capture in time to matter.

A worked example: Rommel's documented habit of personally reconnoitring terrain ahead of a planned advance, sometimes at real personal risk, gave him tactical information, the actual state of the ground, enemy positioning visible from a forward vantage, that shaped rapid in-the-field adjustments his rear-based staff could not have supplied on the same timeline.

Where it fails: leading from the front concentrates irreplaceable command judgement in a single, personally exposed position, and Rommel's own approach removed him from broader strategic oversight during the periods he was forward, a trade-off that worked while his forward tactical judgement was the more valuable resource but that carries an obvious risk to overall command continuity if the leader is killed, captured, or simply unavailable at a moment requiring broader strategic decision-making.

Reading this category with the necessary caution

This guide describes documented strategic reasoning, not an endorsement of the wars in which it was applied. The American Civil War, in which Grant fought, involved the Confederacy's cause of preserving slavery, which deserves no moral ambiguity regardless of any tactical admiration for Grant's command style. Rommel and Patton fought within regimes and campaigns that require the same critical distance. Read this category the way you would any primary historical source: for the reasoning that survived consequence, evaluated separately from whether the cause it served deserved to.


The Military Strategist category collects these frameworks, and others including George Patton, as downloadable .md files for Claude, ChatGPT or any LLM. Patton's documented emphasis on aggressive tempo and personal theatre as a tool for maintaining troop morale under pressure, distinct from Eisenhower's more diplomatic coalition style, extends this collection's range into territory this guide didn't have room to cover in full. Dwight Eisenhower also appears in The Decision-Maker's Stack, a ten-persona bundle for cross-domain thinking under high-stakes uncertainty.

FAQ

Frequently asked questions

What did Clausewitz actually mean by 'friction' in war?

In On War, Clausewitz used friction to describe the countless small factors, exhaustion, weather, miscommunication, chance, that make even a simple plan difficult to execute exactly as designed, distinguishing war on paper from war as it's actually fought. His documented argument is that friction is not a flaw to be eliminated but a permanent condition of any complex coordinated action, meaning a plan's value lies partly in how much slack it builds in for the friction that will inevitably occur.

Was Eisenhower's coalition leadership during World War Two actually as difficult as it's made out to be?

Documented historical accounts, including Eisenhower's own later writing, describe genuinely difficult coordination across Allied commanders with competing national interests, differing strategic priorities, and strong personalities including Montgomery and Patton, each pushing for their own preferred approach. Eisenhower's role required navigating those competing demands to maintain a functioning coalition, documented as requiring as much diplomatic as military skill, a balance historians consistently credit as central to the invasion's success.

How does Grant's 'simple orders' approach actually work in practice?

Grant's documented military correspondence during the American Civil War is notable among Civil War generals for its clarity and brevity, giving subordinate commanders unambiguous objectives rather than elaborate, contingency-laden instructions. His own writing reflects a belief that complexity in an order compounds into confusion at each level it passes through, so orders reduced to the minimum necessary detail were more likely to survive the actual chain of command intact.

Is it accurate to describe Miyamoto Musashi's Book of Five Rings as still relevant strategic writing?

Musashi's text, written near the end of his life documenting decades of undefeated duelling experience, is still studied for its emphasis on adaptability, timing and psychological awareness of an opponent rather than fixed technique, principles that transfer beyond swordsmanship into any adversarial or competitive strategic context. The specific combat techniques described are historically specific to his era's weaponry; the strategic and psychological principles are what modern readers and translators have found to hold up.

Are these frameworks endorsing the actual wars these strategists fought?

No. Several of the strategists in this collection, Rommel, Patton and Grant among them, fought wars whose causes and conduct require serious critical evaluation, and the American Civil War in particular involved a cause, the preservation of slavery by the Confederacy, that deserves no ambiguity. These frameworks describe documented patterns of strategic reasoning and coordination under pressure, studied because the reasoning survived consequence, not as an endorsement of the wars or causes involved.

Can 'operational tempo' be applied to business without it just meaning 'move fast and break things'?

Yes, and the distinction matters. Operational tempo as documented in military doctrine specifically means moving faster than a competitor's decision-and-response cycle, so your next move addresses their outdated information, not simply acting quickly without regard to consequence. Applied to business, it means shipping and adjusting faster than a competitor can respond to your last move, a more precise and more defensible claim than a general bias toward speed and disregard for downside.

How do you apply 'coalition leadership' when you don't have Eisenhower's formal authority over the parties involved?

Eisenhower's own documented approach relied heavily on diplomatic skill and shared strategic purpose precisely because his formal authority over strong, differently-motivated Allied commanders was itself limited and contested. The transferable lesson for a leader without full authority over stakeholders is his documented practice of finding and repeatedly reinforcing the specific shared objective that made continued cooperation rational for parties who otherwise disagreed on method.

Can these frameworks replace actual military training, strategy consulting, or crisis management expertise?

No. Military judgement is built through training and experience under conditions no document replicates, and modern strategy or crisis consulting brings situated expertise in a specific domain that a framework file cannot supply. These frameworks describe the documented reasoning of historical strategists and sharpen the questions worth asking; they are not a substitute for trained expertise in an actual high-stakes strategic or crisis situation.

Written by Gareth Hoyle. Last updated 24 August 2026. Part of the authority.md guides library.

Keep reading

More guides.