Strategy & Tactics

Patterns

Thirteen patterns that decide a battle

This site reads cases as structure rather than heroic legend. These thirteen patterns are what came out of thirteen of them. A pattern is not a template to apply but a tool for checking conditions — which is why every one of them carries the conditions under which it fails.

Last updated: 2026-09-02

Why read for patterns

Read a battle for who was great and all you get is admiration; nothing is left that you can use. So this site looks at who held which premise, and at which moment what gave way. Do that often enough and the same shapes start appearing across cases. Those shapes are the patterns.

But a pattern is not a template. Later commanders who copied the shape of Cannae without its conditions sank into a quagmire. The use of a pattern is not to ask "which pattern is this situation?" but "are the conditions this pattern needs actually present right now?" Hence every card below carries the conditions under which it does not work.

The thirteen patterns

01

A design of space

Make the enemy give up, of his own accord, the ground you want.

Deliberately vacate the place you mean to hold and offer, on your own terms, a target he finds attractive. He judges rationally and moves — and the move redistributes his force exactly as you intended. His correct judgment becomes a component of your design.

Fails when: Nothing happens if he does not move. It has no purchase on an opponent who need not attack, or for whom time is already working. Without a motive on his side to take the bait, you have simply thinned your own line.

Elsewhere: In markets, leave the low end or the periphery open, draw the rival's main effort there, and win in the profitable core. In negotiation, concede heavily on trivia so the other side is satisfied there, and take the clauses that matter.

Austerlitz (1805) →

02

Absorbing momentum

Do not stop his momentum; receive it and change its direction.

Rather than blocking head-on, take the push in, let it come, and arrange things so that his own impetus carries him into the depth of the sack. His greatest strength — numbers, speed, mass — is inverted into an immobile weakness.

Fails when: If the receiving side genuinely breaks, the design becomes an accident. What separates absorbing from collapsing is a command that keeps controlling the rate of withdrawal, not the drawing of a formation. Choose this pattern in an organisation that cannot hold that control and you simply lose.

Elsewhere: When a rival concentrates capital and people in one push, receive it head-on while securing the periphery — complements, distribution, switching paths. In negotiation, take the hard demand, let them push, then secure the flanking terms.

Cannae (216 BC) →

03

A design of time

Take his turns away: chop up the uninterrupted time his procedure needs.

Most operations silently assume time that does not get interrupted. Apply pressure in a stream, and the preparation is broken off before it completes. Even with no hits and no visible result, if you have taken his preparation time you are winning.

Fails when: It has no purchase where the opponent's procedure is robust to interruption — where it can run in pieces or has redundancy. It also demands stamina on your own side to keep up attacks that show no result; measure by short-term output and you will stop yourself.

Elsewhere: In competition, aim not only at output but at the uninterrupted time a rival needs to get organised. In operations, the more a procedure is tuned for normal conditions the more quietly it assumes calm — so keep a degraded-mode version.

Midway (1942) →

04

A design of command

Assume your own chain of command will break, and build in advance for after it does.

Forcing a decisive shape usually destroys your own control along with his. So distribute intent rather than procedure beforehand, and fix the default for when nobody can be reached. Build, in advance, the difference between an organisation that halts the moment direction stops and one that keeps running.

Fails when: Without the training to execute, "use your own judgment" is simply abandonment. Delegation is not a virtue of the delegator but a design on both sides, and it cannot be transplanted without the peacetime work behind it.

Elsewhere: For incidents and front-line judgment, decide in calm conditions what people may do when they cannot reach you. A runbook covers only the foreseen; a shared purpose lets the people present answer for themselves.

Trafalgar (1805) →

05

A design of attachment

Make a place he cannot leave, let his strength be drawn in, and decide somewhere else.

Symbolism and losses already spent drive up the price of withdrawal. While he is holding that objective, he pays the cost of staying there. You settle the matter at a seam he is not holding himself — the junction of a coalition, or the boundary between two owners.

Fails when: It does not work against an organisation that can cut its losses. And pinning costs the pinner too: at Stalingrad the winner's casualties also ran past a million. The design decides whether it can be won, not whether it will be paid for lightly.

Elsewhere: In competition, look at partnerships, subcontractors and acquired divisions — the boundaries between responsibility and resources — rather than the main force. On your own side, set the criteria for stopping before "we have come this far" sets the decision for you.

Stalingrad (1942–43) →

06

A design of frontage

Limit the ground to dimensions in which his numbers cannot deploy — and get him to walk into it.

Numbers are only superiority once they have room. Take a position in a narrow place closed on both sides and his quantity cannot spread sideways; it stacks front to back and turns into density. But choosing the place is not enough. You have to manufacture the reason he comes into it.

Fails when: He will not come in if he can afford to wait — and the side that cannot wait is usually yours. At Agincourt it was the starving English who advanced. Without terrain or conditions that let you narrow the frontage, this pattern does not exist at all.

Elsewhere: Compete in a space too narrow for a large rival to deploy people and budget. In negotiation, narrow the agenda so that the side with more material to bring loses its advantage. Neither works unless you also supply the reason the other side comes.

Agincourt (1415) →

07

A design of convergence

The decision comes from troops who are not on the field yet — and from how many hours away they are.

What decides is not the strength present but the strength that can arrive before the deadline. So there are two jobs before fighting: build the shape in which your second army comes, and the shape in which his does not. The second happens by itself whenever his orders state a procedure and no purpose.

Fails when: A position taken on somebody's arrival becomes the worst position the moment they do not come; the quality of the assurance sets the quality of the position. And when you count up the "if only he had marched", marching time is the one thing you cannot delete — distance and roads do not move.

Elsewhere: In a meeting or a market, count what can be mobilised by the deadline, not who is in the room. If you are relying on another team, pin down how much and when, first. When you delegate, hand over the purpose rather than the procedure, and settle what people may do when they cannot reach you.

Waterloo (1815) →

08

A design of supply

The decision comes not from what he holds but from whether things keep reaching him.

Replace "take that place" with "open the line that place is corking" and the available means multiply at once. Make his line the battlefield and, if you must, give up your own for a while. Cutting your supply costs you supplies — and deletes the obligation to defend a line. That trade is what buys speed.

Fails when: It does nothing against an opponent who does not depend on a line. The side that cuts its own has a deadline: fail to settle inside it and you starve instead. And stopping a line charges the same price to every non-combatant inside it — never put the effect and the price on separate pages.

Elsewhere: Look at a competitor's suppliers, distribution and hiring pipeline rather than their revenue. Drop a fixed cost for a fixed period to widen the range you can move in. Settle it while the other side's two departments, or two decision-makers, are still out of step.

Vicksburg (1863) →

09

A design of defection

Before fighting, take part of his strength out of the count.

What has to be counted is not the men who are there but the men who will obey. Negotiate with the other camp individually beforehand and either bring them over or, at minimum, make them stay still. On the field the two are identical in effect, and the second is far cheaper. The collateral is usually a share of the settlement you do not own yet.

Fails when: It does not exist for someone whose promises are not believed. And from the receiving end, the moment you agree not to move you have given up your only chip, so the price is set by the winner after winning — the Mōri came out of Sekigahara reduced from 1.2 million koku to 370,000.

Elsewhere: Count who will actually move, not who is on the org chart. Before negotiating, establish what you have the standing to guarantee. Do not persuade the whole opposing camp; have them sit it out. Design the period that looks like stagnation as negotiating time.

Sekigahara (1600) →

10

A design of deception

Confirm what he already believes, and the real thing looks like the fake.

The aim is not to go unnoticed. What cannot be hidden is left in plain sight, and a wrong place to file it is prepared in advance inside the enemy's head. Confirming his reasoning rather than contradicting it is cheap, and it keeps working after the real event happens — the real event is consumed as evidence for the fiction.

Fails when: Two things are required: a channel the target believes is his own, and a return line that tells you he believed it. A lie whose replies you cannot read can never be stopped or continued on evidence. It also fails against an enemy who cannot afford to hold anything back — there is nothing there to freeze.

Elsewhere: Ask for the other side's conclusion first: confirming is cheaper than changing. Design where it will be heard from, not only what is said. Build the measurement line before you start. And count the memorable and the effective separately — what goes into the report is what photographs.

Normandy (1944) →

11

A design of the verdict

Decide who rules on winning before you fight.

Whoever decides that you won is usually not fighting. Make it happen where that person can see it, on the indicator that person is watching. Attacking the account the other side has published can beat any tactical gain — break the explanation and the grounds for continuing go before the strength does.

Fails when: Assume there is only one judge and you will miss. The planners of Tet aimed at the population of South Vietnam; the verdict came from the American electorate. Without a deadline on the judge the pattern is slow — with no election, the same events convert into policy far more slowly. And it carries a permanent ethical problem: it drops the bill where the judge is not.

Elsewhere: Before starting, name whoever will rule on success. When there are several scorecards, establish which one carries the authority. Do not let a measurable indicator become the aim. Every "on track" you issue makes a contradictory request harder later.

Tet (1968) →

12

A design of what to lose

When losing, abandon what can be remade and carry home what cannot.

A withdrawal is not loss minimisation; it is a choice. If the ships can carry men or matériel, abandon the side a factory can rebuild. Plant, inventory and cash can be remade; people, and the procedural memory they carry, cannot. And the procedure can only be written before the defeat is settled. Start after it and the time to build the procedure has already gone.

Fails when: The type cannot make time. It only prepares the shape; the time itself is handed over by the enemy or by circumstance (at Dunkirk it was the German halt order). It needs somewhere to go back to and the industry to rebuild. And the hardest condition is the rearguard: somebody has to stay or nobody gets out. You can choose how to lose because somebody who cannot is paying for it.

Elsewhere: The day you decide to close is too late to start thinking about how. Set the order of abandonment by replaceability, not by book value. Have somebody say out loud that the objective has changed from winning to keeping. And a withdrawal plan that does not name the people who stay to the end is not a plan; it is a comfortable story.

Dunkirk (1940) →

13

A design of attrition

Make consuming the other side the objective — but write down first how it stops.

When you cannot break through, move the definition of winning from taking ground to exhausting the other side first. Choose a place the enemy cannot give up, mass the firepower there, and process whatever arrives. If they cannot abandon it, they have to keep sending. At Verdun the French did keep sending — the act of choosing the place worked exactly as intended.

Fails when: This pattern carries a defect of its own: the stopping condition never gets written. With nothing in the plan saying how many is enough, or what to do if the ratio comes out worse than assumed, stopping becomes the fresh decision, and the numbers that could support it do not exist inside the design. That is why the battle ran on for 111 days after Falkenhayn was dismissed. And unlike a design of fixation, this pattern has no elsewhere — stepping out turns everything already spent into a total loss, so you build a structure you cannot step out of. The delivered exchange rate was about one to nine tenths: the stated purpose was never achieved.

Elsewhere: Price wars, litigation, long political fights — put a number on how much you lose before you walk, while you are still calm enough to write it. If the goal has quietly become outlasting them, the route to winning has been lost. Keep exactly one route to winning that lives outside the thing you are currently doing: what ended Verdun was the Somme. And watch the period just after you survive. An organisation that has endured attrition overestimates how well attrition works.

Verdun (1916) →

The losing side has a pattern too: sound caution losing to a structure

Line the cases up and, quite apart from the winning patterns, the same failure keeps reappearing: someone reads the conditions correctly, and the structure of the organisation crushes that judgment.

  • Kutuzov (Austerlitz) — saw that time was on his side and argued for waiting; a young emperor and a hawkish court overrode him.
  • Paullus (Cannae) — wanted to avoid a battle on the plain; a system in which two consuls held the whole army on alternate days cancelled his caution. He died on the field.
  • Gravina (Trafalgar) — argued against sailing on account of the weather. As one of two partners he had standing to object, but not the weight to reverse the decision.
  • Dumitrescu and Paulus (Stalingrad) — the weakness of the flanks was reported and permission to break out was requested. There was no reserve, the estimate above was wrong, and neither carried.
  • Boucicaut and d'Albret (Agincourt) — they brought the lesson of the last defeat, planned to fight dismounted, and raised the option of not fighting at all. But with the king and the Dauphin absent, a council of princes who outranked them would not carry caution. Even the formation was shaped by precedence rather than tactics.
  • Gérard (Waterloo) — hearing guns to the west, he urged his superior Grouchy to march to them. The reading was right; the structure of an order that stated no purpose would not carry it.
  • Pemberton (Vicksburg) — the department commander said abandon the town and save the army; the president said hold the town. When two superiors say different things, the man on the spot takes a little of each and loses both.
  • Ishida Mitsunari (Sekigahara) — the operational plan was sound, but as one of five commissioners he had no authority to guarantee anyone's land. When the man commanding has no standing to command, the army he has gathered is a number and nothing more.
  • Rundstedt and Rommel (Normandy) — holding the reserve until the main landing was identified, and stopping a landing at the water's edge, were each militarily sound. But the input to the judgement was manufactured by the enemy, so a correct rule kept returning the answer "not yet".
  • Westmoreland (Tet) — he built a measure of progress, sustained it, and threw the offensive back in weeks. But the scoring was not being done on his yardstick. Attrition measures how much the enemy will absorb; the same clock is counting your own limit too.
  • Lord Halifax (Dunkirk) — with the army in a pocket and the equipment certain to be lost, he argued for exploring terms. This one did not lose to a structure; it lost to another reading. And the side of a closed option can never be tested.
  • The German Crown Prince (Verdun) — pressed early, from the front headquarters, for the offensive to be broken off. He read it correctly. But in a plan with no stopping condition, the burden of proof falls on whoever wants to stop. That is not a matter of logic; it is a matter of what the document contains.

Twelve of the thirteen cases show the same shape. That is not coincidence; it is a pattern. Reading it right and being able to make an organisation act on it are different abilities. And this is the pattern most likely to happen to you.

The other recurring job: correcting the story

Every case has a story that became more famous than the events. Each article on this site carries exactly one correction. The correction is not the point — an explanation of the form "one battle decided everything" or "it was bad luck" pushes the things that actually decided it out of view.

  • Austerlitz — thousands said to have drowned in the frozen ponds. When the ponds were later drained, far fewer bodies were found.
  • Cannae — the idealisation of the double envelopment. Commanders who copied the shape without the conditions sank into a quagmire.
  • Midway — the "fateful five minutes". Against the Japanese primary records, what stood on the decks was mainly the defensive fighter patrol, not a spotted strike.
  • Trafalgar — "it stopped the invasion". The invasion army had broken camp at Boulogne in late August, before the battle. The order is reversed.
  • Stalingrad — "General Winter did it". The ring closed on 23 November, and both armies were fighting in the same winter.
  • Agincourt — "the longbow pierced plate armour". Neither recent scholarship nor shooting trials support it. Some arrows got through, but what told was less killing power than pushing men toward the centre and raising the density. And the ratio of forces is itself unsettled among historians, so even the premise of an overwhelming disparity is unproven.
  • Waterloo — "a near-run thing". That verdict only holds from inside the battlefield. The Prussians were closing by four in the afternoon, and from that hour the French reserve was already being cut into.
  • Vicksburg — "the turning point was Gettysburg". They fell in the same week (3 and 4 July), and it was the second that halved Confederate logistics permanently. What stayed in the memory was the one that made a better drama.
  • Sekigahara — "Kobayakawa's betrayal decided it". The negotiations were under way before the battle, and the 30,000 on Nanguyama did nothing at all on the day. "Betrayal" is a word for compressing months into a day.
  • Normandy — "rubber tanks fooled the reconnaissance". By 1944 the Luftwaffe could barely photograph England and most of the decoys were never seen by anyone. What worked was the clerical traffic of double agents. A photogenic device took the memory slot belonging to the one that worked.
  • Tet — neither "America lost" nor "the war was lost by the press" stands up. The mistake both share is assuming that winning can be measured on one scale. This battle had three scorecards — loss ratios, ground, and the patience of the American electorate — and only the third had any authority.
  • Dunkirk — "a miracle in which little ships lifted an army off a beach". 98,671 left from the beaches and 239,555 from the East Mole, and the preparation began on 20 May. But this correction has a second half: that story supplied the reason that held up the decision not to stop.
  • Verdun — the claim that Falkenhayn planned to bleed France white. The Christmas Memorandum said to prove it has never been found, and the only source is his own memoir of 1920. The Prussian army archive burned in 1945. This correction is aimed at our own method: there is a permanent risk of mistaking a blueprint drawn afterwards for one drawn before.

The corrections come in five kinds: inflation (an event swells), omission (an event drops out of view entirely), compression (months are folded into one day’s decision), substitution (a photogenic cause takes the seat of the effective one) and units (the result is argued about while nobody has agreed what counts as winning). What they share is one thing: credit everything to a single day or a single factor and the years that built that day disappear. And the correction does not stop at the correction. After “that is not what happened”, write “then what was that shape for” — the Dunkirk case is the worked example. The rules for this are in the editorial policy.

How to use the patterns

These patterns are not boxes for classification. Use them by asking, in this order:

  • What does the opponent consider rational? — space, momentum and attachment are the patterns that make his correct judgment a component of yours.
  • What does his procedure assume? — if it assumes uninterrupted time, the design of time applies.
  • Do his numbers and resources have room to spread? — if they do not, the design of frontage applies.
  • Is there strength that can still arrive? — if there is, the design of convergence comes first.
  • What line does he depend on? — if he depends on one, the design of supply applies.
  • How much of his number will actually obey? — if there is a gap, the design of defection applies.
  • Through what channel does he learn his own situation? — if you can reach that channel and read his reaction, the design of deception applies.
  • Who finally rules on who won? — if it is not one of the people fighting, work out the design of the verdict first.
  • If this is lost, what gets abandoned and what comes home? — too late to ask once you are losing. A design of what to lose can only be written while you might still win.
  • Can my own command survive the shape that settles it? — if not, the design of command has to come first.
  • Am I currently inside the conditions under which this pattern fails? — that is what the "fails when" line on each card is for.

More patterns do not make a better reading. Adding one is only worth it when the case does not fit any pattern already here. Which is why the next case on this site is chosen by whether it is a missing pattern, not by whether it is famous.

Related pages