John Boyd was, by the mid-1950s, the most respected flight instructor at Nellis Air Force Base — virtually unbeatable in practice dogfights, good enough to be asked to rewrite the manual on fighter-pilot tactics. He had developed a style designed to demoralize and terrorize, to get inside an opponent's head and disrupt his ability to react.1
None of it prepared him for the Pentagon, where he was assigned in 1966 to help design lightweight jet fighters and discovered a form of warfare he had no training for: bloodless backstabbing, political maneuvering, and indirect obstruction.1
Robert Greene uses what he built in response as Strategy 10's fifth method — the deliberately constructed frightening reputation — and it's the chapter's only case from an ordinary institution rather than a battlefield.1
Boyd found that Pentagon bureaucrats were more concerned with their careers than with national defense. They were less interested in developing the best new fighter than in satisfying contractors, often buying technological gear regardless of its suitability.1
His own design was a streamlined jet he believed could outperform any plane in the world. Contractors hated it because it was inexpensive — it didn't showcase the technology they were trying to sell. Meanwhile his Pentagon colleagues had their own pet projects competing for the same money, and did everything they could to sabotage or transform his design.1
Boyd's response was to treat the building the way he'd treated a dogfight, and to transfer his style of warfare into it directly.1
The first half of the method was appearance. Outwardly Boyd looked a little dumb — shabby suits, a nasty cigar, a wild look in his eye. He seemed to be just another emotional fighter pilot promoted too fast and too soon.1
Behind that, he mastered every detail. He made sure he knew more than his opponents: he could quote statistics, studies and engineering theory to support his project and to poke holes in theirs.1
The trap this set is the case's central move. Contractors would arrive with glossy presentations delivered by their top engineers, making fantastic claims to dazzle the generals. Boyd would listen politely and seem impressed — and then, suddenly and without warning, go on the offensive: deflating the optimistic claims, showing in detail that the numbers didn't add up, revealing the hype and the fakery. The more they protested, the more vicious he became, tearing the project to shreds piece by piece.1
Blindsided by a man they had grossly underestimated, they would leave vowing revenge. But what could they do? Their numbers were shot, their proposals were mush, and they had been caught in the act of overselling and lost all credibility.1
Soon they learned to avoid him — hoping he would fail on his own rather than trying to sabotage him.
Boyd's reputation did the daily work, but he also built two pieces of infrastructure that decided the outcomes.
A network of allies throughout the building. In 1974, with his team's design finished and apparently certain of approval, these allies told him a group of three-star generals planned his defeat — they would let him brief every official in the chain of command, all of whom would approve, and then scuttle the project at a final meeting, by which point it would look as though it had received a fair hearing.1
At least one powerful protector. Boyd always secured one, and Greene notes this was usually easy: in a political environment like the Pentagon there was always some senior figure disgusted with the system and happy to be a secret patron.1 He called on Secretary of Defense James Schlesinger and got personal approval for the project.
Then, at the meeting with the generals — whom he could tell were inwardly gloating that they finally had him — Boyd announced: "Gentlemen, I am authorized by the secretary of defense to inform you that this is not a decision brief. This briefing is for information purposes only." The project had already been approved.1
He then delivered the presentation, making it as long as possible. Greene's phrase: twisting the knife. He wanted them humiliated and wary of ever messing with him again.1
The other signature move was a trap built from bureaucratic incentives.
When a general gave him an order clearly designed to ruin his project, Boyd would smile, nod, and say: "Sir, I'll be happy to follow that order. But I want you to put it in writing."1
Generals preferred issuing commands verbally rather than on paper, as a way to cover themselves if things went badly. Caught off guard, the general would have to either drop the order or refuse the request — and a refusal, if publicized, would look terrible. Either way he was trapped.1
After several years of this, generals and their subordinates learned to avoid Boyd — his cigars, his verbal abuse, his knife-twisting — like the plague. The wide berth gave him room to push the F-15 and F-16 through an almost impossible process, leaving a permanent mark on the air force.1
Boyd understood early that fighting everyone would exhaust him and he would go down in flames. A strategist never hits strength against strength; he probes weaknesses — and a bureaucracy inevitably has them.1
The specific weakness he located: the people around him wanted to fit in and be liked. They were political, careful about their reputations, very busy, and had little time to waste.1
So the strategy was simple. Over years, establish a reputation for being difficult, even nasty — until getting involved with Boyd meant an ugly public fight that would sully your reputation, waste your time, and hurt you politically.
Greene's image: he transformed himself into a porcupine. No animal wants to take on a creature that can do so much damage, no matter how small it is; even tigers leave it alone. Being left alone gave him staying power — enough to survive long enough to see the aircraft through.1
And the general lesson, which is the chapter's most transferable claim: your own reputation may not be intimidating, because we all have to fit in, play politics, seem nice and accommodating. Most of the time that works fine. But in moments of danger it works against you — it says you can be pushed around, discouraged and obstructed. And if you have never been willing to fight back before, no threatening gesture you make will be credible.1
Enrichment added 2026-08-08. Greene brings Boyd back ten chapters later, in Strategy 20, for the idea he is actually known for — and this vault's page above, built from the deterrence chapter, does not carry it. The material arrives as a sidebar quotation from Robert Leonhard's The Art of Maneuver rather than in Greene's own voice, which is worth noting: he uses Boyd's concept without ever crediting it as the reason Boyd mattered.2
The origin was a puzzle from Korea. Boyd wanted to know why American fighter pilots consistently bested enemy pilots in dogfights.2
His analysis of the opposing aircraft produced a result that should have been the wrong way round:
Enemy fighters typically outperformed their American counterparts in speed, climb, and turning ability.2
The American advantage lay in two things that look minor and are not:
Which is to say: the Americans could see the tactical situation faster and change what they were doing faster. Not fly better — cycle faster.
The result was that the American pilots could more rapidly observe and orient to the tactical situation moment by moment. Then, having decided what to do next, they could quickly change maneuvers.2
That is the loop — observation, orientation, decision, action — and the point is what happens when it repeats:
If one views a dogfight as a series of Boyd cycles, one sees that the Americans would repeatedly gain a time advantage each cycle, until the enemy's actions become totally inappropriate to the changing situations.2
The mechanism is compounding rather than additive. A single cycle's advantage is trivial. Sustained across an engagement, the slower party ends up responding to a situation that has already been superseded — not outfought, but permanently late, acting on a world that no longer exists.
Hence, the American pilots were able to "out-Boyd cycle" the enemy, thus outmaneuvering him and finally shooting him down.2
And then the generalisation Boyd himself pursued for the rest of his career:
Colonel Boyd and others then began to question whether this pattern might be applicable to other forms of warfare as well.2
Why this belongs on the porcupine page. The two Boyds in this book look unrelated — a Pentagon obstructionist who made himself too costly to fight, and a theorist of decision speed — and they are the same operator. The porcupine strategy is a cycle-time attack on a bureaucracy: the deliberately extended briefing, the "put it in writing" trap, the willingness to make any engagement slow and expensive. Boyd could not out-resource three-star generals. He could make every engagement with him take longer than they could afford, which is the same insight as the dogfight, applied to an organisation rather than an aircraft.
Greene splits him across two chapters and never notices he is describing one idea twice. See Strategy 20: The Ripening-for-the-Sickle Strategy for the maneuver-warfare context, and Strategy 14: The Blitzkrieg Strategy — whose whole argument is attacking an opponent's processing loop — for the chapter that most needed this concept and does not name it. [POPULAR SOURCE]
Added 2026-08-08 from the Strategy 26 build — the third and final enrichment to this page, and the one that completes the picture. Greene returns to Boyd a third time, in the guerrilla-warfare chapter, and this is where the machinery under the porcupine finally appears.
The setup is the same one this page opens with, stated more bluntly: joining the Pentagon in the late 1960s to help develop jet fighters, Boyd faced a reactionary bureaucracy dominated by commercial interests rather than military ones.3
And Greene names why the obvious approach was never available:
a traditional bureaucratic war—an attempt to convince key staff directly and frontally of the importance of his cause—would have been a hopeless venture: Boyd would simply have been isolated and funneled out of the system.3
So he waged a guerrilla war instead, and the first move was organisational rather than reputational:
His first and most important step was to organize cells within the Pentagon. These cells were small and hard to detect, giving the reactionaries nothing to hit at when they realized they were in a war.3
The recruitment criterion is specific and worth keeping:
Boyd recruited his guerrillas from among those dissatisfied with the status quo, especially the young—young people are always more receptive to change, and they love this style of fighting.3
Then the dual function, which is the part that changes how the porcupine reads:
With his cells in place, Boyd had constant intelligence as to what was going on in the Pentagon and could anticipate the timing and content of the attacks on him. He could also use these cells to spread his influence through word of mouth, infiltrating ever deeper into the bureaucracy.3
Greene's general instruction from the case: avoid an organization's formal channels and tendency for bigness and concentration. Opt for mobility instead; make your army light and clandestine.3
This resolves something the porcupine account left unexplained. A reputation for being expensive to fight is a deterrent — it discourages engagement, but it cannot tell you when an engagement is coming, and a purely defensive posture in a bureaucracy eventually loses to patience. The cells supply exactly what the reputation cannot: early warning, and a propagation mechanism.
So the three Boyds in this book are one operator with a complete system. The OODA cycle is the theory. The porcupine is the defensive layer, making any direct attack cost more than it returns. The cells are the offensive and intelligence layer, telling him where the attacks would come from and carrying his ideas into places he was never invited. Greene distributes these across three chapters — deterrence, manoeuvre warfare, and guerrilla warfare — and at no point observes that he is describing one man's single integrated method three times.
The uncomfortable note the chapter does not sound: what is being described, admiringly, is a serving officer running a clandestine network inside a defence department to defeat his own chain of command on procurement policy. Greene's framing is that the cause was right and the formal channels were captured, which is very probably true here. It is also the justification every such network offers.
You're trying to get something through an organization that has no particular reason to stop you and a hundred small ways to make it never happen — reviews that don't conclude, requirements that appear late, approvals that require someone who's always busy.
Boyd's method has three parts and the order matters.
Know more than everyone in the room, specifically. The reputation only works because it's backed by the ability to dismantle a bad argument in detail. Difficult without competence is just difficult, and it gets routed around rather than avoided.
Make one public demonstration. Boyd's reputation was built on a small number of occasions where he visibly destroyed someone's case. You don't need many, and Greene is explicit that a few clear demonstrations suffice — but they have to be visible to people who weren't involved.
Secure a protector before you need one. Boyd's decisive win came from having Schlesinger's approval in hand before walking into the ambush. His allies told him the ambush was coming, which is the other half of the same infrastructure.
The cost is worth naming plainly, because Greene doesn't. Boyd got two aircraft built and was, by every account including this one, deeply unpleasant to work with for years. The strategy produced its stated result and it foreclosed a great deal else — nobody in that building came to him with an opportunity.
Boyd's Pentagon career, his role in the lightweight fighter program, his influence on the F-15 and F-16, and his later strategic thinking (the OODA loop, and his influence on Desert Storm planning) are well documented, principally in Robert Coram's biography. [POPULAR SOURCE] for Greene's framing.
Open tension: the account is told from Boyd's side and treats his opponents as uniformly careerist and contractor-captured. Some of them were. Some were presumably making defensible engineering and budgetary judgments that happened to conflict with his. A design that is cheap and streamlined is not automatically the right one, and the chapter's framing — Boyd correct, everyone else corrupt — is the version a partisan biography produces.
A second tension the chapter creates for itself: the porcupine strategy is presented as defensive deterrence, and the tactics described are largely offensive. Boyd didn't only repel attacks; he humiliated people pre-emptively, deliberately extended a presentation to twist the knife, and used the "put it in writing" trap to trap generals who had not yet acted against him. Greene's own Reversal warns against becoming intoxicated with the power fear brings and against using it as an offense of choice — and the case he selects to illustrate the method is a man who plainly crossed that line.
Set this beside Marshall and Remote Control from Strategy 5, and the contrast is the sharpest institutional pairing in the book so far.
Both men faced a dysfunctional War Department full of people protecting fiefdoms. Marshall's answer was to systematically replace the people, install protégés who thought as he did, and rule indirectly with a light touch that made him look like a delegator. Boyd's answer was to make himself so unpleasant to fight that nobody tried.
What the pairing produces: the strategies are available to different people. Marshall was Chief of Staff and could retire generals. Boyd was a major with no authority over anyone. The porcupine method is what's left when you cannot change the org chart — and Greene presents both admiringly without noting that one requires institutional power and the other is specifically the strategy of someone who has none.
That makes Boyd the more useful case for most readers, and the more costly one to run.
Psychology → Reputation as a Precommitment Device. Game-theoretic work on reputation treats it as a way of committing to future behavior that would otherwise be irrational in the moment — fighting an unprofitable battle now to make future battles unnecessary.
The insight the pairing produces: this explains why Boyd's early confrontations had to be disproportionate. Winning a fight economically teaches an observer that you'll fight when it's worth it. Winning viciously and at excessive length — the deliberately extended briefing — teaches them you'll fight when it isn't, which is the only signal that deters people whose calculation is about cost rather than about who's right.
Business → The Individual Contributor With No Formal Power. Every organization contains people who reliably get things done despite holding no authority, and their methods are usually described in terms of relationships and credibility.
The insight: Boyd's case adds the component that account leaves out. Relationships and credibility explain how he assembled allies and found a patron. They do not explain why the obstruction stopped — that came from making himself expensive to oppose. The full pattern for operating without authority appears to require both: a network that gives you information and cover, and a reputation that makes blocking you personally costly. Most people build only the first, and are then surprised that being well-liked and well-informed doesn't stop a determined obstructor.
Boyd's insight was that his opponents weren't trying to defeat him — they were trying to have an easy day. That reframes the entire problem: you don't need to be able to win against a bureaucracy, you need to be more trouble than the alternative to whichever individual is deciding whether to block you this week. Almost nobody in an organization is being paid enough to fight a porcupine.