Behavioral
Behavioral

Strategy 12: The Grand Strategy

Behavioral Mechanics

Strategy 12: The Grand Strategy

Watch someone win and you usually understand what they did. Watch a grand strategist win and you usually don't — not until years later.
developing·concept·1 source··Aug 7, 2026

Strategy 12: The Grand Strategy

The Zigzag That Made No Sense

Watch someone win and you usually understand what they did. Watch a grand strategist win and you usually don't — not until years later.

Alexander's generals spent four years unable to explain their own commander. He attacked when he shouldn't have. He was merciful when he should have been vengeful. He had the Persian army at his mercy and then wandered south into Egypt instead. He started wearing Persian clothes.1

None of it read as a plan. All of it was one.

That gap — between what a plan looks like from inside a single move and what it looks like from the end — is the entire subject of Greene's twelfth strategy. He calls the capacity to work in that gap grand strategy, and defines it simply: you look beyond the immediate battle and calculate ahead.1

Battle Thinking and Campaign Thinking

Here's the distinction the whole chapter runs on.

Ordinary strategy asks: how do I win this? Grand strategy asks: supposing I win this, where does it leave me — better off or worse?1

Greene traces the question to Sun-tzu and Thucydides, who both noticed the same self-destructive loop in warfare. Kings won battles and then grew drunk on victory. They didn't know when to stop. They stirred up hatred and distrust on every side, ended up fighting on several fronts, and lost everything. The Assyrian Empire won its way into the sand.1

The fix was to think one link further down the chain. Then two. Then the whole chain — which is the concept of a campaign, in which individual battles matter only for how they set up the next ones.

And once you're thinking in campaigns, something odd becomes possible:

an army can deliberately lose a battle as part of a long-term plan.1

That single sentence is why the chapter is titled Lose Battles But Win the War.

Principle One: A Goal Specific Enough to Refuse Things

Greene's first principle sounds like a motivational poster and isn't. The distinction he draws is between goals and wishes.

Most of us think we operate by some kind of plan. We don't. What we have are wishes — fame, success, security, something large and abstract. Emotion infects us with hazy desire, and haziness unbalances everything downstream from the beginning.1

The test of a real goal is not that it inspires you. It's that it lets you turn things down.

If some glittering prospect threatens to seduce you from your goal, you will know to resist it. You can tell when to sacrifice a pawn, even lose a battle, if it serves your eventual purpose.1

Napoleon is the working example. At the start of a campaign he could see its last battle in his mind; examining a map with his aides, he would point at the exact spot where it would end. Maps of the era were notoriously unreliable and war is subject to chance — and yet the predictions kept coming true.1

He visualised the aftermath too: the treaty, its conditions, how the defeated emperor would look, and exactly how this victory positioned him for the next campaign.1

The goals that hurt you when you get them

Greene attaches a warning most goal-setting advice skips entirely. Some objectives damage you by being achieved.

When Israel seized the Sinai in the Six-Day War of 1967, a buffer zone between itself and Egypt looked obviously sensible. What it actually produced was more territory to patrol, a permanent grievance motivating Egyptian hostility, and a stretch of desert vulnerable to exactly the surprise attack that came in 1973.1

The proper objectives of grand strategy, he says, are narrow: build a foundation for future expansion, make yourself more secure, increase your power. Anything that doesn't do one of those three is a wish wearing a goal's clothes.

Principle Two: Seeing Through Somebody Else's Eyes

The second principle is about vision, and Greene makes an unusually blunt case for it.

Looking at the world through your enemy's eyes is not sensitivity, and not political correctness. It is a technical requirement. Your own cultural preconceptions are the main thing stopping you from seeing anything accurately.1

The Vietnam contrast is his proof. The North Vietnamese studied the American cultural scene intensely — shifts in public opinion, the mechanics of the political system, the social effects of a televised war. American strategists showed almost no understanding of Vietnamese culture on either side of the line, north or south. Fixed on stopping communism, they missed the deeper influence of culture and religion on how their enemy would fight.1

Greene's verdict is that this was a grand-strategic blunder of the highest order — not a military failure at all.

The corollary is political. Every individual around you is a political creature securing their own position, and everything you do gets read by them in terms of whether it helps or harms them. So winning a battle at the price of alienating a potential ally, or manufacturing a permanent enemy, is never wise.1 Caesar beat the more experienced Pompey partly by planning each maneuver for its effect on opinion back in Rome — he lacked support in the Senate, so he built it among the public instead.1

Principle Three: Sever the Roots

The third principle is the one with the sharpest edge, because it reframes what a problem is.

Wars and quarrels drag on because neither side knows how to strike at the other's root. So you expand your vision not only outward but downward. Dig for what actually motivates the opponent or supplies their power, and you can end the thing with finality.1

Hannibal invaded Italy in 218 BC and Roman general after Roman general failed to stop him. Scipio looked at the same board and saw something different: the problem wasn't Hannibal, or his Spanish base, or his supply line from the sea. The problem was Carthage.

So Scipio didn't fight Hannibal. He invaded Carthage, and Hannibal had to leave Italy to defend home. Not as a feint — as a real invasion. Rome didn't just beat Hannibal; it removed Carthage as a rival power permanently.1

The related habit is preemption: watching for dangers as they sprout and cutting them down while they are still small enough to cut.1 The full pillar-by-pillar version of Scipio's campaign is the subject of Strategy 16: The Center-of-Gravity Strategy, four chapters later — the same insight given its own chapter.

Principle Four: The Indirect First Move

The last principle is about tempo and disguise. The danger in strategy is losing the initiative and finding yourself constantly reacting. The answer is to plan ahead and plan subtly.

So make your first move merely a setup, designed to extract a response from your opponent that opens him up to what comes next.1

Hit someone directly and they take a defensive pose that may block your next blow. Hit them in a way they can't read, and they're guarding the wrong door.

Alfred Hitchcock made this a working method. He controlled every detail of a screenplay before shooting so a producer had nothing left to interfere with. If a producer tried to meddle on set, Hitchcock kept a camera ready with no film in it — he'd shoot the extra takes, the producer felt powerful, the film was untouched. He handled actors the same way, infecting them with the emotion he wanted through how he treated them on set rather than telling them what to do.1

Every step fit into the next one.

The counter-case is Pearl Harbor. Devastating as a surprise; catastrophic as an opening move. The Japanese showed their hand at full strength immediately, rallied American public opinion to a pitch of anger that guaranteed the war would be fought to the end, and did it against the side with more resources.1

Greene's rule from this: the first step sets tempo, determines the enemy's mind-set, and points you in a direction. Deceptively soft is usually right.

Where Failure Actually Lives

The chapter's closing move is the one worth arguing with, and it is also the one worth keeping.

Clausewitz said war is the continuation of politics by other means.1 Greene reads that as a claim about blame. When a war is lost, everyone examines the battles and critiques the generals. But per Clausewitz, failure in war is a failure of policy — the goals were unrealistic, inappropriate, blind to other factors.1

Applied to a life, this becomes uncomfortable:

This means that you yourself are largely the agent of anything bad that happens to you.1

Greene is careful to specify the use of that idea. It isn't for blaming yourself or wallowing. It's for tracing a failure back past the execution to the policy that produced it, so the next campaign starts from a better one.1

Implementation Workflow

You want a thing. Say it's a shift in what your work actually is — a different kind of client, a different medium, a job that doesn't exist yet at your company.

The battle version of this is what you already do. Someone blocks you; you argue. A project goes badly; you fix the project. An opportunity appears; you take it because it's an opportunity. Each move makes sense on its own and none of them accumulate.

The grand-strategic version starts somewhere less comfortable. Before anything else, you write down where this ends — specifically enough that you could point at the spot on the map. Not "more creative freedom." The actual last battle: the piece, the title, the room, the year.

Then you use it the only way a goal is useful: to refuse things. Something glittering arrives in month three — more money, a bigger title, a project everyone wants. You hold it against the endpoint and most of the time you let it go. That refusal is the strategy. People around you will read it as passivity or eccentricity, the way Alexander's generals read the road to Egypt.

Then you look for the root. The obstacle you keep fighting — the colleague, the budget line, the rejection — is usually a symptom. Ask what supplies it. Scipio didn't beat Hannibal, he took away the country behind him.

And you make your first move soft. Not the confrontation, not the pitch, not the ultimatum. The move that extracts a response and opens the next door — an ally acquired, a small piece of work placed where the right person sees it, a question asked of someone who will repeat it. Pearl Harbor was a magnificent tactical success and it announced everything.

Two failure modes to watch, both from the chapter's own Reversal. Early success makes you believe your instincts are infallible; Caesar and Napoleon both went that way.1 And too much detachment can leave you seeing so many options that you can't move — Hamlet with a map.1

Evidence, Tensions, Open Questions

The Alexander and Vietnam cases carry the chapter well, and the Vietnam reading in particular is well supported outside Greene — the asymmetry in cultural study between the two sides is not a controversial claim. [POPULAR SOURCE] for the framing throughout.

The unresolved problem is the retrospective one. Grand strategy is defined by Greene as forethought — planning further ahead than others, in steps whose purpose only gradually becomes visible.1 But every case he offers is read backwards from a known victory. Alexander's zigzag looks like design because it worked. Had the Persian campaign collapsed in Egypt, the identical sequence would read as a young king losing focus. The chapter has no procedure for telling grand strategy from luck while it is happening, which is the only moment the distinction would be useful.

A second tension the chapter creates against itself. Principle Four says the perfect first move is soft and indirect. Yet Alexander's opening as king was the opposite — lightning reconquest of Thebes before anyone could organise against him, and Greene explicitly praises it as the right move for its moment, because "nothing quiets an army faster than battle."1 So the rule is really that the first move should suit the audience it's aimed at, which is a much weaker and more useful claim than the one stated.

Author Tensions & Convergences

Set this against Strategy 2: The Guerrilla War of the Mind and something starts pulling in two directions.

Strategy 2's demand is that you keep the mind moving, erase the last war, hold no fixed principles — "my only principle is to have no principles." Fixity is the enemy; a plan you're attached to is the thing that killed the Prussian army at Jena.

Strategy 12's demand is that you fix a specific endpoint, contemplate it daily, and measure every action against it. Napoleon's pin in the map is the model.

Held together, the reconciliation Greene doesn't state: the goal is fixed and the route is not. What Strategy 2 attacks is a fossilised method; what Strategy 12 requires is a stable destination. Alexander never wavered on ruling the known world and changed how he was getting there roughly every season. The two chapters describe different layers of the same person, and the book leaves the reader to stack them.

There's a convergence worth naming too. Strategy 8: The Perfect Economy Strategy and this chapter are the same argument at different scales — Strategy 8 asks what a victory costs, Strategy 12 asks where it leaves you. Pyrrhus is the figure who fails both tests with the same battle.

Cross-Domain Handshakes

Business → The Difference Between a Roadmap and a Backlog. Product organisations run into this exact split. A backlog is a queue of individually justified moves, each of which passes its own test; a roadmap is a claim about where the thing ends up. Teams that work purely from a backlog ship a stream of defensible decisions and arrive somewhere nobody chose.

The insight the pairing produces, which neither field states alone: the function of a long-term goal is not to generate work, it's to authorise refusal. Greene's grand strategist and a good product lead do the same rare thing — they say no to something that would obviously have been a win, and they can articulate why. That reframes "lack of strategy" from a planning failure into a saying-no failure, which is a much more diagnosable problem. If your organisation can't name something good it declined this quarter, it doesn't have a strategy; it has a backlog and a vocabulary.

Eastern Spirituality → Non-Attachment to Fruits, and Where the Analogy Breaks. The Bhagavad Gita — which Greene quotes in this very chapter1 — instructs Arjuna to act without attachment to the fruits of action. Grand strategy is, on its face, the opposite instruction: fix your gaze on the fruit and let it govern every act.

The insight is in the near-miss. Both disciplines produce the same visible behaviour — calm under reversal, indifference to the local win or loss, the ability to keep moving when a battle is lost. But they get there from opposite ends. Krishna's calm comes from releasing the outcome; Alexander's comes from holding it so firmly that no single day can threaten it. Same surface, opposite mechanism — and the practical consequence is that they fail differently. Non-attachment fails toward passivity; grand strategy fails toward the delusion Greene names in his own Reversal, where a man who has held the outcome long enough begins to believe he is the one causing it. Anyone borrowing contemplative vocabulary to describe strategic patience is quietly swapping one failure mode for the other.

The Live Edge

Sharpest Implication

You cannot be strategic about something you have only wished for. A wish generates activity in every direction, all of it defensible; a goal generates refusals. So the test of whether you have a strategy is not what you're working toward — it's what you turned down this year, and whether you can say why in one sentence.

Generative Questions

  • The last genuinely good opportunity you accepted: did it move you toward the endpoint, or did you take it because it was good?
  • Name the conflict you keep re-fighting. What supplies it? If you can't answer, you've been fighting Hannibal in Italy for fifteen years.
  • Greene reads every lost war back to a failed policy rather than a failed execution. Run it on your last real failure — was the plan badly executed, or was it the wrong plan competently carried out?

Connected Concepts

Footnotes

domainBehavioral Mechanics
developing
sources1
complexity
createdAug 7, 2026
inbound links11
next in Robert Greene
Alexander and the Persian Grand Campaign
Imagine you are a Macedonian general in 334 BC and your job is to advise a twenty-two-year-old.