Here's the instinct, and almost everyone has it. Things are complicated, the stakes are real, so you tighten. More check-ins. More approvals routed through you. Nothing important moves without your sign-off, because you're the one who can see the whole picture.
And the organization gets slower. Not because anyone is lazy — because every decision now has to travel to you and back, and while it's travelling, the situation changes.
Robert Greene's sixth strategy is the counterintuitive fix: break your forces into independent units, give each one a mission and the spirit of the campaign, and let them run.1 You lose some control. You gain mobility, which he argues is the greatest force multiplier there is.
For thousands of years war had been fought essentially one way. A commander led one large unified army against an opponent of roughly equal size. He never broke it into smaller pieces, because dispersal violated the principle of concentration and — the real reason — because scattered forces were impossible to monitor and control.1
In the peace years between 1800 and 1805, Napoleon rebuilt the French military into the Grande Armée, 210,000 strong, and divided it into corps. Each corps had its own cavalry, infantry, artillery and general staff. Each ran 15,000 to 30,000 men. Each was led by a marshal — usually a young officer already proven in a previous campaign.1
Each corps, in Greene's phrase, was a miniature army headed by a miniature Napoleon.
Two mechanisms, both simple.
Napoleon gave the marshals their mission and let them accomplish it themselves, so almost no time was lost passing orders back and forth. And smaller armies need less baggage, so they simply marched quicker.1
The strategic consequence was larger than the sum of those. Instead of one army moving in a straight line, Napoleon could disperse and concentrate seven corps in effectively unlimited patterns — patterns that to an enemy looked chaotic and unreadable, because there was no single line of advance to track.
The chapter's real argument is stated plainly and is worth isolating, because it's the part that generalizes past warfare:
Structure is strategy — perhaps the most important strategic choice you will make.1
A rigid, centralized organization locks you into linear strategies. There is one plan, one axis of advance, and if the plan is wrong you find out slowly. A fluid, segmented organization gives you options — many possible responses, generated close to the situation by people who can see it.
Greene's instruction, if you inherit a group: analyze its structure first, then alter it to suit your purposes. Pour creative energy into the organization itself, with fluidity as the goal. Most people pour that energy into plans instead, which is why most people's plans keep failing to survive contact with reality.
It takes strength of character, Greene says, to allow a margin of chaos and uncertainty — to let go a little.1
The trade is explicit: you give up complete control and receive mobility. What makes this hard isn't intellectual, it's temperamental. A leader who segments their forces will regularly not know exactly what one of their units is doing, and will have to tolerate that in exchange for the unit being able to act on something the leader hasn't seen yet.
The corollary Greene draws is about the people, not the structure: smaller teams are faster, more creative and more adaptable, and their members are more engaged and more motivated. Autonomy isn't only an efficiency mechanism. It's a morale mechanism, because people who can decide things care more than people who execute decisions.
Turning a group loose only works if the pieces will act coherently without being told to. Greene's answer to that is a shared philosophy, held deeply enough to substitute for instructions.
The chapter's model is the Prussian and later German general staff — a structure built deliberately after Jena, self-examining, replicating its own methods down through the ranks, and running on Auftragstaktik, the mission-command doctrine that judged officers on results rather than on obedience.1
The other model is training. Genghis Khan's annual Great Hunt spent three months every winter teaching a scattered army to coordinate across enormous distances without orders — so that in war, Mongol units could disperse and converge in patterns their enemies could only explain by assuming demonic possession.1
Both are answers to the same question: what holds a decentralized force together when nobody is issuing commands? The answer is that the coordination has to be installed before the campaign, through doctrine and rehearsal, or the segmentation just produces a scattered mess.
You run a team of twelve and everything routes through you. You know this is the bottleneck — you've known for months — and every attempt to delegate has produced work you had to redo, which reinforced the routing.
Greene's diagnosis is that you delegated tasks without delegating the mission, and the two fail differently. A person handed a task with no understanding of what it's for cannot adapt when the situation shifts; they either execute it wrongly or come back to ask, which is the bottleneck reappearing.
The change is to hand over an objective and the reasoning behind it, then judge the result rather than the method. Not "build this feature to this spec" but "this customer segment is churning for this reason — fix it, tell me what you chose and why." That's the difference Greene draws between an order to be obeyed literally and a mission to be fulfilled in spirit.
Before that can work, though, install the thing that makes it safe: the shared understanding of what you're all actually trying to do. If your team can't articulate the campaign's purpose back to you unprompted, don't segment yet. A decentralized team without a shared philosophy isn't fast, it's just scattered — you'll get twelve people confidently moving in twelve directions, and you'll correctly conclude that delegation doesn't work.
The historical case is strong and unusually well-corroborated: the corps system is a genuine, documented inflection point in military history, and van Creveld's Command in War — which Greene quotes at length — is a serious scholarly treatment rather than popular retelling.1 The German general staff's performance from 1808 to 1945 is the kind of long-run evidence most management claims never get.
The tension the chapter buries in a two-line Reversal: Greene concedes at the very end that "some people respond better to rigid authority," and that even a loose organization sometimes has to tighten.1 That concession is doing far more work than its length suggests. The entire chapter argues that decentralization is structurally superior; the Reversal admits the optimal structure depends on who is in it — which is a completely different claim, and closer to what the Sherman case in the same chapter actually demonstrates.
A second, larger tension the chapter never touches: Greene's model organization for decentralized excellence is the German general staff, praised across several paragraphs for institutionalizing success, culminating in the 1940 blitzkrieg.1 The institution being admired is the command structure of Nazi Germany's army, and the chapter discusses its 1808–1945 run without a word about what it was doing in the back half of that period. This is the book's characteristic move — extract the mechanism, decline to price the context — and it's at its most conspicuous here.
Set this beside Strategy 5: The Command-and-Control Strategy, the immediately preceding chapter, which insists you never relinquish unity of command and keep every string in your own hands.
Read side by side they appear to contradict flatly. The reconciliation Greene never states: Strategy 5 governs who sets the objective — one person, always, no committees. Strategy 6 governs who decides how to reach it — whoever is closest to the situation. Unity of command is about direction; controlled chaos is about method.
The reason it matters that Greene leaves this implicit is that each chapter, applied alone, produces a recognizable organizational failure. Strategy 5 without Strategy 6 is the bottlenecked micromanager whose organization can't move faster than one person's attention. Strategy 6 without Strategy 5 is twelve autonomous teams with no shared direction, which is not agility but fragmentation. The book hands you both halves and trusts you to notice they're halves.
Business → Small Autonomous Teams and Their Real Precondition. The two-pizza team, the squad model, the autonomous pod — modern organizational design has independently rediscovered the corps system repeatedly, usually citing speed as the justification.
The insight the pairing produces: these implementations fail in a specific, predictable way, and Napoleon's case explains why. Companies copy the structure (small independent units) without the precondition (a philosophy deep enough that units act coherently without coordination). Napoleon's marshals had all fought his campaigns and absorbed his method; the German general staff spent decades indoctrinating officers before turning them loose. Autonomy granted to people who don't share a model of the goal doesn't produce a corps system. It produces Suvla Bay.
Psychology → Autonomy as a Motivational Substrate. Self-determination research identifies autonomy as one of a small number of basic psychological needs, and finds that perceived control over one's own work predicts intrinsic motivation more reliably than most external incentives.
The insight: Greene presents segmentation as an efficiency argument — smaller units move faster — and mentions almost in passing that their people are "more engaged, more motivated." That aside may be the larger effect. The corps system didn't just reduce message latency; it converted officers from executors into decision-makers, which changes how hard people work in a way no reduction in reporting overhead can account for.
The control you're holding onto is the specific thing making you slow, and you will not feel it as slowness. You'll feel it as diligence — as being the only person with the full picture — right up until an opponent who let go of that feeling moves three times while you're still deciding once.