Insight Editions · No. 211
Leadership Strategy and Tactics
Field Manual
Jocko Willink
Jocko Willink presents practical leadership principles and tactics for taking ownership, building teams, communicating clearly, and handling workplace and military challenges.
A study guide to Leadership Strategy and Tactics by Jocko Willink. Shared free for personal reading; not for sale and not endorsed by the authors or publishers. Please read and buy the original.
The Book in Brief
The argument in brief
- Fill the OJT gap. SEAL leadership was uneven on-the-job training; this book is the missing field companion under Extreme Ownership and Dichotomy.
- Foundations. Detach; kill arrogance; stay in your lane; Laws of Combat; relationships first; play the game; know when mutiny is in order; born and made; leadership is not manipulation; subordinate ego; tell the truth; study.
- Core Tenets. Be capable and ask for help; build trust down and up; earn influence; Extreme Ownership (including preemptive and when blamed); pick up brass; lead from the rear; do not overreact; do not care (about ego noise); everyone same/different; let nature work; manage isolation; know what matters.
- Principles. Most important member of the team; span of control; care with discipline; imposed discipline; pride; giving orders; no yes-men; the rare exception to "no bad teams."
- Becoming a Leader. Succeed as new; get chosen; handle not being chosen; imposter syndrome; insecurity; peer-to-leader transition; grudges; new sheriff; do not go Rambo.
- Leadership Skills. Step up without bunching up; do not take it personally; do not dig in; iterative decisions; Decentralized Command vs lazy designation; avoid Easy Button; judge reputations carefully; conform to influence; everything is good (but not that good).
- Maneuvers. Leadership-as-medicine (attitude, humility, confidence, development); lead peers; manage bad bosses; know when to micromanage; give credit up; defend the nearly indefensible; stress relief; punishment; quit tactics, not strategy.
- Communication. Inform the rear of the patrol; kill rumors; clear guidance; explain why; Thread of Why; tactful truth; balance praise; hope in hearts not plans; ultimatums; Reflect and Diminish; yell almost never; listen more; apologize; be approachable; set the example.
- Conclusion. All on you; not about you. Tools for the team, or they backfire.
Argument map: Foundations and tenets unlock Principles; Becoming and Skills ready the leader; Maneuvers and Communication are the employment layer; Conclusion binds ownership to selflessness.
Chapter map
| Ch | Title | In one line |
|---|---|---|
| 1 | Introduction: The Roots of Learning Leadership | OJT gap; why this field companion exists under EO and Dichotomy |
| 2 | Foundations | Detach, humility, relationships, play the game, mutiny limits, ego, truth, study |
| 3 | Core Tenets | Trust, Extreme Ownership, brass, rear, overreact, care, isolation, priorities |
| 4 | Principles | Most important member, span, discipline, pride, orders, yes-men, rare team exception |
| 5 | Becoming a Leader | New seat, selection, imposter, insecurity, transition, grudges, new sheriff, no Rambo |
| 6 | Leadership Skills | Vacuum, personal, dig-in, iterative decide, DC vs lazy, Easy Button, reputation, conform, good-not-great |
| 7 | Maneuvers | Leadership-as-medicine, peers, bad bosses, micromanage, credit, indefensible, stress, punish, quit |
| 8 | Communication | Inform, rumors, guidance, why, Thread of Why, tact, praise, hope, ultimatums, Reflect/Diminish, yell, listen, apologize, example |
| 9 | Conclusion: It Is All On You, But Not About You | Full ownership; zero self-serving use of the tools |
Reading paths
- New to the seat. Ch5 → Ch6 → Ch8 (Clear Guidance, Thread of Why) → Conclusion test.
- Hard people problem. Ch7 (leadership-as-medicine, peers, bosses) → Ch8 (tact, Reflect and Diminish, ultimatums).
- Strategic refresh. Ch2 Foundations → Ch3 Core Tenets → Ch4 Principles.
- Review. Synthesis frameworks + A closer look after a full pass.
Introduction: The Roots of Learning Leadership
OJT as the default SEAL leadership school
When Willink reported to SEAL Team One after BUD/S, there was no leadership course, no issued books, no curriculum. New SEALs were expected to learn the way SEALs always had: OJT, on-the-job training. A good mentor who invests time and walks you through real scenarios can work. Willink lists the conditions that make OJT succeed: a solid leader, willingness to invest, and a junior who pays attention.
He then lists the shortfalls that made OJT unreliable in the early 1990s:
- Not all leaders are good leaders. Peacetime SEAL Teams after Vietnam meant leaders were rarely combat-tested. The first Gulf War ground fight lasted about seventy-two hours; SEALs ran few operations. For roughly twenty years before that, most deployments were peacetime, often training partner militaries. A great leader and a bad leader often received the same assignments and advanced at similar rates.
- Not all leaders mentor. Even good ones can invest deeply in only a handful of people.
- Admin work crowds out coaching. Peacetime still generates enough paperwork that mentorship slides off the schedule.
- Juniors are distracted. New guys struggle to imagine they will one day lead a platoon, so they under-invest in watching how decisions get made.
Willink says he was lucky: great leaders invested in him, Vietnam SEALs told tactical stories that carried leadership lessons, and he later tested those lessons in combat, then codified and taught them to incoming SEALs.
From battlefield principles to a field companion
After retiring, Willink taught civilian leaders the same combat principles, then partnered with former teammate Leif Babin to found Echelon Front. They wrote Extreme Ownership and The Dichotomy of Leadership to state the principles in clear language with combat and business stories. Feedback was strong. Application still lagged: understanding a concept is easier than implementing it.
This book fills that gap. Willink's stack:
- Strategic foundations on which the principles sit
- Core tenets that comprise those principles
- Tactical skills, maneuvers, and communication techniques used to employ them
Caveats he states up front: scenes are from imperfect memory; quotes are approximations; some details are altered to protect identities or sensitive information. The book is designed as a reference, not only a cover-to-cover read: a field companion for leaders facing a live problem.
Why Willink focused on leadership early
He frames his own path as luck plus necessity. As a child he was average across athletic and academic measures: not the fastest, strongest, or smartest; no trophy shelf; uneven grades unless a class interested him. He still wanted to leave a mark. Because individual talent was limited, he learned to get more talented people to work together toward a shared task, forts in the woods, squirt-gun assaults, whatever the mission was. He did not call it leadership then; he called it making things happen.
A rebellious streak kept him outside the "normal" kids. Hardcore and heavy metal, different attitude. From the outside he observed cliques, emotions, and drama with detachment. Observation became a leadership habit.
Joining the navy was the most radical move available in his small New England town, where peers smoked pot, drank, listened to hippie music, or headed to college and trades. He pushed further: he tried for the SEAL Teams. In the late '80s and early '90s, SEALs were obscure. His recruiter had one bad copy of the film Be Someone Special. Machine guns, snipers, explosives, high-speed operations. He enlisted.
His father warned: "You are going to hate it… you don't like authority, and you don't like people telling you what to do." Willink answered that SEALs were a flat team that did not take orders. He calls that view naïve. He also believed SEALs had a 50 percent casualty rate and rarely reached twenty-year retirement. Looking back, he ties that myth to Naval Combat Demolition Units (NCDUs) at Normandy on D-day, not to peacetime SEALs in 1989. The myth made him more eager. He labels himself then: tough, but dumb.
Boot camp, BUD/S, and the blank slate
The navy gave him a blank slate. Grades, hometown, parents' jobs, athletic ranking: irrelevant. Shaved head, uniform, explicit standards: make the bed this way, fold underwear that way, polish boondockers until they look like mirrors. Follow the rules and you get put into leadership. He did, and became a squad leader in boot camp. Technically minor; personally formative. He had found a home.
BUD/S repeated the pattern. He was not the best runner, swimmer, or obstacle-course athlete. He could follow instructions, play the game, and refuse to quit. He rejects the claim that everyone thinks about quitting; he says he never did. Hell Week (about five days of nearly continuous physical training with almost no sleep, the largest quit driver) felt relatively relaxing because nothing was timed. Outside Hell Week, timed runs, swims, and obstacle evolutions put failures "on the bubble"; fail again and you are out. During Hell Week the job was simply not to quit.
At SEAL Team One, the master chief crushed residual pride: no one cared that they finished BUD/S; everyone there had. Prove yourselves for the trident through a six-month probationary period plus written and oral boards with senior enlisted. Theme that stuck: you never rest on past achievement; you always improve.
Early-'90s progression differed from today's. After boarding a team, you were assigned to a platoon where you actually learned the job. BUD/S taught cold, wet, tired, miserable, and not complaining. Platoon taught operator skills at fire-hose pace.
Where the book's roots sit
In his first three platoons, Willink absorbed concepts that became the base of what he later taught SEAL Teams and civilian organizations. He names the sequence of luck: right place, right teachers, right frame of mind; later experiences overlaid those lessons; a system formed, then was applied in the Battle of Ramadi in summer 2006. After that deployment he took over West Coast SEAL tactical training, formalized the lessons, and wrote them down. The roots, he insists, were nontraditional but effective: the SEAL platoon.
- Late 1980s / 1989: Enlists; SEAL myth and recruiter video
- 1991: Into the Teams; peacetime mode after brief Gulf War
- First three platoons: Detach, humility vs arrogance, when not to lead
- Summer 2006: Ramadi / Task Unit Bruiser stress-tests the system
- Post-deployment: Codifies Laws of Combat in West Coast training; later Echelon Front and the prior two books; this volume as implementation companion
Introduction claim chain: uneven platoon OJT → combat crystallization → formal training → civilian transfer → this field companion.
Foundations
A. First Platoon: Detach
Willink learns detachment on an offshore oil-platform assault training target. In the Persian Gulf, platforms could be seized for many reasons; SEALs had participated against Iranian-controlled rigs in the 1980s and trained to retake them. Commercial platforms hosted mock operations. The training value was high because platforms are complex and dangerous: many systems are highly flammable and under massive pressure, so live ammo and door charges on a real hit would demand real structural knowledge.
What makes a platform uniquely hard is geometry. It is a maze of stairwells, hallways, rooms, and equipment-packed open areas. Unlike most SEAL targets it is a true three-dimensional problem: many floors are heavy metal grating you can see through. Concealment is difficult; the enemy can see you from a great distance through the same floors.
As a new guy late in predeployment workup, Willink had already run land warfare, extensive CQB, urban, reconnaissance, and air/maritime blocks. Individual skills were ordinary (not best shot, not fastest reload, no combat-swimmer records). Tactical understanding felt stronger. He watched platoon leadership make calls and tried to understand why. Making calls himself still was not his place.
Then one clearance froze the platoon. The whole element entered a large deck packed with mechanical gear and hiding spots, a complex tactical problem. They stood side by side looking down weapon sights "like an old-fashioned skirmish line," scanning for threats and flammable or high-pressure hazards, waiting for direction.
He waited. Then waited longer. Peripheral vision: every man to left and right in the same posture. Still no call. Finally he elevated to high-port (muzzle safe, skyward), took a half step back off the firing line, and looked left and right. Clarity arrived at once. Everyone, including the platoon commander, platoon chief, assistant platoon commander, and leading petty officer, was sight-locked. Each man saw only his field of fire. From a few inches of physical distance and a mental step back, Willink saw the whole deck, its obstacles, and the simplest clearance path: clearer than more experienced teammates still glued to their optics.
He paused one more second to confirm no one else would move. No one did. He barked: "Hold left, move right!" Half expecting a shut-up for a new guy speaking. Instead, trained word-passing kicked in. The call repeated down the line and became action: left side held and covered; right side pushed and cleared the flank. Not a clever invention: standard cover-and-move rehearsed countless times. The cellar deck cleared; the platoon continued. No one objected. A more senior teammate later said it was a good call.
What: Oil-rig clearance; complex equipment deck; he detaches and calls "Hold left, move right."
When: Predeployment workup, platform training after prior tactical blocks.
Outcome: Deck clears via standard cover-and-move; senior affirms the call; detachment becomes a career habit.
The platoon reaction reinforced the habit. He practiced it in land warfare, CQB, and urban training. Getting caught in immediate detail still happened; awareness of the failure mode was the first win. Goal: never stay fully trapped in minuscule tactics; gain higher mental and physical altitude. More detachment made the tactical picture easier to read.
As rank rose (assistant platoon commander, platoon commander, task unit commander), detachment became a leadership foundation. He detached from the mission-planning grind so he would not drown in detail, could see the bigger picture, and could "come across as the tactical genius that had all the answers." Later he used the same move in ordinary conversation: read others' emotions and reactions; assess and manage his own.
- Be aware. Make it a goal not to be fully absorbed in minute details. Self-check to avoid tunnel vision.
- Read physiological indicators. Hard breathing, raised voice, clenched teeth, squeezed fists signal rising emotion and loss of altitude.
- Step back physically. Take a literal step back. Lift the chin to elevate vision and compel a look around.
- Cue the mind from the body. Deep breath and exhale. Scan methodically left to right and back. Relax, absorb, drop emotion, assess dispassionately, decide.
B. Second Platoon: Arrogance and Humility
Finish first deployment and you are no longer a new guy. You become a "one-cruise wonder": not new, still not expert, often convinced you might know everything. Willink's second platoon at SEAL Team One kept a bunch together and added other one-cruise wonders from other platoons.
The weak link was the platoon commander. He had laterally transferred from another navy specialty. As a senior lieutenant he outranked the room in grade but was inexperienced in SEAL workups and deployments. That alone is normal military design: green officers are supposed to be surrounded by senior enlisted who provide tactical guidance. Here the design failed. The commander would not listen to senior enlisted or to the troops. All plans were his plans; all decisions his decisions.
Subpar training-mission performance followed. Failures did not humble him. He blamed others and would not admit bad plans or bad field calls. Willink later reads the pattern as experience deficit filled by massive ego and zero humility. He credits the senior chief and LPO for sustained efforts to counsel, cajole, influence, and mentor; they spent extra time explaining how the Teams worked and tried to get him to let others make some tactical decisions. Months passed with no change.
One late night before an arduous desert training mission, the LPO disagreed with the plan and said so. Argument became a yelling match; the platoon commander snapped and took a swing at the LPO. The platoon separated them. Friendly scraps and light grappling exist in healthy SEAL platoons; this was different: not play, and worse, an officer striking enlisted.
A dark mood followed. Arrogance was bad enough; violence toward the LPO was unacceptable. Closed-door enlisted meetings with senior chief and LPO produced a plan: go to the commanding officer and say they did not want to work for this platoon commander. Willink names it: mutiny, in spirit. He quotes the stakes under the Uniform Code of Military Justice: a person found guilty of attempted mutiny, mutiny, sedition, or failure to report "shall be punished by death." He immediately grounds the drama: peacetime, zero chance of capital court-martial, still a serious act for enlisted sailors to ask that their officer be fired.
Back at the team, the senior chief briefed the command master chief, who got them a meeting with the commanding officer of Team One: down-to-earth, charismatic, rare reputation as a tactical operator for a senior officer. Enlisted men reported one by one, including the fight night and the general atmosphere. Willink's line: the commander does not listen; his way or the highway. After the last man spoke, the CO answered: situation may not be ideal; sounds like personality conflicts; also sounds like a mutiny; mutinies are not allowed; stop it; go back; get to work; figure it out. They said "Yes, sir" and complied out of respect.
The CO had squashed the rebellion. He also would not keep a bad platoon commander. Over the next days he consulted the command master chief, talked more with the platoon senior chief, assessed leadership shortfalls, called the platoon commander in, and relieved him of duties and removed him from Team One. Mechanism: command decision, not troop veto.
Delta Charlie (replacement): unmatched experience, calm humility, Decentralized Command, planning altitude, took out trash, first message was looking forward to working with them.
Delta Charlie arrives
The replacement went by initials in phonetic form: Delta Charlie. Reputation preceded him: enlisted rise to senior chief, then commission; assignments across old Underwater Demolition Team (before UDT decommission into SEAL Teams), plank owner at Richard Marcinko's SEAL Team, regular SEAL Team, Special Boat Team, BUD/S instructor, SEAL Delivery Vehicle Team (mini-subs); combat in the Grenada invasion in the element tasked with the country's main radio tower.
Willink expected stern correction of mutineers. Reality: about 5'7", roughly 165 pounds, lean, relaxed, usually a half smile. First address: "I'm looking forward to working with all of you." Not "leading you," "taking over," "running a tight ship," or even "honored to command." The word with marked the difference.
Experience predicted, in Willink's head, that Delta Charlie would dictate every plan. Instead he ran classic Decentralized Command: stated what needed doing, told juniors (not only senior enlisted) to figure out how and report back. "Hey, here is the mission for tonight. Figure out how you think we should do it and let me know." Nervous juniors poured four or five hours into maps and hole-poking, then briefed him; he quickly found remaining mistakes. He looked like a tactical genius. Willink later realized the mechanism: Delta Charlie was detached from the planning grind, so altitude made holes obvious.
Ownership flipped. Because the plan was theirs, buy-in was automatic; in the field they drove through obstacles. Under the old commander, imposed plans triggered ego resistance: when something broke, the silent script was "his plan is awful; mine would have been better," and effort sagged.
Delta Charlie also took out the trash and sometimes ran a broom at day's end. Platoon hut cleaning usually belongs to new guys; one-cruise wonders felt above it; distance from menial work seemed to grow with rank. Except him. Consolidate two or three cans, walk to the dumpster, under two minutes. Pure visible humility. After seeing it a couple of times, lower enlisted preempted the chore out of earned respect. The old commander had treated garbage as beneath him; juniors would not take out his. Humility, more than tactical gifts alone, made them refuse to let Delta Charlie look anything less than perfect to the CO. Willink calls it the best platoon he was ever in.
Life consequence: under the first commander the platoon's whole world was miserable; under Delta Charlie it was almost instantly good. Strongest display of leadership impact he had seen. The thought that started his officer path: one day make the world good for sixteen SEALs in a platoon. Core teaching: humility when you have every reason to elevate yourself is what makes people truly want to follow.
C. Third Platoon: Overstepping My Bounds
The core group stuck together again: trust, closeness, shared reps. After returning from the Delta Charlie deployment they received a new platoon commander: solid reputation, liked, aware of the oversized shoes, unwilling to imitate Delta Charlie, leading with his own strengths. By then lower enlisted could make a lot happen from prior teaching; the new commander accepted that.
Good workup, then peacetime deployment aboard a U.S. Navy ship: host-nation training or unilateral work when no counterparts were available. At one point they left the ship for unilateral land-warfare refreshers in a Persian Gulf desert, drilling immediate action drills (IADs). IADs are preplanned responses to enemy contact, analogous to football plays: flank, break contact, get on line, move forward/back/left/right. Calls usually come from platoon commander or platoon chief depending on enemy location.
Willink was radioman, toward the front just behind the platoon commander (who follows the point man). On "contact" (man-shaped silhouettes), everyone dropped into fields of fire. He scanned, then mentally detached and swiveled to assess. A small sand berm gave most of the platoon solid cover. Out of "danger" behind it, he saw a clean escape: peel behind the berm one man at a time.
He waited for the commander's call. None. Waited more. Still none. He shouted "Peel right!" Word passed; the basic maneuver ran smoothly. After a couple of hundred meters: hasty perimeter, 360-degree security, ammo redistribution, head count, cease-fire, ENDEX (end of exercise).
Debrief: commander frustrated. "What were you doing making that call?" Willink cited the maxim "In the absence of orders, lead!" Commander rejected the premise: there was no absence of orders; he had been assessing and wanted to assault through the enemy; Willink had spoken too soon. Not a huge scene, but clear unhappiness.
Easy path: get defensive ("someone had to"). Willink chose the other path. He owned a real though non-grievous mistake: he had overstepped, and the platoon had not executed the commander's intent. Positive residue for him: he did not always need to lead or sit at the center of decision-making. Supporting the team and mission meant supporting the boss. Across the rest of his SEAL career and later in business he watched the same failure mode as egos jockeyed over who was in charge instead of maneuvering against the enemy.
D. Laws of Combat and Principles of Leadership
Countless later lessons were tested when Willink led SEAL Team Three, Task Unit Bruiser in the Battle of Ramadi; those combat examples fill Extreme Ownership and The Dichotomy of Leadership. Principles were not fully crystallized until he took over West Coast SEAL collective tactical training. This is not individual skills school (sniping, trauma). It is platoons and task units hashing SOPs, integrating, learning to shoot, move, communicate, close with and destroy, and practice combat leadership.
Environments covered: rural desert/forest/mountain; urban cities and villages; close quarters in varied buildings; long ocean transits in small boats; subsurface on rebreather scuba; parachute and helicopter insert; vehicle formation fighting. End of each block: FTX (field training exercise) phase of full-mission profiles: plan, rehearse, insert, infiltrate, actions on the objective, exfil, extract, then intel analysis and follow-on planning. Typical FTX length: about five to seven days continuous. Sleep limited; planning cycles short; field stress maximized.
Realism stack the cadre built:
- Simunition paintball rounds, or a multimillion-dollar laser tag system mounted on real weapons, with sensor vests that announce wound type or kill and play snap/whiz/explosion effects
- OPFOR (opposing force): experienced SEAL trainers in enemy role, "without question" the toughest enemy those units will face
- Professional set design: façades, local construction materials, foreign-language signs and graffiti, assembled markets
- Ethnic civilian role-players who look, dress, and speak the part
- Pyrotechnics: explosions, smoke, fire, rockets, grenades, simulated IEDs
Through night vision, with detail, moving people, and explosions, trainees can slip into a wartime mind-set.
Days into the job, fresh from Ramadi, Willink watched a land-warfare FTX become "absolute disaster."
Planning failure. Target: one large building in a small valley surrounded by six smaller buildings. The unit split into six elements approaching from different directions. Isolation logic looked smart on paper; it minimized mutual support and communication. Ancient maxim ignored: keep things simple. Split multiplies confusion.
On target. Assault starts; some elements pinned. Distance prevents cover fire; movement without cover produces more casualties. Vietnam SEAL teaching reinforced across Willink's career: Cover and Move. If you move, someone covers: active shooting to keep heads down, or good position scanning as you move. He inventories the scale ladder:
- Two-man prisoner control: one on gun, one cuffs
- Danger crossing of road/river: extra security holds the open area
- Hallway movement: one or two muzzles cover down the length
- Rural fire teams: one moves while the other suppresses or scans
- Target assault: base of fire shifts ahead of the maneuver element
- Larger scale: aircraft overhead with sensors and ready fires
On this FTX, elements could not cover each other at all.
Priority failure. A larger element bogged down in the main building: paintball fire from multiple directions, wounded men, screaming civilians, incomplete head count, leader afraid to exit and leave someone. Willink watched him try to treat wounded, get accountability, control civilians, and locate shooters simultaneously. If he did not win or at least suppress the firefight first, none of the other problems would matter because they would be dead. He needed Prioritize and Execute.
Language failure. Orders were long, tangled, convoluted; in chaos nobody understood them. Simple applies to language, not only to scheme of maneuver.
Command failure. Everyone waited to be told what to do: platoon commanders on the task unit commander, squad leaders on platoon commanders, fire team leaders on squad leaders, individual operators on someone else. All direction from the most senior leader; all command centralized; freeze. Needed Decentralized Command: understand broad intent, then act.
Willink had OPFOR back off. The task unit was combat ineffective. More than half were "casualties." Carrying two- to three-hundred-pound bodies over steep rough terrain for four or five hours gave them time to think about failures, and gave him time to conclude the root cause was one thing: leadership. Far and away the most important thing he had to teach was how to lead: Vietnam-inherited lessons, Ramadi-crystallized, distilled for young platoon and task unit leaders.
That night at a chow-hall table he wrote what became the Laws of Combat:
- Cover and Move: Root of other tactics; synonym for teamwork. A unit alone is a fraction of a mutually supporting pair of units; coordination multiplies impact. Maintain supporting distance: distance coverable by fires, plus primary or at least secondary communications, so help can be called. Out of supporting distance, an element is "all but doomed." Highest priority law.
- Simple: After teamwork exists, set a simple, distinct, clear goal. Communicate plans and directives up and down in concise language everyone can comprehend under stress. If they cannot understand the goal or plan, they cannot execute.
- Prioritize and Execute: Multiple tasks and problems will stack. Doing all at once usually accomplishes nothing. Biggest or most impactful problem first; then the next; then the next.
- Decentralized Command: Comes alive only after the other laws. A task unit has about eight four- or five-man fire teams, each with a leader. Rhetorical test Willink put to commanders: what if every fire team leader clearly knew your intent and took initiative to realize it? Answer: the commander's job gets easier. Requires simply conveyed intent, junior confidence, and cultural empowerment, not one-time permission.
As units improved implementation across training blocks, task accomplishment rose; units that got sharp could defeat OPFOR "regardless of what the OPFOR did." Failures traced to failure to follow or implement one or more laws. Laws were solid and hard; mastery needed training and failures.
Two further components solidified while he commanded the training detachment:
- Extreme Ownership: mind-set of no excuses and no blame when problems occur; own them, find solutions, implement. Without ownership, problems never solve and teams never improve.
- Dichotomy of Leadership: opposing forces pull leaders in contradictory directions. Any trait can go too far. Talk too much (overwhelm) vs too little (uninformed troops); too aggressive (needless risk) vs not aggressive enough (no progress). Balance is mandatory; the dichotomy list is indefinite.
Watching platoon after platoon, he saw Ownership and Dichotomy as the cement holding the Laws together under arduous scenarios. Then he saw the same laws off the battlefield: jiu-jitsu mats, family life, coalition building, buy-in fights, ego and personality work. Equally hard to master in noncombat settings. More angles of observation improve comprehension and implementation.
| Law | FTX failure mode | Fix posture |
|---|---|---|
| Cover and Move | Six separated elements; no mutual support | Supporting distance + comms + overlapping fires/scans |
| Simple | Over-clever multi-axis scheme; convoluted orders | One clear goal; language the LCD can run under fire |
| Prioritize and Execute | Leader tried wounded, head count, civilians, shooters at once | Win/suppress the firefight first; then next problem |
| Decentralized Command | Every echelon waited for senior direction | Intent known; juniors empowered to act |
Laws of Combat stack: teamwork and simplicity enable priority and junior-led action; Extreme Ownership and Dichotomy bind the stack under stress.
E. The Power of Relationships
Another key element of exceptional teams: relationships. Leadership requires relationships with people above, below, and beside you. Better relationships produce more open, effective communication; more communication produces a stronger team.
Example problem: boss driving a less-than-ideal path. With relationship capital, you can tactfully show errors. Approach matters. Put the onus on yourself. Sample script: you want to support the plan to the best of your ability, but you are having a hard time understanding how to execute this part; can the boss explain why so you can do it right? Conversation opens; you can learn the real why and begin to influence.
Three filters before you spend capital challenging upward:
- Gain check. How much is actually gained if the boss changes? If minimal, do not invest time or effort.
- Ego check. How much of your concern is ego dressing up as "smarter" or "more efficient"? If little real gain, let it go; do not create drama for pride.
- Relationship vector. Will raising this move the relationship with the boss forward or backward? You build the relationship so the boss trusts and listens when mission requires it, not to garner personal favor. Choose battles carefully.
Building upward trust sounds obvious and is often skipped: performance. Complete what the boss expects. On time, on budget, low drama. Including things you are not 100 percent aligned with. Willink's career pattern: extra paperwork, cover a shift, clean an admin mess, execute a nasty low-reward mission. Be the solution. No complaint, no dumping bad jobs on others, no hunt for praise. Head down, work. Trust rises; clout rises. Opposite archetype: the constant objector who always has a better way; every objection sounds like another excuse. "The more you talk, the less people listen." When the high-performer finally objects, the boss hears facts worth considering.
Downward problem: if you see flaws in the boss's plan, your subordinates see them too. Preserve respect by telling them the truth. Sample framing: there may be better ways to skin the cat; changing the plan may cost as much as just doing the job; so we execute hard; and by crushing these tasks we build trust that earns listening rights later when something truly does not make sense. Dichotomy: if pure nonsense comes down and you never push back, the team reads you as a pushover, and upward you become a useless yes-man. Good bosses should hear critique; clout makes that survivable. Ultimately: one of the most powerful tools is a good relationship with your boss; solid relationships up and down are the basis of all good leadership.
- Deposit: low-drama execution of tasked work, including imperfect non-catastrophic orders
- Balance: boss trusts you to make things happen; team hears honest framing of why you are executing
- Withdraw: rare, high-stakes objections delivered with facts, tact, and self-onus framing
- Guardrail: never become a pure yes-man; silence on true nonsense spends downward trust
F. Play the Game
"Play the game" means play the long game. Willink knows his brand makes readers hungry for blunt-force counsel: victory by trauma; battle-axe through politics. That hyperaggressive posture is simple and feels fail-proof. Often it works briefly: a day, a week, maybe months; a few projects forced through by ruthless offense. Then relationships are trashed, bridges burned, earth scorched, and you look up with nothing left.
Do not do that. Playing the game upward: support the boss, perform at best ability, build trust. Purpose is not promotion or easier tasking; purpose is mission accomplishment with the resources and space trust buys. Playing the game downward: when subordinates object, listen, ask for alternatives, and say yes to decent alternatives even when slightly less efficient than your method. That stores downward trust so that when you must say no, they do not conclude you never listen; they take the explanation and commit.
He worked for every type: inspirational hands-off leaders with tactical prowess; micromanaging egomaniacs without common sense; paranoid, risk-averse overthinkers. Goal always the same: relationship so they trusted him, gave what the job needed, got out of the way, and let him accomplish the mission. Building that was never easy. It meant suboptimal tasks and swallowed pride.
People who treat playing the game as weak hypocrisy or sycophancy are wrong in his framing. You are optimizing so the team can win, building influence to move things in the right direction, not hunting personal gain. Dichotomy: you can go too far into brownnosing and calling every boss idea perfect. Do not. Be professional, courteous, and genuinely interested in why the boss wants a method. The script "I want to understand why so I can fully support your plan" is not only a relationship trick; the goal is actual understanding. Collateral benefit: relationship capital. Executing a small non-best method is not hypocrisy; it is storing capital for when it matters. If you are asked to do something you truly do not believe in, or that you know will catastrophe the mission and team, duty is to say no. Those cases should be few and far between. Until then, play the game and build relationships.
G. When Is Mutiny in Order?
As important as relationships are, there are times a boss must be disobeyed. Absolute last resort. Costs: massive disruption, setback, jeopardized or failed mission, possible total team disintegration.
Hard refusal triggers: illegal, immoral, or unethical orders. Inexcusable to do wrong because ordered. If unaware in the moment or unavoidable then, report up as soon as possible so illegality stops. Also consider disobedience when the path means catastrophic failure. Willink invokes Napoleon: if a subordinate leader executes a mission he knows is wrong, the subordinate is culpable.
Few situations are that clear-cut. Refusal is almost impossible to unwind. Many steps exist before that final measure.
Escalation ladder:
- Ask the boss to restate the purpose of the mission. Assess that statement; explain frontline concerns the boss may not see from altitude. Passing that information is the subordinate's responsibility.
- Good outcome A: boss reveals a detail or constraint you lacked; you now understand and can brief your team.
- Good outcome B: your concerns surface a detail the boss missed; ideally you also present a mitigating alternate course of action; boss adjusts.
- If the boss still commands forward: redouble tactful explanation. Return to the drawing board for any way to implement the boss's plan without wrecking mission or team. Smaller adjustments that still support the boss's intent may be enough if residual risk is acceptable. If not, capture detailed potential outcomes and present a logical, unemotional case.
- Delivery rules. Never lead with "this makes no sense," "this plan is ridiculous," or "why would we ever do this?" Two failures: emotional arguments get discounted; attacking the plan attacks the boss and triggers dig-in. Prefer indirect, fault-on-self framing: "I want to make sure I understand your thinking so I can learn to think through these issues myself"; "It's hard for me to understand this clearly since I don't have the experience you do."
- Ego on-ramp. Give the boss an easy way to own a better idea. Do not present your option as the only option. Tie alternatives to something the boss already said, however briefly: "I was thinking about one comment you made, and it made me think that maybe we could…" People like their own ideas better than anyone else's. Do not pit my-plan versus your-plan.
- If still ordered forward: assess even more granularly, mitigate further, document a stronger case, present again. Hope: boss either explains alleviating details or recognizes shortfalls and adjusts.
When the boss still will not move: weigh whether a hard stand is due. Efficiency loss alone is not worth the fight. More substantial but non-major efficiency loss: still usually not. Significant risk: go back again with precision. Only when you are sure the outcome is completely unacceptable do you reach the mutiny gate. Even then, model outcomes of refusal:
| If you refuse / quit | Likely result |
|---|---|
| Boss recognizes severity (you risk career and punishment) and changes plan | Best case; then fully rejoin and support the new plan |
| Boss digs in, fires you, installs a handpicked yes-man | Team loses the voice of reason; probable when ego already refused input |
| You draw a line or quit in protest | Loud clear statement, then zero remaining influence on outcome |
| You register final concern, then lead execution as well as possible while mitigating harm and logging results | Keeps long-game relationship and mitigation power; Napoleon problem remains: you are still culpable for outcome |
Whatever course you pick when pushing back hard, consider carefully. Some branches are catastrophic for team, mission, and subordinate. Proceed with caution.
- Illegal / immoral / unethical? → refuse and report
- Catastrophic to mission/team after repeated, documented, tactful pushback with alternates? → consider hard stand
- Mere inefficiency or ego bruise? → play the game
- Before the stand: restated purpose, alternate COA, detailed risk, indirect delivery, ego on-ramp for boss
- After modeling outcomes: refusal, mitigated execution, or exit, with eyes open to yes-man replacement risk
H. Born or Made?
Age-old question. Willink's answer: both.
Physical layer. People are born with different height, strength, flexibility, fast-twitch versus slow-twitch bias. Training improves capability (weights, running, stretching) but DNA eventually confines. Sports make the ceiling visible.
Cognitive layer. Training maximizes intellectual capability; limits remain. No amount of study turns average intelligence into Einstein. Still: reading improves contextualization; language study grows vocabulary; practiced questioning and problem-solving improve thinking up to genomic limits.
Leadership-native traits he lists as unevenly distributed at birth:
- Articulate simple, clear communication
- Ability to break complex problems into simple concepts (needed both to brief the team and to find a simple solution inside complexity)
- Confidence and charisma (hard to quantify; some have magnetism, others struggle for attention)
- Being loud enough to be heard (if the team cannot hear direction, they cannot execute)
- Ability to read people (many are socially awkward and miss emotion and reaction)
All leaders have strengths and weaknesses. Improvement paths he names:
- Become more articulate: practice speaking, expand vocabulary, read and write to clarify thought
- Simplify better: detach, think abstractly, make simplification the goal, reprioritize or remove the unimportant
- Grow charisma at the margin: posture, countenance, experience-fed confidence, eye contact, intent listening, clear speech with humble authority, projected voice
- Read people better: attend to body language, facial expression, tone; learn baselines; notice deviations that signal mood
Unrealistic to expect a leap from low to exceptional in every category, as unrealistic as turning a world-champion marathoner into an Olympic weightlifter.
If native traits are thin: build a counterbalancing team. Case from SEAL tactical training: a task unit commander over two platoons who was smart, tactically savvy, respected, and had "the vocal cords of a mouse." Combat leaders must be heard through machine-gun noise. Radios with noise-canceling headsets do not reliably solve it; in gunfight chaos people often cannot hear or attend to radios; commands vanish. Verbal commands are different. From day one of basic SEAL training, the drill is: stop shooting when a command is yelled, look at the caller, repeat the command back, look to the next person opposite, pass the word, wait for them to yell it back. That chain does not happen the same way on the radio; that is why radio direction is so often lost.
Willink counseled bluntly: men cannot hear you; get louder; weak voice is rendering you ineffective. No improvement next exercise; team lagged. Addressed again; still no improvement. He began to doubt the officer could be an effective SEAL leader, reflecting on how his own naturally loud voice had pierced gunfire and explosions. He pushed again: tactics, planning, and decisions were good; none of it mattered if unheard; get louder or you will not make it. The officer was disappointed, not angry; he seemed to recognize the shortfall.
Next mission: chaos of belt-fed blanks, simulated artillery, explosions. A strongpoint call was obvious (enter, clear a building, set security). Willink watched the quiet commander. Instead of straining alone, he told "Bill," the loudest bigmouth in the task unit: tell everyone to strongpoint that building and set security. Bill thundered it. Word passed as trained; the unit executed. Awesome to watch. Proved verbal commands worked. Also proved Willink wrong: the officer was capable of leading in combat; he needed to use people to cover his weakness.
That is what good leaders do: recruit and use teammates who compensate for shortfalls. Combine compensation with hard work on weaknesses and almost anyone can drastically improve. Exception: a person who lacks humility. Without humility they will not acknowledge weakness, will not improve, will not staff against gaps. They never get better. Beware. You may not transform awful into excellent, but you can make bad better and good outstanding regardless of how they were born.
What: Repeated unheard orders in live training noise; finally relays "strongpoint" through Bill.
Outcome: Maneuver executes; lesson is team compensation beats waiting for a genetic loud voice; Willink revises his assessment of the officer's potential.
I. Leadership and Manipulation
Leadership and manipulation are closely related and morally opposed in reputation. Shared aim: get people to do what you want them to do. Highest form of both: get them to do it because they want to.
Shared technique set: build relationships, leverage influence, maneuver politically, capitalize on others' egos, personal agendas, strengths, and weaknesses to reach a preferred outcome.
Glare difference: manipulators aim at outcomes that benefit the manipulator (promotion, better position, looking good to the boss). The manipulator's ultimate priority in every move is the manipulator. Leaders put themselves at the bottom of the priority list; good of mission and team outweigh personal concern.
Both attitudes eventually shine through. Manipulators may fool some people some of the time; they will not fool all people all the time. True leaders may not always get immediate credit because they deflect it; over time they are recognized, admired, and likely promoted. Short-term manipulator wins happen when someone plays a good hand and gets noticed. Sacrificing others for self does not pan out long term; people notice and stop following. Good leaders do the right things for the right reasons: work hard, support the team, lead solid execution. In the long run, true-leader reputation outweighs glory-seeking; looking out for mission and team wins.
Leader: same influence tools aimed at mission and people; may receive less immediate credit; long-run trust and followership compound.
J. Subordinate Your Ego
At Echelon Front, Willink and Leif Babin assessed a fast-growing, highly profitable company that needed junior leaders trained ahead of growth. Day one with senior executives impressed him: smart COO; central-casting detail-oriented CFO; solid CTO, HR lead, and other seniors.
Then the CEO. On paper: NCAA college athlete, Ivy League MBA, not yet mid-thirties, already running a hundred-million-dollar company. Physically: at least 6'5", about 250 pounds of muscle. Handshake read: massive ego, "I'm better than you," teenage-tough chest. Smug tension, looking down his nose. Willink had handled big egos in military and corporate life; he filed it as manageable.
It was not. Every comment haughty; anything Willink said met with "I already knew that." Conceit did not thaw across the day. Day two with midlevel managers and frontline leaders, Willink quietly dug for dirt on the prideful CEO. None came; most said they liked and respected him. Willink's private conclusion: he has them fooled. Afterward he softened: maybe a bad day, missed deadline, seeping anger. He prided himself on getting along with anyone; next visit would be better.
Wrong. Return for leadership training: seniors happy; CEO still radiating conceited self-importance in the handshake. During Willink's first session the CEO performed disinterest: phone, whispers, walking out as if more important. While Babin took the second session, Willink sat boiling: how is this egomaniacal jerk blind to his arrogance? How do fellow executives and frontline leaders not see what he sees?
Then the bolt: is the problem me? Could his own fragile self-image be threatened by a physically gifted, smart, bold thirty-two-year-old running a hundred-million-dollar company? Were two massive egos creating the friction?
At the break he asked the CEO outside. The CEO smirked: "Sure… you gonna give me some coaching?" contempt on the word. In the hallway the CEO looked ready for a fight. Instead of confronting arrogance, Willink subordinated his own status: leaders are solid; morale is great; mission is understood; most impressive is you; smart, presence, vision understood; company greatness reflects outstanding leadership; respect for the athletic, academic, and company-building record.
Face change: arrogance to almost bashful. CEO blurted respect back (SEAL life, ranks, combat leadership). Both laughed; tension vanished; relationship flipped in seconds. Back in the room the CEO engaged and even chimed in with supporting experience. Mechanism, as Willink reads it: detach, recognize ego clash, humble yourself briefly, problem solves. Metaphor: ego is reactive armor; the harder you push, the harder it pushes back. Opposite move disarmed it.
Fear that subordinating ego gets you trampled is usually wrong in his account: subordinating ego is ultimate self-confidence and earns respect. Initial feeling may be that you backed down; actually you showed strength to give credit, and the other person recognizes that confidence consciously or not. If you cannot put ego in check because you fear looking weak, you are weak. Subordinate your ego, build relationships, win the long game.
K. Leaders Tell the Truth
Truth and honesty are among the most essential leadership qualities. Tell the truth to your people, your boss, your peers, and yourself. Truth is not a license to be a jerk or to attack. Tact and sensitivity still bind.
Easy truths get told: we are winning; you are doing an amazing job; competitors do not stand a chance. Hard truths hurt to say and hear: we are losing; your performance is substandard; the enemy is gaining ground. That is why so many people, especially leaders, fail to deliver them. Leaders must speak them anyway.
Preconditions. Know your people and communicate often, so bad news is not the first contact in months. Delivering bad news should not be the one visit to the front lines in four months. Consistent relationship makes negative news survivable and also lets subordinates deliver bad news up the chain. Communicate across forms: meetings, phone, email, text, video, whatever is available. Frequency makes bad news sting less.
Market-share cascade (teaching scenario, not a cited dataset): company loses 5% share in a month; CEO hides it hoping to recover. If they recover, fine. If they lose another 5% (10% total), explanation gets harder; some bosses hide again. Cross fingers another month. If recovery never comes, leadership can look up in three months, six months, or a year at 50% share gone, then forced cuts to marketing, training, and personnel. Early truth, framed positively, could have let frontline leaders redouble effort and recover. Hidden truth also leaks: someone in accounting tells operations or sales; rumor fills the information void with worse-than-reality stories; gossip and groupthink become a self-fulfilling doom prophecy. Why would the boss hide unless it was total disaster? Countermeasure: kill rumors by telling the truth.
Worst product of untruth: the team stops trusting the leader's words, plan, and vision; then team and leader fail.
When you cannot tell everything. Military compartmented classification; civilian legal constraints. Answer still: tell the truth, specifically the truth about why the full truth cannot be told. Scripts: "that is classified and compartmentalized information I am not allowed to discuss"; "due to the legal situation, I cannot disclose it right now."
Truth also binds Extreme Ownership: what happened, what went wrong, what mistakes you made, how you will fix them. Truth is still not an excuse for needless harshness. Mitigate by knowing who people are, what they stand for, what drives them; without that knowledge you cannot communicate critique well.
Harsh team truths: deliver them; explain circumstances; no excuses; no holding back; explain why. Terminations: explain necessity for the good of the team. Unwanted extra hours: explain importance. Then lead from the front when things are bad: you take the pay cut; you take the first overtime shift. Do not leave the hard things to the troops.
With individuals: do not wait on hard conversations with subordinates, superiors, peers, or clients; delay does not soften the issue. Attack it. Even with relationship, most people dislike criticism; deliver indirectly with the minimal negativity needed to get change. Willink rejects the mechanical praise sandwich ("hit numbers three months… but churn is bad… offset by performance while here") as a shortcut around actual relationships. If the relationship is real, you should not need manufactured positive buns around the critical meat. He points forward to later criticism tactics in the tactics half of the book.
L. Study
Leaders are never good enough. In any leadership job, new unexpected challenges keep arriving; headcount grows; projects multiply; strategic impact expands. Leadership in a chosen profession is a profession. Being a leader is your life. Do everything humanly possible to know your field and to know how to lead in it. Strive every day to learn and become better.
Learning components:
- Leadership lens on every group. Leadership is occurring in any group of people. Pay attention. Note successful and unsuccessful techniques: how leaders talk, words they use, interactions they run. Think about application.
- Leadership lens on reading. Almost every story embeds leadership; a book or article need not be "about leadership" to be about leadership. How does the leader act and speak? How do superiors and subordinates react? History through books is experience without living it, but only if you read with enough engagement to catch actions, emotions, and human nature inside the words.
- Small things. People overlook nuances and then wonder why events unfolded as they did. Little things matter less than big ones; they still matter.
- Principle overlay. Map what you see onto Cover and Move, Simple, Prioritize and Execute, Decentralized Command, Extreme Ownership, and the Dichotomy of Leadership. If you look for them you will see them; seeing improves understanding; understanding improves implementation; implementation improves further looking. The cycle does not end.
None of this runs without humility. A leader who thinks they have reached the pinnacle is already going the wrong direction, stagnant in skill, and unconsciously giving off arrogance. Do not let that happen. Stay humble, and always learn.
- Watch live leadership with intent
- Read history and stories for leader behavior, emotion, and human nature
- Notice small frictions and cues others skip
- Map events onto the Laws + Ownership + Dichotomy
- Implement, then re-observe
- Reset ego so the loop does not stop
Foundations map: platoon origin stories feed the Laws; relationship and character disciplines keep the Laws usable.
Core Tenets
A. Be Capable and Ask for Help
A leader must know and understand the jobs, skills, and equipment of the people below him, without being an expert in all of them, which is impossible. A platoon commander shoots worse than his snipers, knows the radios less well than his radioman, and knows routes less well than his point man. A construction foreman cannot lay block like a mason or tie rebar like an ironworker; a plant manager cannot run every machine. All of them must still be familiar with what happens beneath them.
When a leader does not understand a skill the mission depends on, the answer is simple: ask to learn the skill and actually do it, rather than settling for an explanation. Sight in the sniper rifle, program the radio, lay some block, run the equipment.
- Ego is the obstacle. Leaders avoid this because they fear looking stupid and losing respect. The opposite happens. Troops do not respect a leader who pretends to know everything. As a junior SEAL, Willink was impressed by bosses who showed interest, more impressed when they asked for his perspective, and completely impressed when they tried to program a radio, fire an advanced weapon, or build a demolition charge themselves. Learning frontline skills also shows humility and that you know the job is hard.
- Not an excuse for ignorance. Not needing to perform frontline tasks does not license being unprepared. Read the manuals; know what the equipment is and what it is for. Not knowing how to run a piece of gear is understandable; not knowing what it is is inexcusable and makes you look out of touch. If caught unprepared, step away, learn, and come back.
- Keep going back. Doing it once is not enough. Willink told the CEO of an equipment manufacturer to build a product from beginning to end at least once a month, so he understood the workers' challenges and could spot anyone trying to "pull the wool over his eyes." That knowledge is "worth its weight in gold."
- Relationships and information. Time in the dirt builds relationships, and frontline troops with a relationship tell you what is really working and what is not. You cannot live on the front line; balance it, but spend enough time there to earn respect as a leader and as a person.
B. Building Trust and Relationships
The chain of logic is short: trust makes relationships, relationships make teams; without relationships there is only "a group of random people." Honesty is the foundation (see "Leaders Tell the Truth"), but other tools build trust in each direction.
i. Down the Chain
To build trust down the chain, you have to give trust. Let subordinates run a mission, make a decision, or work a problem without oversight. The risk is failure, so trust is built in small, incremental steps.
Willink's incremental trust loop: each success, or each failure turned into teaching, earns a slightly bigger task until the leader can step fully back.
- Start small. The first mission is a simple training operation, not a real-world operation with strategic consequences; the first decision is one where a wrong call causes little trouble; the first problem is one easy to recover from.
- Success compounds both ways. The leader's trust grows, and so does the subordinate's: trust that the guidance is good, that he will not be micromanaged, that he can figure things out.
- Failure is a teaching moment. No hammer of punishment, no berating or belittling. Teach, counsel, mentor, then give another task, perhaps with a little more guidance, and resume the climb.
- Oversight scales with risk. As stakes rise, mistakes still happen. Keep letting them lead, but micromanage a little: small course corrections to prevent catastrophic or unacceptable loss, which they still learn from.
- The end state. What starts as micromanagement becomes more and more hands-off until full trust is reached.
ii. Up the Chain
Upward trust also begins with truth. The common error is telling bosses what they want to hear: "Morale is great," "We will definitely make our sales numbers," "We have all the support we need." It feels good short term, then hurts the mission, the team, and the boss, who remembers who fed him the bad information.
- Truth is not complaining. "The team has worked hard and a break would be nice" is not worth the boss's time. "The team is so fatigued they need rest before they make a significant mistake" is. Distinguish what the boss needs to know from complaints about every little thing.
- Add performance and tactful pushback, as covered in Foundations. Without trust, leadership falls apart.
iii. Trust and Decentralized Command
Trust matters most under Decentralized Command, because in dynamic situations the only thing holding the chain together may be trust. Willink normally teaches the opposite of barking orders: explain the why so people can own the task and adjust; encourage questions and pushback, since the leader lacks the frontline view and open dialogue yields the best plan. But some moments allow no discussion.
C. Earning Influence and Respect
Rank carries some inherent respect and influence: subordinates assume a superior's training and experience mean good decisions. That platform is extremely limited. To build beyond it, give respect and influence to get them.
- Giving respect means: let people give their opinion; listen; do not interrupt; do not disparage their job or position; share the burden of hard tasks.
- Giving influence means: actually listen, consider their recommendations, incorporate their ideas whenever possible, and keep an open mind.
- The return. The more you respect people and let them influence you, the more respect and influence you gain over them.
D. Extreme Ownership of Everything
Extreme Ownership, the first chapter of Willink's first book, means the leader is responsible for everything. The idea is simple to state and hard to absorb, because subordinates sometimes do things the boss feels he could not have controlled.
The pig gunner
Willink's teaching example is the SEAL machine gunner. His belt-fed weapon fires over seven hundred rounds per minute and supplies the main cover in Cover and Move. He must carry, maintain, load, and fire it, pick positions, read terrain for himself and the enemy, and respect his field of fire, the sector he owns. Staying inside it keeps him from hitting civilians, friendly forces, or his own SEALs. The job needs little leadership, sits inside a four-to-six-man fire team, and usually goes to big, strong new guys. The gun is "the pig," the gunner a "pig gunner," and the running SEAL joke is that pig gunners are not the sharpest tools; a new guy who does something dumb "will make a good pig gunner." That makes him the easiest target for blame.
In Willink's training (Hollywood set designers, role-players, paint rounds, the laser system), "the ultimate leadership laboratory," young leaders routinely blamed gunners who fired outside their field of fire. "Whose fault is that?" "He pulled the trigger." "Actually, it is your fault."
- Not trained properly? The leader trains the gunner.
- Not briefed on his field of fire? The leader briefs him.
- Simply incompetent? The leader must spot it and then train him, move him to a job he can do, or, as a last resort, fire him.
Whatever the reason, it is the leader's fault. Willink even felt this when a SEAL drank too much in town and got into a fight: where did I fail to make him see the consequences, and why did I not see trouble coming?
i. Preemptive Ownership
A leader who knows he cannot blame anyone practices preemptive ownership: owning things before they go wrong. He trains the gunner and confirms he understands the plan; he layers weather contingencies. Willink's point: the highest form of Extreme Ownership takes place preemptively, before the mistakes occur.
ii. Taking Ownership When Being Blamed
People ask how to take ownership while others are blaming them. Willink's answer: that is the whole point. Say "Yes! Everything is my fault. I am the leader... and here is what I am going to do to fix it," then move straight to problem solving, or say you are working on a solution. It is hard because accepting blame hurts the ego, and having a finger pointed at you hurts more and triggers defensiveness in everyone.
The harder case is a subordinate blamed for something "not really my fault." Willink's scenario: a four-man fire team (leader, machine gunner, grenadier, and you, a rifleman next to the gunner). The gunner fires outside his sector, endangering friendlies. The leader asks, "Why did you let the machine gunner shoot outside his field of fire?"
| Response A: deflect | Response B: own | |
|---|---|---|
| What you say | "The machine gunner is responsible for his field of fire, not me. You should go tighten him up." | "I'm sorry, boss. While I knew my own field of fire, I should have confirmed that the machine gunner knew his. It would only have taken me a second or two... It was my fault, and I won't let it happen again." |
| How you read the question | An unfair charge against a "simple rifleman" | A compliment: the leader expects you to help lead others |
| Leader's reaction | A disappointed look; he walks away | "Perfect... I need you to step up and lead. I can't be everywhere all the time." |
| Which person a leader wants | The one who evades blame | The one who owns even others' mistakes |
E. Picking Up Brass
Leaders outrank subordinates but are not superior to them, so no job is too small or menial for a leader. After a block of training, SEALs must pick up hundreds of thousands, if not millions, of brass casings across ranges covering dozens of square miles: valuable, recyclable, and required for range cleanliness. It takes a couple of days on hands and knees in desert heat and demands no skill or leadership.
Leaders always have meetings, admin, and planning to fall back on. Willink always picked up brass with his troops. It showed no job was beneath him, let him interact and bond with frontline SEALs and junior leaders, let him watch how everyone interacted, and revealed who was slacking. Leaders who skipped it got another meeting or more sleep but no relationships, no observation, and no proof of humility.
- Balance. A leader should not always be in the trenches; meetings, admin, and planning are real work. But when a job is especially taxing, get in the dirt.
- Share risk and discomfort. If the team faces harm regularly, the leader must sometimes face it too. Periodically do the hardest, most uncomfortable work yourself: repairing power lines in freezing cold, pouring concrete in extreme heat, patrolling a bad neighbourhood, enduring the rejection of cold calling. You never forget to respect the job and the people doing it, and they see you shoulder the burden.
F. Leading from the Rear
"Lead from the front!" is common advice, and often right.
- Breaking fear. Open ground to cross, a sniper waiting, a room full of enemy behind a door: people freeze, and inaction makes it worse. When nobody else has the courage, the leader charges, maneuvers, or breaches. Otherwise the enemy seizes the initiative and wins. The same applies to any situation stalled by fear.
- Arduous tasks. People procrastinate on suffering; when the leader starts attacking the job, others join.
- Setting the example. Respect, mutual care, and constant professionalism, modeled from the front.
But there are times to lead from the rear or the middle:
- Risk. A leader killed or incapacitated can be catastrophic; be judicious about when to take risk.
- Lost altitude. At the front, the leader gets bogged down in the immediate fight and cannot see beyond it. In business, the leader buried in daily minutiae loses sight of broader events and decision-making collapses.
- In IADs. Young leaders should not stay at the front engaging; after the first volley and the call, move to covered ground to assess and make the next call.
- In planning. Lead from the rear: let the team build the plan so it is theirs and needs no selling. Step in only if planning bogs down or the team cannot agree. The best ideas come from those closest to the problem: "They have the knowledge. Give them the power."
| When to lead from the front | When to lead from the rear |
|---|---|
| The team is frozen by fear and someone must act | The front would bury you in the immediate tactical problem |
| A miserable task needs someone to start it | Your loss would be catastrophic to the team |
| Setting the standard of respect and professionalism | Supporting assets, reinforcements, and the next move need managing |
| Planning: the team should own the plan |
G. Don't Overreact
When people do senseless things or events go wrong, stay levelheaded: keep emotions in check, keep opinions to yourself, and analyze logically. Anything said in the moment rests on incomplete and probably inaccurate information; let the picture firm up first.
Even urgent decisions need a pause. Willink's gunfight example: fire from the north means returning fire north at once, but not committing to maneuver until you have assessed:
- Size. A small enemy may be attacked; a large one may call for breaking contact.
- Terrain. Open ground without cover may make even a small attack futile; covered approaches may make it right.
- Main effort or feint. Is this the enemy's main thrust, or a distraction while a larger force prepares to hit from elsewhere?
Consider it quickly, but fully and carefully. In business: hear that an employee is talking to a competitor? Stay calm and dig for information. Told a project is badly off track? Do not yell; find the cause and the support needed. Overreaction is always bad: it produces poor decisions and signals a leader who is not in control and may make irrational snap calls. Step back, detach, find the reality, decide calmly.
H. Don't Care
A harder form of detachment is "I don't care." In negotiation it is the power to walk away: "you don't want to lower your price? That's fine, I don't care, keep it." For a leader: You want to use your plan, not mine? I don't care. You want me to do a demeaning job? I don't care. Give someone else the chance to lead? Awesome, I'll support them fully.
It is hard because it requires subordinating the ego, the strongest drive a person has. Drill into what you care about and much of it is ego. A crappy task angers us because of ego. Handing over a project would actually lighten your load; it hurts only because surrendering leadership, then supporting your replacement, wounds the ego. Ego pushes you, will not let you sleep, cares about no one else, and is shortsighted.
I. Everyone Is the Same, Everyone Is Different
Everyone is the same: every organization, from a SEAL platoon to a boardroom to a Girl Scout troop, has the same archetypes: confident natural leaders, shy loners, quiet cerebral thinkers, bold aggressive types, people who want to win, and people unconcerned with winning. Everyone is different: each has distinct motivations, agendas, idiosyncrasies, and ideas, and no two "leaders" or "loners" are alike.
The leader must vary communication style by person while keeping one message, read what drives each individual, gauge how much pressure each can take, and do it while sharing attention equitably and without spoon-feeding custom messages until everyone depends on them.
The failure pattern: a tool does not work, the leader blames the team and applies it harder, the response worsens, he applies maximum pressure, and, like wood that splits, burns, or warps under too much pressure, the team or individual is ruined. The prudent leader takes the pressure off, studies the team, the individuals, and the dynamics, then adjusts the technique or changes tools.
| Symptom | Wrong tool, applied harder | Better adjustment |
|---|---|---|
| Team shows no initiative | More specific direction, then more oversight, then exact instructions. Initiative falls to zero; they wait to be told. | Recognise it as micromanagement; give broad guidance, authority, and autonomy so they own the way ahead. |
| Individual underperforming | Pull responsibility to send a message; confidence drops, performance worsens, more is pulled, resentment and an antagonistic spiral follow. | Increase responsibility with higher-importance projects; the worker feels trusted, gains experience and confidence, and asks for more. |
Like a woodworker who is an artist as well as a craftsman, a leader applies tools with tact, diplomacy, prudence, and subtlety. "That is the art of leadership."
J. Let Nature Work
People are products of nature and nurture: personality, motivation, temperament, attitude, skill, aptitude. Which traits come from which, and how much, is unclear, and the leader need not know. The job is to use the traits for the team and the individual, matching attributes to roles:
- Do not make a shy introvert a salesperson.
- Do not put a brash, insensitive person in charge of human resources.
- Do not put a wildly creative person in a strict-procedure role.
- Do not put a meticulous perfectionist into chaotic duty.
Perfect fit for everyone is untenable, and people should also be stretched outside their comfort zones, in a measured, controlled way, to shore up weaknesses: sales training calls for the introvert, role-play exercises for the brash talker. But primary duties should fit natural strengths; people enjoy the work more and do it better. "Don't fight against nature. Use it."
K. Isolation as a Leader
Leaders must be comfortable alone. There is some separation from the troops, you usually work longest (in first, out last), and decisions are yours alone: you can seek counsel and consensus, but the final call is "the burden of command."
Isolation need not mean loneliness. Willink was usually not lonely because he cultivated strong relationships up and down the chain, carefully: not everyone has the maturity for a close relationship with the boss, so build slowly. The goal is a few trusted agents at various levels to keep a finger on the team's pulse, flag coming problems, test ideas, and share a laugh or vent a little under stress.
- Keep relationships in bounds. They do not mean preferential treatment, undue influence, or unfiltered candor. It is a fine line; err toward professionalism, but do not go it alone.
- The decision stays yours. Some things only the leader's position reveals, however well explained. If the decision fails it was not "the team's decision"; however many advisors weighed in, it rests on the leader alone.
L. Know What Is Important and What Isn't
A jiu-jitsu black belt differs from a white belt by seeing past insignificant movements and focusing on what matters; he is a master of energy conservation, wasting no movement on attacks that do not matter. A good battlefield commander recognises reconnaissance by fire and enemy ploys and ignores what will not affect the battle. Every leader needs the same discrimination.
Change is constant: external (environment, enemy behavior, market, weather, timing) and internal (individual emotions, relationship dynamics, morale). Leaders routinely burn time and energy on events that will not affect results. Immersed in minutiae, "every molehill looks like a mountain," so detach and ask first:
- How will this problem impact the team's strategic goals?
- Can it cause mission failure?
- Is it worth my time and effort to engage in it?
- How bad can it get if I leave it alone?
- The dichotomy. A leader can climb too high: thinking a problem beneath him, hoping it goes away if ignored, or assuming a subordinate can handle what actually needs the leader. Any of these lets a problem grow out of control. Know when to step down into the tactical situation and fix it before it gets out of hand; only proper detachment and assessment make that call possible.
Principles
A. The Most Important Member of the Team
Willink told the point man he was the most important member of the platoon: leads the patrol, knows location and destination, guides through hazards, is eyes and ears for ambush and IEDs. Truth. He told the radioman the same: if a large enemy force threatens overrun, the radio and the ability to call for fire (aircraft, tanks, other friendlies) keep the platoon alive. Also truth. Same speech to the medic: bring guys back alive; if someone is wounded, only the medic keeps him alive to surgery. Same to machine gunners (without suppressors the platoon cannot maneuver and survive), to rear security (like the point man, knows where to go if contact hits), and to enlisted and officer leadership (leadership is the most important thing on the battlefield).
He was never lying. At any moment on a patrol, any one person can become the most important. Failure by any member at a critical moment can be catastrophic.
Carry that attitude into any team: every job is absolutely critical. Explain what happens if they do not do it well. Even menial roles: show how the small job fits the big picture and strategic mission. Everyone has the most important job. Let them know that.
B. Span of Control
How many people can you lead? Loose rules exist; the real answer depends on variables.
1. Situation dynamism. In combat or other demanding physical/mental environments, keep the number small. That is why military units use four- to six-man fire teams: noise, confusion, fog of war, distance, and comms limits prevent even excellent leaders from directing larger groups effectively.
As SEAL task unit commander with about thirty-five to forty people (depending on augments), Willink still only directly led a few at a time. Structure: two platoons → each with two squads → each with two fire teams. Decentralized Command meant he usually tracked two or three subordinate leaders, not forty individuals.
Head-count example. Signal for head count; each fire team leader (almost always in visual/audible range) confirms four guys in seconds; passes to squad leaders (two per platoon); platoon commanders signal "up" (all present) or not within seconds. Infinitely better than counting off every person or walking the formation. Each fire team also needs a succession plan: if the leader is wounded, killed, or incapacitated, next ranking member steps up, including head count. If a squad leader tried to cover incapacitated fire team leaders and track all eight to ten people alone, control would fail; too many. Leadership at every level is required for Decentralized Command to work.
2. Administrative environments. Locating, communicating, and interacting is easier, so leaders can control more people, but limits remain. Business leaders face meetings, calls, travel, and day-to-day demands. Generally: about eight to ten people. Beyond that, bandwidth collapses; the boss cannot track events inside each subordinate's world.
3. Quality, experience, and trust of subordinate leaders. Strong subordinates who understand the mission and interpret Commander's Intent need little guidance; you can supervise more of them. Inexperienced subordinates who lack judgment and do not grasp strategic objectives demand close monitoring; you can oversee far fewer. Reality is usually mixed: some nearly autonomous, some needing constant oversight, some in the middle. Goal: transition everyone toward low-guidance so you can look up and out instead of down and in. That takes time and is only possible with a limited number of people to invest in.
If span grows too large, elevate high-potential troops to lead smaller teams beneath you and restore a manageable number. Organize however you must; keep span limited so you actually have control.
| Factor | Smaller span | Larger span |
|---|---|---|
| Environment | Combat / high chaos | Administrative / stable |
| Typical ceiling | 4-6 (fire team) | ~8-10 (business) |
| Subordinate quality | Inexperienced, low trust | Experienced, high trust, clear Intent |
| Fix if overloaded | Elevate juniors into nested leaders; cut direct reports | Invest until more can run hands-off |
C. Taking Care of Your People with Discipline
Military leaders hear "take care of your people" from day one. Some translate that as comfort and happiness: coddle, maximize time off, avoid hard pushes. Willink calls that wrong; the opposite is true.
In the SEAL Teams, caring means push hard, train hard, ensure they understand war tactics and the weapons and radios they will run, keep them in top physical condition, and prepare them for mental and emotional combat stress. Highest probability they and the team return home to families comes from hard, disciplined training.
Business transfer: lives may not be on the line, but professional failure blocks financial goals and the ability to provide for families. Push them; make sure they understand their jobs; drive them toward goals.
Dichotomy: do not drive so hard you break them. Burnout is real on battlefield and in business. Know when to back off and give a break (he points ahead to the stress-handling tactics section). Job is not to put people on the easy path. Easy path leads to misery. Path of discipline leads to freedom.
D. Imposed Discipline
Optimal team discipline is not imposed by the leader; it is chosen by the team. Optimal discipline is self-discipline.
Teams do not always have it; they may not see the rewards. Then a carefully applied level of imposed discipline may be needed so they learn the benefits.
Change resistance case. Leader introduces a more rigid process, explains the why and advantages, and attitudes still refuse. Soft pressure scripts: "we have to give this a try to at least get some feedback"; "before the company wastes more money on it"; "if we don't make changes, we fall behind and it costs us all."
Why not just order it if you know you are right? Direct order is the least effective change method. Removing input removes ownership; without ownership there is no personal stake; at first resistance, forward progress stops. Voluntary embrace and ownership drive success.
Exercise analogy. You can make people show up; you will not get maximum effort. Maximum effort is intrinsic. Best athletes push themselves; coaches still matter and sometimes impose extra workout, another rep, another play. If the player has no say at all, control and morale slide. Sometimes allow the break, the preferred drill, the active rest day. More control in subordinate hands is better.
When soft encouragement fails to connect benefits to the task, a rare hard line appears: "We are going to do this." Willink says he can count on one hand the times he imposed his plan on a SEAL team in a leadership seat. If the change truly benefits mission, buy-in should usually be available. Cases that force a direct order often involve individual agendas misaligned with leader or mission.
After a direct order: caution. People directed against their will may withhold maximal effort or, worse, sabotage to prove the leader wrong. Worst case, and a reason imposed discipline is never the best option. Best recovery: team eventually accepts, sees benefits, and applies the discipline voluntarily.
Always prefer: explain why → show benefits to mission and selves → maximize ownership → intrinsic discipline. Imposed discipline is an uphill battle.
- Explain why and benefits; invite ownership
- Soft pressure / trial framing if resistance holds
- Rare direct order when agendas block a necessary mission benefit
- Watch for withheld effort or sabotage; aim for conversion to self-discipline
E. Pride
Pride is one of the seven deadly sins and a powerful force for good. Same word, opposite meanings depending on construal. "He took a lot of pride in how he looked" can mean professional self-care or vain mirror obsession. For teams: excessive pride → arrogance → no hard work, practice, or respect for competitors → ego inflation, stagnation, downward spiral. Healthy pride → extra work, care for details, higher performance, self-policing of standards.
Military unit pride is observed even if not perfectly quantified: appearance, mission execution, carriage. Patches, songs, banners create belonging and exceptionalism. Pride comes from history, past performance, shared hardship (as long as challenge does not break them). In Iraq, Army and Marine units hung historical documents, flags, and battle streamers in TOCs, chow halls, ready rooms, barracks. Sports and business do the same with banners, trophies, framed articles, awards, good reviews. Displayed past becomes the standard to pursue. Optimally the team holds itself: slackers corrected by peers, not only by leadership.
Team without pride? Leader's critical task: instill it. Not by telling them they are great or hanging unearned banners. Give them the opportunity to earn it. Put them in situations requiring unity, strength, perseverance. Push training to true test points.
Military hard training (basic, airborne, SOF selection) prepares for combat and builds pride. As task unit commander, Willink's unit trained harder than peer task units: earlier, later, extra shooting/maneuver iterations, morning jiu-jitsu, hard team PT. At first he imposed the discipline; grumblings about extra work. Over time complaints faded; imposed → self-discipline → pride. Lines he heard: "We work harder than anyone else at this team"; "No one else comes close"; joking-but-true "If you aren't in Task Unit Bruiser, you wish you were." Better performance came from more shared work and higher mutual standards, not more raw talent.
Formula he states: if you want to build pride, bring pain. Pride from shared suffering. History and winning help; you cannot count on them. Make them earn it through hard work.
Dichotomies to avoid:
- Push so hard you break spirits instead of forging them
- Build pride into arrogance / invincibility / slacking because they think they need not earn it
If morale fades or frustration dominates, back off; let them get wins. If they win so much in training they think they cannot be beaten, push harder. No pride on easy wins; some wins are still required. Find and hold that point. Pride works when balanced between humility and confidence; the leader builds, maintains, and channels it.
F. Giving Orders
Returning from his first Iraq deployment as platoon commander to take Task Unit Bruiser, Willink had more training-and-combat leadership experience than the rest of the unit: prior-enlisted tactics instructor across SEAL mission sets; early Iraq platoon that took target after target. He knew troop placement, timelines, and actions on the objective.
As task unit commander giving mission orders, he still did not dictate troops to bring, where to put them, vehicle counts, weapons, timelines, routes, or contingencies. He stated the mission objective: the goal. Military term: Commander's Intent. Platoon leadership and SEALs then chose troops, vehicles, weapons, timelines, routes, contingencies. The plan became theirs. Ownership followed.
He often judged he had a better plan (ego plus real experience). He still usually did not override.
- Their ~80% vs your ~90%: let them execute; commitment makes up the ~10% efficiency gap
- Their ~70% vs your ~90%: still theirs, after small course corrections
- Their ~50-60%: bigger course corrections to lift to ~70-80%; still their plan
- Nearly irredeemable: ask questions until they see the shortfalls (usually not hard); send them back to the drawing board with lessons learned; new plan still theirs, not a forced substitute
When opportunity allows, let subordinates plan: ownership plus the altitude to see holes while you stay out of the weeds ("tactical genius" effect from detachment). Biggest obstacle: ego. Leaders want control, want to be listened to, often believe only they can craft the right plan. Let it go. Be overjoyed at a somewhat workable subordinate plan; make minor adjustments; let them run. Iteration plus your corrections makes their plans as good as yours, then better. Then you look up and out, which is the leader's job.
Issue Intent, let them build: plan is theirs; conviction high; you retain altitude for corrections without stealing ownership.
G. Yes-Men
Leaders should not want to be surrounded by yes-men. Subordinates should not be yes-men; speak up when something does not make sense.
That prescription scares some leaders: constant pushback, constant why-questions, frontline recommendations. Some prefer exact compliance. Willink calls that a bad idea.
Tactical example. He commands three platoons, positioned toward the rear. Lead element (first platoon) takes fire from elevated enemy bunkers with multiple machine guns and interlocking fields of fire. First platoon retreats to a small depression safe from the guns and reports. Anxious to move, he orders: "Take your platoon and assault and destroy the enemy bunkers." Simple attack order; horrible idea. Open uphill assault into interlocking machine guns kills the assault force.
Last thing he wants: a subordinate who says "Roger that, sir" and leads the platoon to death. He wants a subordinate with confidence and trust to say: "Boss, that isn't a good idea. We need heavy artillery on the bunkers; then we can flank." A good boss listens to the person closer to the problem and supports the better suggestion.
The pattern transfers to planning, preparation, and execution. Optimal performance does not run on one brain. Encourage thinking and questioning. Yes-men help neither leader nor team. Discomfort with pushback: check the ego; it is probably inflated.
What: Instinctive "assault the bunkers" order vs needed artillery then flank.
Outcome (teaching): Blind compliance would be fatal; trusted dissent plus leader humility saves the force.
H. The Exception to No Bad Teams, Only Bad Leaders
In Extreme Ownership, Willink and Babin wrote "no bad teams, only bad leaders." Not original: Napoleon said no bad regiments, only bad colonels; U.S. Army colonel David Hackworth in About Face said no bad units, only bad officers. Willink still rejects "bad team" as an excuse for bad performance. No situation where a subordinate is ultimately responsible for team performance; always the leader's fault.
Exception: it is possible to have a good team that delivers outstanding performance despite a bad leader.
How, if leadership is the most important success factor? Subordinates lead regardless of rank: tactful people who lead without official authority, without offending the structural leader who may not tolerate being outshone. If the structural leader's ego is huge, he will not listen and will counter junior leadership until the team fails. So in a successful team actually led from below, the structural leader still deserves credit for the humility to let subordinates run things. Without that humility, junior leadership would be resisted and the team would fail.
Implication: strong performance does not prove the structural leader is the driver. Stepping back so others can lead is a positive quality; it is not the same as driving the success.
Why the next leader up must know this: organizations are not stagnant. Tasks shift; missions change; people move; teams re-form; promotions happen. Misread the true strength and you make bad personnel moves: transfer the "strong team's leader" to a weak team, and nothing improves if that leader was never the engine. Identify the actual subordinate driver, promote them into the weak team, and turnaround becomes possible. The strong team, with sustained culture and knowledge, often keeps performing even after losing its star.
Leadership remains the most important factor, but it may not sit in the box at the top of the wire diagram. A bad team is without question a bad leader's result; a good team is not necessarily a good structural leader's result. Know your people well enough to recognize and capitalize on that.
| Claim | Status in this chapter |
|---|---|
| No bad teams, only bad leaders | Still the default: performance failure is on the leader |
| Bad team as excuse | Rejected |
| Good team + bad structural leader | Possible when juniors lead and boss has enough humility not to block them |
| Promote/transfer by title alone | Dangerous; find the real performance driver first |
Principles map: role criticality and span set the org geometry; discipline and pride set culture; Intent, dissent, and the bad-leader exception govern how authority actually works.
Becoming a Leader
A. How to Succeed as a New Leader
Starting right is simple and hard. Willink's fundamental rules for taking command:
- Be humble. Leadership is an honor; the team counts on your decisions.
- Do not act like you know everything. You do not; the team knows. Ask smart questions.
- Listen. Ask for advice and heed it.
- Treat people with respect. Rank aside, every person is human and plays a role. Take care of them and they take care of you.
- Own failures and mistakes.
- Pass credit for success up and down the chain.
- Work hard. Harder than anyone else; no job beneath you.
- Have integrity. Do what you say; say what you do. Do not lie up or down the chain.
- Be balanced. Extreme actions and opinions are usually bad.
- Be decisive when it is time to decide.
- Build relationships. A team is people who trust one another; otherwise it is a disconnected cluster.
These rules make sense on paper and are easy to forget under pressure. Review them often: in the morning, before meetings, before you make things happen, before sleep. They become second nature; when you struggle, pause and check them again.
Stepping into a seat without full knowledge or experience is normal. No one expects omniscience on day one. Being new is not an excuse for ignorance or lack of preparation: learn terminology, fundamental principles of the work, names and faces, and study any documentation that familiarizes you with the mission.
If you have studied, the questions you ask land as smart and are well received. Ask to be shown how things work. Learn to operate the equipment; you will not match operator proficiency, but going through the motions builds deeper understanding. Interact with frontline troops; learn their challenges and the details of what they do. Interest in their job raises respect and builds the relationships that are the leader's main goal.
B. How to Be Chosen to Lead
Number one path to promotion and leadership: performance. Do the job well. First person to show up, last to leave. Volunteer for the most challenging tasks, projects, and missions that no one else wants, including those that are mundane and unrewarding.
Next: do not make being chosen the primary goal. Make helping the team win the goal. Do not feel you need to be in charge of everything. When someone else has stepped up, be a good follower. The more you help the team win, the more people want you on the team. The more they see humility without spotlight-chasing, the more trust and clout you gain.
Dichotomy: you can be too humble. Constantly deferring leadership opportunities signals that you do not want to lead, and you will not be put in charge. Volunteer to lead whenever possible, but keep primary focus on team goals. That attitude gets noticed; the chance follows.
C. When You Are Not Chosen
There will be times you are not selected: someone from your team is promoted, or someone from outside is brought in. Frustration and anger are normal. Keep those feelings to yourself.
Instead of nursing anger, do a good honest self-assessment of why you were not chosen. After you have calmed down, ask superiors why, with tact.
Wrong: "Hey, boss, why wasn't I selected? I am just as good, if not better, than the person you gave the role to."
Right: "Hey, boss, I wanted feedback. There was a recent promotion, and I eventually want a more senior leadership seat too. What can I focus on so I am more qualified and prepared when the next opportunity comes?"
When you receive that feedback, actually listen. Humans get defensive by default; do not. Try to understand the perspective offered. Own the shortfalls and improve in the areas of critique.
Not all leaders are good at giving feedback; direct critique is hard for some. You might hear, "Oh, you're doing great. It just wasn't your time." That is not necessarily true. There was a reason; dig harder in self-assessment and analyze where you can improve.
Finally, do not hold a grudge against the person who got the promotion. As much as it pains an immature ego, support them. Make them look good. Help them win. Undermining hurts the team, makes you look bad, and creates an antagonistic relationship that moves you farther from a leadership seat, not closer. Be a team player; help the team and the new leader win.
Career reaction: private assessment, tactful feedback ask, own the gaps, support the winner.
D. Imposter Syndrome
Some people worry they are not ready for a leadership seat; some feel, once in it, that they do not deserve it. These anxieties are often called imposter syndrome. Willink treats the feeling as potentially good.
Worry that you are not ready means humility. Nerves mean you will prepare and, once in the seat, be thoughtful about words, actions, and decisions. All of that is positive.
As assistant platoon commander, platoon commander, and task unit commander in the SEAL Teams, he always felt not quite ready or not quite capable. The burdens of command and responsibility for men and mission made him nervous about decisions and actions. Because of that feeling, he doubled down on preparation: strategy, tactics, and leadership. He wanted to do a good job.
Contrast: some SEAL leaders he worked with or put through training thought they were not only ready but eminently qualified. In their minds they did not need to prepare, study, carefully consider words and actions, or listen up or down the chain. That attitude is the opposite of imposter syndrome: plain arrogance that destroys leader and team. Extreme overconfidence is a disaster.
Going too far the other way is also a problem. Lack of confidence that you belong is obvious to every team member. Balance between too confident and not confident enough.
If getting too confident: step back, listen, do not judge, let subordinates step up and lead. Relatively simple if you recognize cockiness. Warning signs: friction from troops that is not productive disagreement (your ego brushing theirs); or a complete lack of resistance after you have denied their plans a few times with no ground given (they shut down because they cannot contend with your ego). Pushback and disagreement that lead to productive conversation and eventual agreement are fine. If you cannot get them to agree, the problem is likely you. Prefer letting them execute their way when the plan has a decent chance of success; give guidance that raises odds while keeping the core plan theirs so they keep ownership. That only works if your ego is in check. Force your plan down their throats and they may execute begrudgingly.
If imposter syndrome is too strong: people tend to clam up and become invisible, which invites more disrespect. Counterintuitively, open up. Ask why a team member did a certain thing at a certain time. Ask for input about a plan. Solicit advice on how best to move forward. You do not know everything; no one expects you to. Acting like you do makes the troops see you as what you fear: an imposter. Act humbly, expose yourself, ask questions, admit gaps, and trust and confidence begin to build.
This is not a free pass for stupid questions. For leaders, dumb questions exist. That lack of preparation shows.
Stay humble, study, ask, learn, and balance the dichotomy between too much humility and too much confidence.
Hesitation to volunteer for or accept a new seat is normal for humble people. You will rarely feel completely ready. Have faith in yourself and in the leaders offering the role: trust that they see readiness and that is why they are asking you to step up.
E. Insecurity as a Leader
If imposter syndrome gets in a leader's head, it can grow quickly into true insecurity. Uncontrolled, it begins a downward spiral for the leader and then the team.
The problem is not feeling insecure about ability, experience, and knowledge; that can still be humility. The problem starts when you inevitably try to cover it up: shift conversations, avoid questions, use other subterfuge to mask weaknesses. You will not fool anyone; everybody sees through you. When the team sees the weaknesses, they start attacking them. The more they attack, the more you cover up, the more obvious it becomes.
Overcome insecurity not by hiding but by being humble enough to admit what the gaps are. Present them. Ask for help. Explain shortfalls and what you want to do to correct them.
Do not go overboard into presenting yourself as incompetent. Prepare and research enough to understand areas of weakness. When a new blind spot is uncovered, take notes and reinforce the weak area.
Humility and vulnerability can work together: admit a vulnerability, address it, reinforce it, solve it. That is contrary to the intuitive idea of masking weaknesses. Admit to yourself, air to the team, then work to improve.
F. Transitioning from Follower or Peer to Leader
Many organizations elevate someone from a peer group into a leadership seat. The transition is hard: peer relationships are closer than normal leader-subordinate ties.
Willink watched it twice in SEAL platoons when "one of the boys" (a young enlisted SEAL) was selected as LPO (leading petty officer). Structure then: OIC, AOIC, platoon chief (CPO), then LPO as fourth in command. LPOs usually had more experience than the rest but were not necessarily senior in rank. The LPO transferred much of Commander's Intent from OIC and CPO to the troops and made things happen. Often LPOs came from another team or training command to mitigate excessive familiarity; these times an insider was chosen.
Larry. Platoon newly formed, no LPO assigned. Junior enlisted sitting in the hut when OIC and CPO called out a more experienced same-rank SEAL ("Larry"), told the rest to stand by, took him to the commanding officer and command master chief, and selected him as LPO. About half an hour later he returned. Chief announced the selection and asked for support. Larry pulled out a wheel book (navy-issued four-by-six notebook) and a checklist: full weapons and sensitive-items inventory (radios, night vision, crypto); gear staged by 1000 on the grinder for pallet build; hazmat paperwork for lithium batteries, fuel, and ordnance; pallets by lunch; immediate-action drill walk-throughs at 1300; wrap by 1430 or 1500 for home time before leaving. Then: "What do you guys think? Did I miss anything?" Respectful, appreciative, confident, clear.
Brian (~18 months later, next platoon). Same formation void, same summoning ritual, same return as new LPO. Instead of a wheel book, checklist, schedule, or ask for input, he cracked a joke: "Looks like I'm responsible for all the crap now." That was the word. Completely ineffective. Brian was a great guy and great operator; he was not ready to make the transition. The platoon floundered for a few months until he got his leadership bearings.
Floundering is not required. When you transition from within a group to leading that group, step up. That does not mean know everything or lay down the law. It means differentiate who you were as one of the troops from who you are now as a leader:
- Come up with a plan.
- Give simple, clear, concise direction.
- Stay humble, take input, and listen.
- Lead.
One more point: once in the seat, step not only up but out of the weeds. Stop some old comfortable tasks; start uncomfortable leader tasks. Look up and out, not down and in. Guide plan development and oversee execution; let the troops do the doing. If the leader is doing, the leader is not leading.
Dichotomy: do not become so detached you are aloof from what frontline troops contend with. Don't be the leader with hands in pockets; don't be the leader with hands in everything.
G. Overcoming a Grudge
When you are the one promoted above former peers, most accept it and get on board. Some get bitter and resentful and show it.
Mitigate a bad attitude from former peers:
- Do not force rank down their throats.
- Tell them you appreciate their experience and will look to them to help lead.
- Let them come up with plans and ideas; ask for and listen to input; if solid, let them run.
- When opportunity arises, put them in charge of tasks, projects, and missions. That shows trust and appreciation; if they can put egos in check, the situation can be overcome.
Also be advised: some people are hypersensitive and see you putting them in charge as condescending, or as proof you do not know what you are doing and that they should have been promoted. When pouting and bad attitude become apparent, recognize that the likely reason they were not promoted (assuming they do have the most knowledge and experience) is lack of humility and maturity. Continue to be cordial, treat them with respect, try to build a relationship, but do not expect rapid improvement. Long process; be patient; do not let them distract you from the mission or the rest of the team.
H. New Sheriff in Town
Approaches to change after moving into a leadership seat span a spectrum: come in hard and immediately impose will, or spend a large amount of time observing and change slowly and incrementally. Many methods sit between. Which to use depends on the situation you are entering.
Know as much as possible about mission and troops before taking over. A thorough turnover from the previous leader is ideal: state of the team, challenges, personalities, strengths and weaknesses.
When receiving information from the departing boss, remember their bias. Are they being fired? Personal relationships with team members? Big ego that might undermine the new leader? Understand the spin.
Also try to know people before you meet them: individual and collective training records; a guidebook with pictures, positions, skills, experience, personal interests, family situations.
Consider team status. High-performing or failing are extremes; most sit in between, so modulate. Be smart: do not change what is working; do not accept what is not. Better team → less you have to change. Worse team → more adjusting.
High-performing takeover. Go in fairly gently. Introduce yourself; make yourself available; do not bark orders or impose your way. They are already functioning, relating, succeeding. Do not interfere. Observe closely, learn how they work, eventually look for areas where some improvement is possible. "If it ain't broke, don't fix it." Once on board, get to know the team: formal all-hands plus individual meetings if time and logistics allow; also informal visits while they work, drop-ins on meetings, walking the grounds. This is when you build the relationships that become trust and camaraderie.
Failing team, causes known. More direct and aggressive. Research the problems; bring ideas to implement immediately; lay out a clear vision and new mission; emphasize specific changes; set new processes; move personnel; perhaps terminate people causing significant problems. No doubt in anyone's mind that the status quo is gone.
Failing team, causes unclear. Still make some changes, but ones that do not impact current operations: communication protocol; add, change, or cut meeting times; perhaps a new dress code or other fairly benign adjustments that get attention without interfering. Develop relationships with senior leadership, midlevel managers, and frontline troops; interview separately; look for trusted agents at every level. Open trust slowly: a failing team is traumatic, and people can be emotional and make false or misleading statements. Take everything with a grain of salt. As you isolate problem areas, incrementally make more impactful changes, slowly, with feedback on effects.
The better the people, the more you lean on them for solutions: ideally you identify problem areas and they invent fixes, take ownership, and execute. If the team is grossly subpar, listen more critically; track record indicates weaker problem-solving. Also watch for the case where the leader you replaced caused many problems: once unburdened, subordinates may be ready to perform exceptionally. Do not hinder that.
Pattern: with a high-performing team, after relationships and understanding, make incremental changes toward maximum efficiency. With a low-performing team, start dramatic and back off over time as function returns. Always modulate guidance, interaction, and direction based on actual performance.
| Team state | Opening move | Then |
|---|---|---|
| High performing | Observe; relationship-build; minimal interference | Incremental tweaks |
| Failing, causes known | Clear vision, process/personnel shocks | Sustain until standards hold |
| Failing, causes unclear | Benign attention changes + multi-level interviews | Escalating changes as truth emerges |
I. Don't Go Overboard, Rambo
You want to be a leader. Good. Do not be offensive about it. Do not run around saying, "I'm the leader! I am in charge! Listen to me! I'll make the decisions!" That attitude offends many people. It is the equivalent of "Look at me! I'm important!" and does not go over well. Rambo is a cool movie character; charging out alone without regard for others does not work in a team. Saying "I am the leader; follow me!" can offend egos that may already think they should be in charge. When you make a mistake (and you will), they will be ready to pounce.
Leadership, in most cases, should be subtle. There are situations for bold, overt leadership: emergency with no one taking action; morale down, troops stagnating, movement needed from the front. In everyday situations, overt leadership is not needed. Better to give subtle direction and let troops move forward on their own ideas.
Same for mentoring and coaching. Many people say they want to be coached but have a hard time when someone actually steps up. Offering to coach implies not only that the other person is lacking but that you are better. That bothers people, especially big egos; unfortunately, the biggest egos often need the most coaching.
Prefer indirect openers that start a conversation and disarm defenses:
| Direct (activates defense) | Indirect (opens conversation) |
|---|---|
| "I'll tell you how we are going to execute" | "How do you think we should execute?" |
| "Let me coach you how to do that" | "Can you explain why you do it that way?" |
| "I will mentor you" | "I would love to compare how you do things to how I do them" |
Once discussion starts, embed your thoughts. If your methods are superior, that should become apparent; the person becomes more receptive. Over time, sway them toward your way of thinking far more acceptably than shoving mentorship down their throat.
Occasionally someone truly craves your leadership and mentorship; then you can be more direct. Even then, use caution: people asking for criticism can still be offended when they get it. Start softer.
The people who taught Willink the most about leadership, strategy, and tactics never explicitly said they were coaching or mentoring; they guided so delicately he thought the ideas were his. That is the most powerful way to teach. The best leaders he worked for were also incredibly subtle. Very rarely did they come out with direct orders stating exactly what and how. They led by suggestion, putting ideas out and allowing the troops to identify them as best and enact them through their own volition. Ownership follows because the ideas feel like their own. Indirect leadership almost always trumps direct.
Almost: times of duress with critical immediate decisions require a call; so do moments of indecision when multiple ideas are argued and the team cannot choose. Because the subtle leader has not constantly made every decision, those rare calls are respected. Contrast the leader who must drive every choice and sit at the center of every conclusion: that voice loses value because it is heard too often.
Do not go overboard as leader, mentor, or coach. Do not be Rambo. Be as subtle as you can until you can't. Then lead.
Leadership Skills
A. When to Step Up and Lead
There is a dichotomy between when to lead and when to follow. Even if you are in charge, if someone has a good plan and is giving direction the right way, step back and let them lead. Be a follower.
There are times when a leadership vacuum appears: no one is taking charge; bad circumstances unfold; no one is doing anything about it. That is a moment to jump in with a simple plan and clear direction. People are often waiting for it; when you step up, they accept and execute.
It is not always that simple. If you are the only one who has recognized the threat of inaction, others may think everything is okay. Jump up barking orders and they may be taken aback, offended, or feel you are stepping on their toes.
That is why Willink often hesitated a moment when he saw a vacuum. Immediate threat that needs an instantaneous call with no one acting: step up now and fill it. Problem unfolding more slowly: do not rush. Let it develop a little. Detach mentally; truly observe; confirm what you see. Allow opportunity for someone else to step up. If they do and guidance is good, support them. If guidance is bad, keep refining a better plan so you can correct when the time is right.
When no one else steps up quickly, it is usually because no one else has noticed the vacuum. They are not detached; minds absorbed in the situation. Detachment puts you at a virtual distance where problems appear sooner. Still do not always jump immediately. Let the void linger a little longer so everyone begins to notice. Then when you give orders, people listen and execute.
Another reason to pause: make sure no one else is jumping in. Two people filling a void at once usually bump into each other; while the problem grows they spend precious time sorting who leads and who stands down. Ego clash at that moment is problematic. Prefer avoiding it. If someone else will step in with a plan, fine. Pause, look around, assess. While you wait, the problem grows; soon everyone notices; then you make the call everyone knows needs to be made and is waiting for. When you speak, people listen.
One more advantage of the tactical pause: the call gets better. Extra moments clarify problem and solution; direction lands on point; people follow.
Inverse: too many people trying to lead. Everyone offers opinion, advice, weigh-in. That inhibits decision-making and the leader's ability to lead.
Battlefield parallel: troops bunch up in tight groups. One well-placed (or lucky) round (bullet, mortar, RPG, IED) can kill or wound many. Military fix: dispersion. "Don't bunch up" is a common critique in training. Simple, hard: compelling forces draw people together.
- Psychological safety. Fear makes another person nearby comforting; three, four, five congregate and become a cluster at risk.
- Opportunity. Limited cover and concealment; everyone wants those spots; crowding follows.
- Desire to know. See, hear, communicate face-to-face; when one person stops, others flock.
Only understanding plus repetitive training overcomes the instinct. The same phrase applies to leadership: crowding the leader's mental real estate, stepping on toes, undermining authority, and denigrating team capability by interfering. Bunching up on the leader hurts the team.
Main driver: ego. Intrinsic desire to be in charge, make decisions, be important. When we are not in charge, ego hurts; we infringe to prove we should be deciding. We also think our ideas are best (ego again): talk instead of listen; bombard the leader instead of giving time and space; bump and disrupt instead of support. Even with ego in check, desire to contribute can force ideas into a moment that needs execution more than brainstorming.
Step away. Do not crowd the leader by finagling your ideas into the mix. Give the leader room. Don't bunch up.
B. Don't Take Things Personally
This may seem obvious; Willink sees people take things personally all the time. Don't. It is hard. You have to fight your ego. Even when people ask for critique points, they often get mad when they actually hear them. Do not take criticism personally:
- Not about the plan you came up with.
- Not about the idea you had.
- Not about the presentation you gave.
- Not about the decision you made.
Even when your biggest rival, the last person you want to hear from, has something to say: listen. Even when someone you do not think is on your level, someone without the knowledge, position, or authority to give you feedback, wants to speak: do yourself a favor and listen. Detach; from an objective mind-set see if you can learn anything at all; apply it; say thank you. It stings. Get over yourself. This takes humility. It will make you better.
C. Don't Dig In
General George S. Patton famously told troops not to dig in; he wanted them to advance. You cannot advance if you are dug in. The idea transfers to leadership: when you have an idea, thought, or opinion, do not dig in. Do not overcommit. Keep an open mind. Leave yourself an out.
In SEAL leadership seats there were always many ideas: how to execute, what plan, which tactics. Like many organizations, no one seemed to agree; safe assumption: the idea people liked best was almost always their own (ego, pride, or clearer sight of their own perspective). Not unique to SEALs. People hang up arguing for their idea, not the best idea. Worst case: they dig in to protect it, concede no inch, and under attack dig deeper. Tactically: when people dig in to defend ideas, they cannot advance them and cannot maneuver or change thoughts.
Willink saw leaders come up with a plan, dig in, and defend with zero compromise: hours of fruitless argument driving toward their solution, not the best one, until they painted themselves into ordering compliance. If the dug-in person was a subordinate, the boss eventually ordered a different direction; they complied begrudgingly after wasted hours.
His default: seldom dig in or overcommit. On opposing views, do not look for ways to prove your idea better; look for which idea is actually better. If yours is not as good, concede and accept theirs. If relatively equal, defer to theirs so they have ownership. If yours is far superior, differences are usually obvious enough to convince without you ever claiming you were right (so you never have to admit you were wrong).
Rare dig-in occasions: 100% certainty you are right (almost impossible, so almost never); immoral, illegal, or unethical activities; violation of fundamental Laws of Combat he knew to be true. Even then, almost always leave room to maneuver (see Foundations on mutinies). It is almost never good to get into a position you cannot get out of.
Don't dig in unless you have no choice; even then, leave room to maneuver.
Battlefield dichotomy: if you are bogged down and cannot move, or decide to hold fast, then absolutely dig in and fortify. Leadership parallel: rare true defensive stands deserve a solid defense.
D. Iterative Decision-Making
"Be decisive!" is common advice; Willink heard (and sometimes delivered) reprimands for slow decisions. Indecision can make horrible situations worse. In the SEAL Teams it is often called analysis paralysis: overwhelmed by events, unable to decide. It can occur in any leadership environment. If you are not maneuvering, the enemy is; allowing enemy maneuver is one way to lose the upper hand.
Rushing without fully understanding can be just as bad. Example: receiving a small amount of enemy fire and attacking immediately. If you have not let the situation develop, that fire might be bait into a channelized kill zone.
Learn to let situations develop until you have a relatively clear picture. Until then, a conclusive decision is foolish. That does not mean no decision. When unsure or under-informed for a bold clear call, use an iterative decision-making process: look at the situation; make small decisions moving toward your best guess without overcommitting.
Raid example. Platoon tasked to assault a building where an insurgent is suspected of bedding down. He has been on the move for months; first predicted location. Target ~300 miles away. No helicopters (possible surface-to-air missiles). Drive ~five hours each way; plus a couple of hours for final recon and clear. To finish in one cycle of darkness (night-vision advantage), leave just after sunset.
Major problem: only suspicion he is there. Roads mean IED and ambush threat: big risk for mere suspicion. Do not immediately commit to taking the target. Start the planning process (several hours). Include stops at friendly forward operating bases for better assessment while routing. Near sunset, brief and check intelligence. If still suspected, proceed, but not yet all the way: to an FOB ~200 miles from target; recheck intel; continue only if still indicated. Repeat at ~100 miles and at the last FOB ~12 miles out. At any point negative intel appears, pause, assess, turn back. Mitigate risk to troops and risk of burning the target (hitting empty teaches the enemy the site is unsafe; almost zero chance he returns). Small iterative steps toward the goal reduce those chances.
Iterative decision-making is contrary to blunt "be decisive," but immediate launch on thin intel can put men at risk across six hundred miles of driving and burn the target for follow-ons. Be decisive when you need to be; try not to make decisions until you have to. Assess with the information you have; make smaller minimum-commitment decisions toward the direction you most highly suspect is right.
E. Decentralized Command or Lazy Designation?
Decentralized Command requires leaders to push tasks and authorities down to subordinate leaders, who push further to frontline leaders and troops. Willink often says: if a leader wants to be in charge of everything, try to be in charge of nothing. Only when the leader has delegated actions can the leader truly lead. It is impossible to lead a team forward strategically while directing and managing lesser tasks subordinates could handle.
As the boss delegates, it can look like the boss does not want to do anything. At what point do troops think the boss is lazy or dodging hard tasks, missions, or projects?
Real problem; simple prevention:
- If you sense any inkling of attitude that you are shying from tough missions or tasks, take charge of the most challenging ones and crush them. Set the example. Lead from the front.
- If you hear actual complaints about an assigned task: "Oh, you don't want to do that? Okay. I will." It should not take long for complainers to realize that turning work over to you puts them out of a job. It also hits egos: they lose control and ownership while you gain it. That can sting and change attitudes.
- Sometimes attitudes do not change. They happily let you take jobs because they do not want them: lazy, no desire for ownership, no pride, do not care. Good: clear signal they are not invested. Start looking for options to remove them from the position.
- Take on some of the harshest jobs yourself. Nasty work; get down in the grime. Short enough not to encroach on critical up-and-out time. Willingness removes the "delegating to avoid work" story and displays humility that raises respect.
Decentralized Command: push authority down, still grab the ugliest tasks yourself, and reclaim any mission the team treats as optional.
F. The Easy Button
Taking ownership of hard tasks does not mean doing everything for the team or subordinate leaders. Do that too much and you become the easy button: whenever there is even slight difficulty, they want you to solve it. You make their jobs and lives easy.
Occasional step-in problem-solving is required. As default mode, with troops expecting it, it hurts the team: you constantly look down and in instead of up and out; you focus on tactical issues when you should be on the strategic picture and next move. Worse: you stunt collective growth. They do not learn to think; they learn to ask you for solutions. Progress as leaders halts.
As task unit commander, Willink had the most experience among the officers: enlisted advanced-training instructor across SEAL mission sets; six overseas deployments including Iraq platoon commander on scores of direct-action missions. Junior officers had a fraction of that. They knew it; during the training cycle they often asked how to plan training missions. First few times he gave ideas and guidance from lessons learned. Soon: "Go figure it out yourself and come back to me when you think you have a good plan." At first they were nervous, perhaps expecting a throat-jumping chew-out. They learned he was there to teach, not abuse. He counseled shortfalls and tactically unsound elements; they corrected and returned with better plans. After dozens of training-cycle operations they understood planning solidly. Overseas he did not have to worry about their plans; they planned as well as or better than he could. That freed him for the overall operational picture, deconfliction with friendly units, and support of higher headquarters objectives.
He could lead because people below him learned their jobs and his. Don't stunt growth. Don't solve every problem they bring. Don't be the easy button.
G. Judging Reputations
As a leader you constantly meet new people: taking over a team, a new member joining, or working with another team. They arrive with reputations. History precedes them. Usually some written or virtual record: prior performance, awards, punitive actions.
Do not judge solely on what you have heard or read; keep an open mind and judge for yourself. Still consider prior history: read it, listen, note it. Give the benefit of a fresh start.
Because you noted past performance, confirmation is faster. History of lateness + late today = real problem. History of getting emotional + emotional outburst = confirmed.
If someone shows up with negative facts on résumé or record, give them a chance. Last boss might have been a nightmare. They might have lacked experience and fallen short. They might have made immature mistakes. Many of these can be resolved if the person is given a chance and led properly. Do your job and lead.
H. Conform to Influence
Willink liked highly motivated, aggressive people he had to reel in more than people he had to push, both as a leader and as a junior. Being fired up is not always welcome. It can offend people up and down the chain, usually via ego, sometimes for other reasons. He learned this in his first SEAL platoon as a new guy.
1992, SEAL Team One. Extremely motivated new guy wanting to train as hard as possible for war. Peacetime navy: first Gulf War had ended six months earlier after about seventy-two hours; Vietnam (the fierce reputation that drew him) had ended twenty years earlier. He did things differently: early to work; conditioning runs in heavy boots instead of shoes; rucksack with a forty-pound sandbag on the obstacle course; night ocean swims alone in web gear; everything a little harder than required. Preparing for war, in his mind.
Some older guys (six, eight, ten, a dozen years in) did not appreciate it. For them, sustained SEAL performance was a marathon, not a sprint. Extra wear on knees, shoulders, ankles, back had to be monitored. New guys out of BUD/S were healthy and ready to charge; he personally wanted the next level.
Grumbling started: "Here comes Rambo," "Look at this tough guy." First sounded like jokes; tone strengthened; he realized they did not like what he was doing.
Easy wrong story: What is wrong with them? I work extra hard; they are weak; I am hardcore; I am preparing for war; can I even rely on them? Especially easy when some older guys were not in the best physical condition: they must be intimidated; egos too big to handle a charging new guy.
Correct reframes: Who was he? New guy; never deployed; never been through a workup. Who was he to judge? Team perspective: a platoon should work together; he was alienating himself; a rift was forming; that disrupted unity and hurt operational readiness.
So he backed off. Extra work on his own time; with the platoon, he tried to act like the rest of the guys. He conformed.
That is something people do not want to hear about Willink. The myth says he would never give in to pack weakness. Holding the hardcore line would have meant his personal feelings mattered more than the team; ego could not subordinate; he believed he was more important as an individual than the team. Wrong attitude. Most important thing in a team is the team. The team exists to accomplish the mission; more unity → more capability. Causing a rift hurts mission capability.
Further: if some platoon members were not in great condition, he wanted them better. He was junior; he could not order them. Influence required relationship; relationship required membership. Lesson: you cannot change the group if you are not in the group. Inside it, you can move it, maybe not as much or as fast as you want, but in the right direction. Don't be overaggressive. Don't alienate yourself. Become part of it and earn influence.
Does that mean conform no matter what? No. Maintain individuality and unique perspective; just do not let personality block relationships inside the group.
If the group is doing things immoral, illegal, or unethical: stand up (smartly); participation or passive approval makes you culpable (see Foundations on mutinies).
If the group is not illegal/unethical but is hurting mission capability, or has a bad attitude toward leadership or the mission: digging in and forming an antagonistic relationship may not help. Alienation means they will not listen. Bond; build relationships so they listen. Stronger relationships → more listening. You may need partial compromises to connect, not full ones.
When someone says, "This mission is stupid, and so is the boss!":
- Full disagreement ("No, mission and boss are awesome") → they stop listening, or listen only to throw words back.
- Full echo ("You're right, stupidest mission, can't believe the boss") → solidarity that is hard to walk back; cheap bond via disrespect that compromises character. Extreme caution when talking about leadership and direction when they are not there to defend themselves.
- Middle path: "Well, it certainly is hard to understand the mission from our perspective. Why do you think the leadership has us working on it?" Opens civil discussion that grows the relationship; the question reveals their perception so you can better counter and get them on board.
As relationships and balanced conversations multiply, influence grows. Sway the group from inside by trust, not by attacking beliefs head-on (which isolates you). Be balanced. Build relationships. Lead.
I. Everything Is Good (But Not That Good)
Bad things are going to happen. When they do, the leader should maintain a positive attitude and find the good in the situation.
- Denied the funding we wanted? Good: we can learn to be more efficient.
- Mission we had been planning canceled? Good: more time to prepare.
- Client we were about to sign walked away? Good: focus on building better relationships with other clients.
No matter what goes wrong, some good can be found. Negative attitude spreads; so does positive. Leaders should maintain a positive attitude.
A leader can go too far. Positivity 100% of the time reads as Pollyanna who cannot see reality. Temper positivity with realism:
- Funding denied? Okay, this will take a little more time than we thought, but at least we can streamline and become as efficient as possible.
- Mission canceled? Not ideal, but we can rehearse details and be even more prepared.
- Client walked? Not what we wanted, but it gives opportunity to strengthen other clients and ultimately win more business.
Measured responses connect with the troops. If they think you are blind to the challenges, you lose credibility. Maintain a positive attitude; do not ignore problems; do not gloss over trials. Be positive, but be realistic.
Part Two map: Becoming a Leader covers the transition into the seat; Leadership Skills covers how to operate once you are in it.
Maneuvers
A. Using Leadership to Teach and Build
When someone is placed in a leadership seat, perspective changes and often reveals the errors of their prior ways. Putting people into leadership roles is one of Willink's most common remedies across a wide set of challenges. When mentoring, many different symptoms get the same basic medicine: put the person in a leadership position. Leadership cures an extensive assortment of problems.
i. Fixing a Negative Attitude
As a young officer and assistant platoon commander, Willink was friends with an assistant commander in another platoon who was searching for a solution, not merely complaining. One SEAL had unlimited potential: extremely smart, charismatic, athletic. After one deployment he was no longer a new guy and could have influenced the platoon positively. Instead he cut corners, complained about training, and carried a consistently negative attitude. Because of his gifts, that negativity was starting to sway others. Not good.
Willink knew the SEAL only casually: "too cool for school" face, everything below him. Hard to lead. The platoon commander, chief, and assistant had tried for months: verbal counseling (no change), weekend duty to "think" (no help), written counseling (seemed to make it worse). The assistant was at wit's end. Willink's suggestion surprised him: "Put him in charge."
Explanation: smart and charismatic means wasted talent; probably not challenged, bored; that may cause the attitude. Put him in charge of something so he steps up. The assistant agreed without confidence.
Weeks later, after Willink returned from a training trip: "Not good… He got worse." Responsibility had made the attitude more negative. That surprised Willink. As instructor cadre at SEAL Team One training, attitude cases put in charge of a training mission almost always straightened out or at least moved right. Second platoon: young enlisted trusted to plan and run operations; all stepped up with positive attitudes.
Then the clarifying question: "What did you put him in charge of?" Answer: cleaning the bathroom outside the hut and emptying trash daily. "Tasks weren't even that hard!" Wrong charge. For a guy with a platoon under his belt and real potential, bathroom detail is punishment for new-guy screwups, not leadership. Of course attitude worsened.
Recovery: take him off bathroom detail; tell him you see more potential; put him in charge of a mission. They had combat swimmer full-mission profiles that week (plan and execute scuba harbor attack from start to finish: dive, plant mines on target ship, extract). Perfect challenge. Within days Willink saw the SEAL in the hallway looking purposeful and determined: "Good to go." Next day the assistant debriefed: 180-degree attitude change; outstanding job overseeing planning and execution; few questions to Chief; all him; attitude stuck even when not running the next op; he supported the next guy.
Solidified lesson: one of the best tools to shape others is leadership itself. Give real responsibility. The more accurately you aim that tool, the more specifically you teach what each person needs.
ii. Teaching Humility
We want confident subordinate leaders; confidence easily inflates into arrogance. Fueled by success, ego gets out of control: believe own hype, stop listening, stop planning and preparing.
Life is the ultimate humility teacher for those who live long enough and take true challenges, but leaders often cannot wait for life. Willink's method: put the young overconfident leader in charge of a mission or project known to be outside their competency. Frame: "You've been doing such a great job; I want you to lead this." Arrogance usually accepts eagerly: finally where they think they belong. Mission is difficult, not impossible or unrealistic, hard enough that failure is likely.
Two outcomes after they take planning: (1) they see they are over their heads and ask for help (requires an ounce of modesty; arrogant people refuse help or think they can handle it); (2) they refuse help, fail, and get humbled by the face-plant. He would not let arrogance fail on real-world missions with lives at stake; training missions were different. Everyone got leadership seats in training; cocky people got the toughest ones and were humbled.
Business transfer: do not let arrogance fail with a major client or lose significant money. Set up training projects; lead low-consequence plans; stop them before harmful implementation. Sometimes an arrogant junior does not even know what a cohesive plan takes; attempting the plan is enough to humble them. No need for unnecessary risk.
If they do well anyway: do not be disappointed; high potential is good. Still need humility: harder mission, then harder, keep cycling until they fail or ask for help. Once humbled, rebuild confidence.
iii. Building or Rebuilding Confidence
Opposite problem, similar medicine. New to the seat and uncomfortable, or shaken by failure/poor performance: put them in charge of a mission you know they can lead and execute well; even fairly easy. They step up; positive result; then slightly tougher; then tougher. Confidence grows; then test with legitimately challenging missions.
Mitigate risk. Do not send the underconfident onto a critical mission: unreadiness can fail the team and bury their confidence deeper. Select missions/projects with enough pressure and low enough risk to force desired growth without overwhelming the person or risking the strategic mission. Too easy reads as a softball and reinforces their belief they are not good enough. Find the balance; apply the right pressure.
iv. Building High-Level Team Players
A person need not have a problem to benefit from leadership seats. Good leaders develop teams by putting juniors in charge so they become more experienced and knowledgeable.
In Willink's second SEAL platoon, the commander constantly put young SEALs in charge of training operations and evolutions. After planning full missions a few times, radioman work felt easy, and he understood how his planning piece fit the overall mission. He carried the tradition as an officer. As assistant platoon commander, with a senior officer grading a series of operations, he put the most junior petty officer, Freddie, in charge of the first: helped along the way, but Freddie owned the plan, prepared the briefing, and executed. Opening of the brief: grueling gut-check, complex, lots of moving pieces, significant coordination; "our youngest and most junior petty officer will be the ground force commander… Freddie, it's all yours." Senior officer's face: unexpected. Quietly: "Impressive. Risky, but impressive." Willink: "Negative, sir. Low risk. These guys know how to lead." Freddie did a great brief and a decent training mission.
Putting juniors in charge makes them understand levels above their pay grade and how their jobs tie to strategy. One of the best ways to develop subordinates into better performers and future leaders. Humility, confidence, and high-level team play are only some uses. Leadership is a tool to help your people. Use it.
- Negative attitude → real, challenging responsibility (never punishment chores dressed as "charge")
- Arrogance → hard stretch that forces ask-for-help or controlled training failure; escalate difficulty if they keep winning
- Low confidence → achievable then progressive challenge; avoid critical-mission risk and softballs
- High potential / no problem → early ownership to build strategic literacy
B. Leading Peers
Leading peers is one of the most challenging leadership types. Equivalent rank and position need more tact and an even better relationship. Once the relationship exists, influence leads the team. Influence is always preferred and especially critical among peers.
Influence is hard when rank is equal because egos become more visible. People look to prop themselves up and get an edge. If your ego manifests, you draw out the worst of theirs. Antagonistic peer relations become blue-on-blue (friendly fire): you destroy your own team. Subdue your ego first. Take the high ground.
Practices that build peer influence:
- Support their ideas when slightly different but functional. Let them take the lead. Do not chest-flex your plan. Even if you think yours is better, if theirs is close, go with it: dedication to their plan beats lackluster motivation on yours. Accepting their plan shows openness; they usually listen to you later. Improve shortfalls with them; do not take credit for the winning modification; give credit to them. That begins the relationship and raises influence.
- When assigning tasks, jump on the hard ones; shoulder heavy weight; own extra work. Dichotomy: stepping up for everything can look like a threat or power grab. Monitor reactions; if you sense toe-stepping, back off.
- When things go wrong, take responsibility and fix them (Extreme Ownership). Dichotomy: resolving every problem can also offend; stay aware of attitudes while you own and solve.
- If a peer's ego maneuvers to look good or make you look bad: do not fall into the ego trap; do not attack; continue great work; mission first. They may get initial positive attention; eventually they are uncovered. Take the high ground or the high ground takes you.
As you put team and mission before yourself, relationships form; relationships enable influence; that is leadership.
"Who would you hire?" / "Who would you promote?" Imagine two peer subordinate leaders, similar projects, both late. Leader A: materials late, subcontractors late, weather, shift conflicts: no ownership. Boss should be unhappy. Leader B: I ordered materials too late (will order earlier); I did not keep subcontractors on track (daily check-ins next time); no weather contingency (weekend make-up next time); shift crews not getting along (I will integrate proactively). Ownership and fixes. Whom do you promote? Obviously B. Yet working with peers, people often fail that connection: they blame openly, grab credit, think no one notices. Superiors and peers notice self-serving maneuvers. Sometimes the self-serving peer even gets promoted; that hurts; deal with it; do not get impatient; play the long game; truth reveals.
Do the right things for the right reasons. Support peers. Stay humble. Own problems. Pass credit. Build relationships. That is how you lead peers.
Blue-on-blue among peers is an ego fire. Equivalent rank makes ego more visible. If your ego shows, you draw theirs. Support close-enough plans so they own execution; improve quietly and give them the credit; take hard tasks without looking like a power grab; own failures without resolving every problem in a way that offends. When a peer plays to look good at your expense: do not attack; outwork; mission first; long game. The "who would you promote" test (blamer vs owner) is what superiors actually run, even when peers pretend nobody notices.
C. Micromanaging, Indecisive, or Weak Bosses
Bosses vary; some leave much to be desired. Common challenges:
Micromanager. Many reasons; primary is lack of trust. Build trust by giving all the information you can and then performing. Requires ego work: "I know what I'm doing; boss has no right to minutiae" is ego. Reframe: they want information because they care about the outcome; they prescribe methods because they have field experience and want you to benefit. Their picture is often based on what you tell them; incomplete picture is your under-brief. It is your job to earn trust, not theirs to gift it. Give more than they ask. Give plans in exacting detail so no questions remain. Repeated thoroughness shows you think through details as they do; leeway follows. Then perform. Execute their way when required; flawlessly follow minute directions. If something goes wrong, own it, brief the fix, fix it, get it right next time. Attitude will not change overnight; sustained performance; do not get frustrated; build the relationship; over time, trust and room to maneuver.
Indecisive on priorities. Common shortfall: hesitancy to Prioritize and Execute. Spread thin and nothing finishes. Team cannot focus without knowing what matters most. Usually works; accept minor or major corrections; leave with a prioritized list. If still "everything is priority," explain you cannot do everything at once and need an order to focus people and resources. If still stuck, agree, set priorities yourself to the best of your ability, and move. Quiet, subtle Prioritize and Execute; do not throw it in their face.
For decisions: tact. Not "since you haven't made a call, here's what I'm doing." More: "A lot going on; I want to be proactive toward your vision; thinking we should move this direction to hit your goal efficiently; does that make sense? If we don't move, we miss the timeline." Put the decision back on them made easy: complicated details already sorted; they can say yes; they remain the decision-maker; subordinate speech and attitude disarm ego; your plan appears as extension of theirs.
Weak / lackluster. "My boss is weak; it is horrible!" Willink heard that often. He saw opportunity: if they will not plan, clarify mission, take ownership, or lead: he will. Caution: even the feeblest bosses have egos; offense can trigger lash-out. Soft, ego-boosting frames:
- "You have a lot going on; helpful if I jump this project and move it?"
- "Sorry for being slow; want to make sure I fully understand your vision. Do I have it right when I say…"
- "Trying to step up my game; mind if I take a crack at planning the next project for experience?"
Tell them what you are doing and deciding, humbly and gently, so toes are not stepped on (power-play perception). With tact and ego in check, weak bosses are manageable.
Script patterns that work upward (ego-safe):
- Micromanager: over-brief detail before they ask; execute their prescribed method flawlessly when required; own misses with a fix plan; never sneer at their care.
- If still "everything," quietly Prioritize and Execute without theatrical defiance.
- Weak: "You have a lot going on; helpful if I jump this?" / "Confirm I have your vision: …" / "Mind if I plan the next one for experience?" Humble updates so it never reads as a coup.
Willink's summary stance: fine with all three. Micromanager = engaged and cares about a good job (shared). Indecisive = room to set priorities and guide decisions. Weak = room to step up and lead. Shortfalls aside: build the relationship; do what helps the team accomplish the mission; team wins and so do you.
D. When to Micromanage
Some of the smoothest operations Willink led as SEAL ground force commander needed only "Execute, execute, execute." External security, entries, breaches, clears, detainees, searches: zero further guidance. Why? Plan, SOPs, adjustments to mission goal, skills. Ideal: troops understand mission and parameters and can execute; leader sits back, looks up and out at what is outside the team's purview and at next moves. Decentralized Command at its best; opposite of micromanagement.
Hands-off does not always work. Micromanagement becomes necessary when an individual or group is not doing the job. Not first option. First: normal leadership: ensure understanding of mission, goal, specific role, task, expectations; positive and relationship-building. If that fails: more specific still-indirect confirmation ("confirm you understand your role and how it fits the strategic goal"). If still failing: very direct: exactly what and how. Then show it; perhaps do it so they see; monitor closely; follow up; micromanage. Depending on reaction, name it: "I know it seems like I am breathing down your neck; I want you to know exactly how to execute; once under control you get space."
As they get on track, back off a little; continued success → more room; slip → tighten again. Eventually, proper execution → run on their own.
Chance remains that even under close micromanagement they do not improve. Micromanagement is not permanent: leaders cannot focus all attention on one person or team indefinitely; other work slides. Unacceptable. Then clear notice: get up to speed or you will not have this job / be terminated; for a team, address its leader: get the team up to speed or you are removed as leader. If unmet: terminate or remove.
Micromanagement is a tool with limits; know when limits are reached; then remove or replace personnel.
Micromanagement as temporary corrective, not identity. The ideal remains Decentralized Command: "Execute, execute, execute" with the leader looking up and out. Micromanagement is the exception when understanding and indirect confirmation fail. Name it when you do it ("I am breathing down your neck on purpose until this is locked"), then return space as soon as performance earns it. Permanent micromanagement of one person destroys the rest of your span of control; that is when removal replaces oversight.
E. The Boss Wants All the Credit
If the boss wants all the credit, give it. Straightforward; hard only because of ego (you did the bulk, the hours, "everything"). Why should they get credit? Because they are the boss. They will get it whether you like it or not. Raising your hand to claim credit is a horrible move in any scenario; worse when the boss is asking for credit (likely insecure; credit builds their ego; taking it is an attack; distrust and antagonism follow).
Do not be jealous or bitter. Accept that whatever they did or did not do allowed the team to accomplish the mission: maybe they got out of the way; maybe they micromanaged like crazy. If success happened, it worked. Let them have the credit.
"What if they are not particularly good and individual contributors are the real reason?" Play the long game. Unless completely and utterly inept (mutiny path in Foundations), the devil you know with a good relationship can benefit team and you.
Fear they get promoted despite weak skill: true, repeated success often promotes them. Then they need someone trusted and supportive to fill the vacancy: humble enough to have let them have credit. If you played correctly, that person is you. Promotion is for the team: you can then lead and execute better and keep influencing the (now higher) boss for the team's good.
Fear you never get the credit you "deserve": check ego (main reason you want it). Relax. Hard work and results eventually bring credit. Unasked-for credit is doubly valued: competence plus humility. Put ego in check; give them the credit; humility and leadership rewarded long-run.
Credit and the long game, restated. Giving the boss credit is not surrender of truth; it is refusal to open an ego war you cannot win. Insecure bosses who need credit will punish claimants. Secure bosses notice humility later. Either way, repeated mission success often promotes the boss; the vacancy under them goes to the trusted supporter who never competed for the spotlight. That promotion is for the team's sake: you lead better from the new seat and keep influencing upward.
F. The Nearly Indefensible Leader
Always good to support your leader. Undermining hurts them, troop morale, and you as a subordinate leader. You set the example; disrespect up the chain invites the same from those you lead.
Presenting a plan you dislike as "I don't agree, but boss says so" is bad: they see you do not believe; then why should they; then why execute? Debate behind closed doors; once decided, execute as if your own: "Boss and I talked through this quite a while. From all angles, especially bigger-picture effects, I think this is the best solution.
Same attitude toward the person: boss may make imperfect decisions, be awkward, say wrong things. Troops may jab behind their back. Do not join; stop it. Not blind sword-falling; explain load and role: "boss has a lot on his mind"; "job is to run the company, not keep us entertained." Respect for the job remains.
Nearly indefensible cases: egotistical, arrogant, condescending, repeated bad decisions. Blind defense puts you at odds with the team and hits your credibility. Open belittling leads to complete disrespect and failure of good order. Balance defending with connecting. Mission-first phrases:
- "Boss might not be perfect, but he is driving us toward the same strategic goals we want."
- "Might not be ideal, but she still gives support we need; better we perform, more support we get."
- "Complaining doesn't get us anywhere or make jobs easier; form a good relationship so we can influence her in the right direction."
These balance unconstrained backing and visible hesitation.
Truly impossible to defend (rare): illegal, immoral, unethical, or decisions that put mission or troops at real risk → consider going above in the chain; absolute rarest cases → mutiny (Foundations).
G. Stress Relief
Almost every job creates stress: angry clients, criminals, physical hazards, unruly students, deadlines, hostile customers. When people succumb, it is extremely bad for individual, team, and mission. Prevention starts with what leaders should already do: build relationships. Good relationships up and down the chain are among the most important success elements; one reason is stress management. Talk; they talk; you listen; decent chance they disclose inordinate stress.
They may not: embarrassment, promotion fear, unrecognized symptoms (never felt it before). Another reason relationships matter: you know them, so you know when they are not themselves: less talkative, easily aggravated by little things, disheveled. Behavior change can signal stress.
Major Dick Winters (2nd Battalion, 506th PIR; Band of Brothers / Beyond Band of Brothers): sign a man was reaching breaking point was helmet off, head buried in hands. Visually obvious: enough. Treatment: temporary duty away from the front, framed as a rear task that needed doing, not "you need rest" (shame would make them refuse). Willink as platoon and task unit commander: logistics run to HQ for a few days, or liaison with a unit in a relatively nice area. "Important task; I trust you," not "you're cracking." Operational downtime; return recharged.
Best treatment for combat stress and any stress: remove from the inducing environment. After rest, usual return to normal. Mind under stress ≈ Check Engine light: can run a while; needs service; push without service → catastrophic burnout. WWI shell-shock film: pushed to the limit without relief; broke; no longer able to function. Do not allow that. Know them. Watch them. When they need a break, give it.
Winters' signal, Willink's practice. Helmet off, head in hands = approaching break. Treatment framed as needed rear work, not pity, so shame does not block acceptance. Logistics run to HQ, liaison in a quieter sector, "important task I trust you with." Best treatment for combat stress and ordinary overload: remove from the inducing environment long enough for the Check Engine light to clear. Push without service and you get shell-shock outcomes: people who can no longer function. Know them so you see the change before they name it.
H. Punishment
Punishment must be dealt at times; good leaders need it seldom. Clear guidance on what, how, why, and consequences should produce execution. If troops do not execute, look in the mirror first: do not assume willful refusal; assume direction failed.
If a rule was violated or direction not followed even though understood, some punishment must be meted. Should be rare if leadership is working. Need to punish almost always reflects the leader's failure to lead appropriately: Extreme Ownership. Late → maybe importance of punctuality not explained. Incomplete project piece → maybe support not given. Alcohol/police trouble → maybe drinking parameters unclear. Leader always responsible for subordinate actions; extend further: preempt troublemakers by removing them.
Even with Extreme Ownership eliminating most failures to follow rules, negligence, malice, or willful disobedience happen. Punish when lines are crossed: lines must be clearly defined and understood. Punishing unwritten rules is usually inappropriate unless behavior is grievous enough any reasonable person would deem it out of line. Counsel bad judgment; formal punishment without clear documented rules is poor practice. Also lay out consequences for violations: no one should be surprised; knowing the risk eliminates much need.
Once rule and punishment are clear and the rule is broken: administer. Circumstantial consideration and mercy are not weakness; sensible clemency is understanding, not being a pushover. Willink weighed infractions against historical performance: great record + uncharacteristic → slack; habitual → full punishment; no legitimate reason or mitigating circumstances → hold the line as defined. Less appealing part of leadership; sometimes necessary. Better you lead, less you need it; still sometimes need it. Deliver with justice.
I. When to Quit
SEAL mantra "Never quit" is a main BUD/S refrain and makes sense there: that is how you make it through and become a SEAL. In the Teams the extreme attitude must be modulated or it leads to disaster.
Classic failure: young leader, "never quit" ingrained, builds a marginal training-mission plan from inexperience, briefs, executes, plan proves ineffective (bad route, wrong approach, underestimated resistance, weather, any variable). He will not give up; presses; expends all resources, energy, time; mission fails; squad spent or compromised, unable even to support another mission. Wrong. He should have quit, returned to base, reformulated, rested troops, reloaded for another shot.
Training problem Willink ran: urban building, long hallway, multiple rooms, large end room with a barricaded shooter: massive paintball gun, virtually unlimited ammo, bunkered in sandbags/plywood pillbox, barrel through a small hole down the hallway. Platoon tasked to clear. Leader's standard plan: two into hallway for first room, then two for next, and so on. First two enter → gunned down → "dead." Leader peeks, sees them, calls "Give me two more!" Next two slaughtered. Four piled up. "Two more! Go!" Six dead. Sees the silhouette; announces barricaded shooter; still "Two more! Go!" Continues until only he remains; charges; dies in a blaze of glory. Whole platoon dead. Team failed. "At least he didn't quit?" Wrong.
Debrief: objective not achieved; everyone dead; never want that again. Difference between strategic and tactical objectives: okay to quit a tactical plan that is not working, especially when not quitting destroys ability to reach the strategic objective. Dead platoon = zero strategic value.
Next iteration (same or similar building): first pairs die again; if he stays the course, intervene. "You're doing the exact same thing." "We need to clear this building / hallway." Force the connection: quit this plan; already lost four (in real life: gone); rethink. "I can't just run away." "Detach. Look around. Other options? Windows into the end room?" Flank: fire teams external; grenade simulators; enter windows; eliminate shooter. New (actually old) approach: flanking maneuver. More important: okay to quit.
Better word than quit: retreat. Not giving up completely; not surrendering; giving up on one approach that is not working to try another. Tactical = immediate fight here and now. Strategic = broad long-term overall objective. Okay to quit a tactical objective (hill, city sector) if enemy too strong and cost in men/matériel too high: bypass or defer. Do not quit the strategic mission (e.g., remove a tyrannical leader who threatens regional stability and your nation's safety).
Sometimes tactical quit is necessary for strategic success: Washington's retreat of Continental forces from New York, crucial to fight later; Gallipoli abandonment after extensive Allied casualties, freeing evacuated troops for other theaters toward eventual strategic victory; Dunkirk: over 300,000 Allied troops evacuated across the Channel to live and later defeat Axis powers.
Sometimes quit the short-term tactical goal. Never quit the long-term strategic goals.
- Tactical = the fight here and now (hallway, hill, sector, this week's plan)
- Strategic = the broad long-term aim (clear the building; remove the threat; win the war)
- Quit / retreat from a failing tactical plan when pressing it destroys the force needed for the strategic aim
- Never quit the strategic mission; re-form, rest, reload, and try another approach
- Better word than quit: retreat (abandon one approach to try another; not surrender)
Historical pattern Willink cites: Washington's New York retreat kept the Continental Army alive to fight later; Gallipoli abandonment after heavy Allied casualties freed troops for other theaters toward eventual strategic victory; Dunkirk evacuated roughly 300,000 Allied troops across the Channel so they could live and later defeat Axis powers. In each case, tactical withdrawal served strategic persistence.
The young SEAL leader who presses a failing training plan until the squad is spent is not "never quitting." He is quitting the strategic objective by destroying the only tool that could achieve it. Detach. Look for windows. Flank. Reload.
Communication
A. Keep the Troops Informed
SEALs move long distances by air and boat, but the final approach to a target is usually a foot patrol: fifty to seventy pounds of gear at minimum, up to about 120 pounds, often at night over hard terrain, alert for enemy. Movies make it look like a walk in the park. It is not.
At SEAL Tactical Training (STT) after BUD/S, Willink walked every role: heavy machine gunner, medic, point man, rear security, patrol leader. Order of march in a squad: point man, patrol leader, radioman, first machine gunner, medic, second machine gunner, assistant patrol leader, rear security. Position dictates information.
- Point man: hardest physically (breaking trail) but knows everything: map, paces, terrain features, distance remaining.
- Patrol leader: works with point; map studies at rest stops (ten minutes each hour); bearings and triangulation.
- Radioman: near the patrol leader for external nets; hears map talk and position reports; stays informed.
- First machine gunner onward: progressive disconnect. Farther back means less overheard discussion. Tail-end troops barely know where they are, when the next rest comes, or what terrain is ahead. Morale drops. Tactically worse: if attacked or separated, they are lost. Knowing location is the most important battlefield fact, and they do not have it.
Willink hated the bag-over-the-head feeling at the rear. As patrol leader, then as officer (squad, platoon, task unit), he made it his mission that everyone knew what was happening: reinforce signal-passing in briefs; brief the route and identifiable terrain; at each rest stop walk the map to each man or team leader (where we are, how far to target, what terrain next); check water, feet, fatigue. Comfort mattered; tactical soundness mattered more. Informed troops stay engaged and capable. Uninformed troops are a disaster waiting to happen.
Transfer to any organization: when people do not know where they are, where they are going, or how long to the objective, they are lost. They cannot connect effort to strategy. Morale plunges. Hardest leadership truth: the team does not see what you see. Assuming they have your information is careless. Be proactive. Update continually. Do not wait for questions (they may not know what they do not know). Assume they know nothing; take responsibility to keep them informed.
Patrol rest-stop ritual as a leadership habit. At each halt: map to each man or team leader; where we are; how far to target; terrain next; water; feet; fatigue. Comfort is one payoff; tactical readiness is the real one. Uninformed rear troops do not know where to go if attacked or separated. The same ritual in business: stand-ups that locate the team on the plan, not only assign tasks.
B. Rumor Control
If rumors run rampant, you created the environment: lack of information. Silence is filled with invented versions, and those versions are ugly.
Get the word out ahead of rumors. Layoffs? Explain why. Discontinue a product? Tell why. Shut an office? Communicate the reason. These talks are uncomfortable; silence feels easier. People notice anyway and invent: layoffs become "we are going out of business"; product kill becomes the same; office shut makes it "certain."
Attack rumors by getting ahead of bad news. Be truthful, direct, timely. The longer you wait, the larger the rumor and the harder the recovery. Quicker truth is better received and creates fewer problems.
C. Clear Guidance
If subordinate leaders or frontline troops are not doing what you want, check yourself first. Most likely cause: unclear or misaligned guidance.
Make guidance simple, clear, concise. More guidance is not clearer; excess can confuse. Align guidance across levels: details differ by layer; the underlying message must match.
Ramadi rules of engagement. As Task Unit Bruiser commander, ROE documents were pages of legalese ("enemy military and paramilitary forces," "reasonable certainty… legitimate military target"). Fine for a mature reader in comfort; hard for a young shooter under combat stress deciding life or death. Willink translated: "If you have to pull the trigger, make sure the person you are killing is bad." Suspicion is common; the clear line is when someone takes hostile offensive action against coalition forces. Then they are bad and must be engaged. He also explained why ROE mattered: killing or injuring an innocent civilian would damage the whole campaign; the mission was to protect civilians; harm to them was contrary and unacceptable.
Do not only ask "Do you understand?" (people nod to avoid admitting confusion). Ask them to explain the guidance back in their own words. Quiz with scenarios. Propagate through many channels: written, face-to-face, video they can rewatch, conference calls, subordinate leaders repeating. Different people absorb differently.
ROE simplification as a guidance template. Pages of legalese → one clear line the shooter can use under stress → plus why (civilian harm wrecks the campaign). Then verify by playback and scenarios, not nods. Propagate in writing, face-to-face, video, calls, and through subordinate leaders. Alignment across levels matters as much as simplicity: details may differ; the underlying message must not.
D. Because I Said So
Parents shout "Because I said so" about rooms, curfews, dishes, helmets. Used carelessly, the same language migrates to employees. It is wrong with children and wrong at work.
Helmet example (Southern California skate culture). "Wear a helmet because I said so" works only while you watch. Alone with friends, helmets are hot, uncomfortable, uncool: off they come. "Because I said so" carries no weight in your absence. Explain dangers; show a hospital bed with brain damage or a grave of a child who died from a skateboard head injury: then the why sticks, and she may even police friends.
Workplace forms of the same failure: "It's my call," "This is my project," "I outrank you." None produce best effort: people carry out orders without enthusiasm or tenacity because they do not understand why.
Explain why a task, maneuver, or procedure matters: to the team, company, mission, and to them. Another reason to avoid "because I said so": you might be wrong. If the only answer you have is rank, you may not know why you are doing the thing. Then why are you doing it?
Tech hardware launch. Undermanned company racing a first major project. Willink told engineers: if you do not understand why you are doing a task, ask your supervisor; if they do not know, ask theirs; keep going up. To the CEO: do you want anyone working on something if no one in the chain can explain why it matters? CEO: absolutely not; with this much work, every person must be on critical tasks. If no one can explain importance, stop doing it.
Explaining why enables execution with understanding and stops wasted work. If you catch yourself saying "because I said so," stop, assess, give a real reason.
E. The Thread of Why
After Willink addressed a large workforce on Laws of Combat and Extreme Ownership, the CEO announced the company had turned profitable for the first time in two years and shareholders were happy. He expected cheers. He got awkward silence. In the debrief he was confused: cut expenses, removed unneeded personnel, explained the why (profitability), delivered results. What was not to like?
Willink owned failing to review the speech. The facts were good from the CEO's seat. From the troops' seat:
- "Cut costs" → you removed supplies and resources we needed.
- "Got rid of unneeded personnel" → you fired my friends; we are more undermanned.
- "Profitable for shareholders" → someone else makes money off our sacrifice.
The message needed a thread that connects the why back to them:
We were profitable for the first time in two years → more money into advertising → more leads → more customers → more sales → lower unit cost → more competitive price → more sales again → more advertising capacity → growth → long-term job security, increased responsibility, leadership opportunity, more pay. When the company succeeds, every member succeeds. Thank you for the hard work.
The CEO got it; they built an email and video to retie the thread.
Lesson: explaining why is not enough if the why ends at "corporate" or "shareholders." Frontline people care when profit means their security and growth. Military parallel: explain not only national strategy but impact on them: disrupt mortar attacks on our base; dent enemy intel and staging; stop them on their turf so they never reach ours and our families stay safe.
No matter the goal, troops need to see how it positively impacts them. Make the Thread of Why explicit.
F. Tactfully Delivering the Truth
Criticism punched in the face produces defense, not learning. Use consideration and delicacy, built on real care (they can tell) and real ownership.
Ownership-framed feedback (believe these; they are true):
- Not "You failed to finish on time" → "What support or assets could I have given you so we could have finished on time?"
- Not "You failed the mission objective" → "I do not think I explained the objective well. Did you fully understand it?"
- Not "Your lack of professionalism lost the client" → "I think I allowed professionalism to get too slack, and that is one reason we lost that client."
If the leader follows up on support, explains simply and confirms understanding, and emphasizes professionalism, outcomes change. Willink's answer to "When is the leader not fully responsible?": never. Non-performance means the leader has not trained, mentored, prioritized training, escalated for support, or removed the incapable.
Ownership spreads. Ask "What support could I have given?" and the subordinate often answers: "I could have used one more person, but if I had planned better and used hours better we would have finished. It will not happen again."
If indirect critique fails, escalate directness without personal attack:
- "This is your project; I trust you to drive on-time completion. What else do you need?"
- "You led this mission; we missed the objective. Did you not understand it and its importance? What can I do to ensure 100 percent understanding next time?"
- "I allowed slack. As a leader you need to hold the line too. Lack of professionalism will not cut it."
Further escalation: warn of write-up; then written counseling with problem, expectations, corrective measures, consequences. If still unmet: remove from the seat or from the team.
- Ownership question (what support did I fail to give?)
- Direct role ownership ("this is your project; what else do you need?")
- Warn of written counseling
- Written counseling: problem, expectations, corrective measures, consequences
- Remove from seat or team
G. Balancing Praise
Task Unit Bruiser CQC workup: live fire, live breaches, live sniper shots; strong leadership; midlevels fresh from combat; humble new guys; Laws of Combat in use. Kill-house runs went well; mistakes owned and fixed; team rallied around strugglers.
Near end of week two, a massively complex multi-building problem: chaos grabbed and controlled. Debrief: senior instructor, respected master chief: "This is the best task unit we have ever had come through here! You guys are absolutely crushing this!" Hoots. Willink shuddered walking past: "I wish you hadn't said that. They are going to let down their guard." Master chief: "They'll be fine." He was not.
Next run: unmitigated disaster. Missed targets, uncleared corners, bad head counts, bogged assaulters, eternal clearance. Instructors hammered mistakes; none named the real cause. Willink: you got complacent; you took the compliment to heart; you lost humility; me too; now go annihilate the target with aggression, precision, vengeance, zero slack. They locked and loaded and performed.
Lesson relearned across his career: too much praise (consciously or not) makes people ease effort; times a whole team, negative impact. Dichotomy: give praise when warranted, judiciously, tempered with a next goal. Instead of bare "best task unit ever," add: "and if you push harder you will set a new standard; shave another two minutes." Something to strive for.
Opposite failure: never-satisfied leader who moves the goalposts every time. Morale dies; people stop full effort because they never "win."
Willink's mitigation: praise individuals, not blanket team glory. "Mike, nice job on the obstacle room. Jim, outstanding marshalling civilians. You three locking the backside: awesome." Recognition required an A game. After retirement he heard guys had hunted his compliments; when earned, they chased them again. Multiply that across a team.
Willink's post-retirement feedback confirmed the system: guys had hunted his compliments, felt they earned them, then chased them again. Multiply that across a whole team and results speak. Blanket praise is cheap dopamine; earned specific praise is a renewable standard.
Praise is a tool: too much → rest on laurels; too little → lost hope. Fading morale → well-placed compliments; overconfidence → a few critical remarks. Your words move behavior more than you think. Measure them.
H. Hope
"We hope the weather holds." "Hopefully the enemy has no sentries." "Hoping competitors ignore that market." Military line: hope is not a course of action. Plan. Contingencies. Stack the deck. Do not let hope play a role in planning or execution.
Hope does play a role in leading and winning. It must live in hearts and minds of people executing. No hope for relief, success, or victory → will cannot endure → surrender.
Sustain hope: explain that victory is possible and how; if victory is distant, designate shorter-term wins so the team feels it can win. When victory is impossible but retreat is not an option: explain that driving on in the face of defeat is a victory of reputation; each member carries that into the next chapter with head high. That attitude is hope enough to fight on.
Hope dichotomy, restated. Hope in the plan = malpractice. Hope in the people = leadership duty. Short-term wins keep hope alive when the strategic win is far. When the fight cannot be won but cannot be abandoned, redefine victory as reputation and head-held-high transition to the next chapter. That is enough to keep the will from surrendering.
I. Ultimatums
Ultimatums are not optimal. Like digging in, they leave no room to maneuver. No one likes being trapped. Extremely rare times: when enough is truly enough. Then hold the line. Never make an ultimatum you cannot keep.
i. Making an Ultimatum as the Boss
First ask: where did my leadership fail? Solid leadership (why, benefit to the team) should get what you need. Ultimatums are last resort after coaching, mentoring, and persuasion fail.
Once delivered, an ultimatum cannot be reversed; people feel trapped; failing to keep it destroys credibility. Make requirements and consequences explicit; ensure full understanding.
Even rarer on whole teams: some will adjust, some will not; you cannot cleanly sort who tried. If you must ultimatum a collective effort, place it on the team's leader. They deliver or not and bear repercussions; they know who onboarded; if the team fails, you know exactly whom to deal with.
ii. Making an Ultimatum as a Subordinate
An ultimatum up the chain is a threat and power play: high risk. Classic: "Promote me or I leave." Most bosses hate it. Better: diagnose why you are not promoted (performance, peers, seniority, freeze, unreadiness). Demanding promotion rarely works; even if it works, you revealed loyalty limits and put self above team. Remembered.
Prefer legitimate discussion without ultimatum. Rare exhaustion case: frame as a warning, not a trap. Gentle example after years of right moves: love it here; family to support; other opportunities exist; if no upward mobility I may have to look, though I do not want to. Many bosses still take offense. Do it only if you must, and only if other opportunities are real. Same caution for support, pay, equipment, funding: the sting up-chain is almost always the same.
iii. Dealing with an Ultimatum Placed on You
Boss ultimatums usually mean other tools failed and the demand is near-impossible. Response: tell the truth.
- Truth to yourself: is it possible? Are you making every effort? If you can do more, redouble.
- Truth to the team: the ultimatum is on us; here is why we dig in.
- If you deliver: acknowledge, move on.
- If maximal effort is still not enough: gather what would make it possible (people, funding, dropped competing tasks); tell the boss you cannot meet it as stated; describe needs and consequences of denial.
Humble bosses may modify. Ultimatum-prone bosses may not. Then: knuckle down, protect the team, suffer consequences with head high. No spite, no bad attitude, no disparagement, no giving up. Dignity and troop morale are the victory.
J. Reflect and Diminish
Leaders must control emotions without being devoid of them. Direct and modulate; sometimes show emotion to connect or make a point.
Subordinate storms in, red-faced: "This is ridiculous! Supply missed delivery two weeks running; we will miss the deadline!" Do not say "calm down": that inflames, opens a chasm, and shuts their mind.
Reflect and Diminish: reflect the emotion you see, at a lower intensity, so you become an ally and the heat steps down.
- Reflect (raised but less than theirs): "You've got to be kidding! How late are they?"
- They: "Two days!" (still mad, less venom)
- Diminish further: "Two days is way too long. We need to fix that permanently. Also: how can I help you fix the predicament you are in?"
Now you solve the problem. Works across emotions: sadness, envy (mirror a little, then name the ego), humor (chuckle, then steer to seriousness without looking humorless). Works up the chain as well as down. Foster shared emotion; de-escalate; solve. Reflect and Diminish.
K. When to Yell at Subordinates
Almost never. Yell for volume (noise, large group) is not emotional yelling. Yelling from anger, frustration, panic is weak leadership; the team mimics: your anger, frustration, panic become theirs.
If they do not understand, yelling is wrong: the articulation failed. Calm down; different approach; ask what they miss; have them explain what they think they understand; clarify until it lands. Patience earns more respect than temper.
Calculated yelling: extremely rare. Willink yelled few times in twenty years; each left a mark; never from lost temper; only after multiple calm failures to convey seriousness. Escalation path: note the rule break → second time, explain why the rule exists → maybe a third calm pass → then private, quick, direct, aggressive yell: "You did this again; absolutely unacceptable; I will not tolerate this again. Ever." Then controlled growl: "Am I perfectly clear? Do you understand?" Shock, fear, understanding. Because it was the first yell they had ever seen from him, seriousness landed. He never had to yell at the same person twice.
Even calculated yelling can look like lost control. Alternative escalation: threaten write-up, then write them up. Equivalent impact for many. Chronic non-changers: document and remove.
Count-on-one-hand rule: if you yell weekly, you are not escalating; you are managing by fear and training people to wait for volume. If you yell once in years after clear calm passes, the rarity is the message.
L. Getting People to Listen
When people interrupt or talk over you: let them talk. Let them finish. Cure for someone who needs to talk is letting the thoughts out; then you can make your point. Bonus: you now know what they know; you can form counterpoints and recommendations. In groups, listening while others argue and detail ideas gives you the most comprehensive picture; when you speak, your statement is the most developed.
The less you talk, the more people listen. Do not talk just to talk. Speak when needed. Absorb; then deliver the impactful line. Even simple articulated approval can outweigh blather. Do not waste words. Speak with poignancy and power.
Listen-first influence. Let interrupters finish; their dump empties the need to perform and hands you their full map. In a room of competing ideas, silence while others argue is not passivity; it is intelligence collection. When you finally speak, one precise statement outweighs a session of filler. Waste no words; make others waste theirs if they must.
M. Apologizing
Leaders who treat apology as weakness are usually weak and insecure. Apology after a mistake is ownership, especially when you left someone out, overlooked them, or disrespected them: then apology is the right thing.
If apologizing for a decision: pair with explanation: what you saw, how you read it, what you expected, what happened, how you prevent repeat. Then apologize if you mean it. Do not apologize for every slip with no major negative result. If you feel you owe one, give it.
If you truly think you were not at fault: you still are, in Extreme Ownership terms. Disarm blame by owning, then move to the solution.
Willink struggled to find cases where apology was bad. He was not scared to apologize; he owned his mistakes and others' unowned mistakes. Willingness to take the hit was part of why he kept landing in leadership seats. Recommend the same.
Apology paired with decision explanation. What you saw; how you read it; what you expected; what happened; how you prevent repeat; then the apology if warranted. Skip apology theater for slips with no real harm. When ego says "not my fault," Extreme Ownership still finds the piece you own; owning it disarms blame-hunters and clears the path to the fix. Willink could barely invent a case where apology was bad; willingness to take the hit was part of why he kept getting the seat.
N. Be Approachable but Careful with Words
Chasms form: physical separation, pay/socioeconomic gaps, rank. Close them: spend time in the field, offices, jobsites; do not flaunt money or ski vacations; do not let rank kill conversation. Talk work and life, family, future. Know them. Relationships surface brewing issues; that is how you read true climate.
There is still a line. Do not become too familiar, casual, unguarded. Gossip, sarcasm, flippant remarks from a leader land too hard. Harmless ribbing among friends can wound a subordinate. Critique preferably private to preserve dignity; team-wide reviews of mistakes should target the mistake, not the person's potential.
Words intensify enthusiasm or crush spirits. Be judicious about what, to whom, and how.
O. Set the Example
The team watches attitude and behavior; they miss nothing: late to a meeting, eye-roll, yawn (tired, bored, or both). They imitate: your lateness, sloppy dress, rule-breaking, calm, panic, negativity, positivity, respect, humility, professionalism.
Willink knew because he was the youngest and most junior in his first two platoons: they always watched the bosses. Closely watched leaders cannot cover mistakes. Admit, own, explain prevention. Do not lie; they see through it.
You are being watched. In everything, set the example.
Conclusion: It Is All On You, But Not About You
It is all on you
As a leader there are no excuses and no one else to blame. You have to:
- Make decisions
- Build relationships
- Communicate so everyone can understand
- Control ego and emotions
- Detach
- Instill pride in the team
- Train the team
- Stay balanced, tactful, and aware
- Take ownership
The list continues. Leadership is an incredibly complex undertaking. Do those things well and the team succeeds and the mission is accomplished. Fail to lead effectively and you fail, and the team does not accomplish the mission.
Leadership is all on you.
But it is not about you
At the same time, leadership is not about you. Not at all. Leadership is about the team. The team is more important than you are. The moment you put your own interests above the team and above the mission is the moment you fail as a leader. When you think you can get away with self-serving maneuvers, when you think the team will not notice, you are wrong. Your people will see it, and they will know it.
How to use this book
The strategies and tactics in this book are not tools for personal career advancement. Use them so the team can be successful. Use them for your own agenda and eventually they backfire and bring you down: you fail as a leader and as a person.
Use them to help others and to help the team accomplish its mission, and the team succeeds. When the team succeeds, you win as a leader and as a person. Infinitely more important: your people win.
That is true leadership.
Main Points
Main Points
- All on you, not about you: own every outcome; never use leadership tools for a private agenda.
- Detach first: step out of the emotional blast radius before you decide, speak, or dig in.
- Relationships are the operating system: influence beats rank; build trust down, up, and sideways.
- Play the game without selling your soul: work the system for the mission; mutiny only for illegal, immoral, or mission-destroying lines.
- Born and made: talent helps; deliberate practice, study, and owned reps make leaders.
- Subordinate your ego: credit up and out; blame in; ego noise is not mission data.
- Tell the truth early: sandbagging upward and sugarcoating downward both fail the team.
- Be capable and ask for help: competence earns the right to lead; asking for help is not weakness.
- Extreme Ownership everywhere: preempt problems; own when blamed; pick up brass; lead from the rear when that serves the fight.
- Do not overreact; do not care (about ego): calm beats drama; ignore status games that do not move the mission.
- Span of control and the most important member: design teams so leaders can lead; the "most important" seat is contextual, not a permanent crown.
- Discipline is care: imposed discipline without ownership fails; pride and clear orders beat hope.
- No yes-men: dissent inside, alignment outside; the rare "bad team" exception does not erase leader responsibility.
- New leaders: earn, do not announce: succeed quietly; handle not being chosen; crush imposter theater with competence.
- Do not go Rambo: filling every vacuum and crowding every leader destroys Decentralized Command.
- Do not dig in; decide iteratively: leave room to maneuver; small reversible steps beat frozen pride.
- Decentralized Command ≠ lazy designation: Intent, checkbacks, and support; not dumping and disappearing.
- Leadership-as-medicine: real challenge for attitude; hard stretch for arrogance; achievable wins for low confidence; early ownership for high potential.
- Lead peers by ego suppression: support close-enough plans; own failures; long game over blue-on-blue.
- Manage up with information and soft frames: micromanagers need trust fuel; indecisive bosses need your prioritized list; weak bosses need your step-up without a coup vibe.
- Micromanage as a temporary corrective: then return space, or remove the person when oversight cannot be permanent.
- Give credit up; defend without lying: nearly indefensible bosses get mission-first framing, not open belittling; illegal/immoral lines still escalate.
- Quit tactics, never strategy: retreat from the hallway of death; flank; reload; hold the strategic aim.
- Keep the troops informed: walk the map to the rear; starve rumors with timely truth.
- Thread of Why: connect every task to a frontline benefit, not only to shareholders or "because I said so."
- Critique through ownership, then escalate: believe the ownership question; climb the ladder to write-up and removal if needed.
- Balance praise: specific and earned; blanket glory crashes the next run.
- Hope in hearts, not in plans: hope is not a course of action; it is fuel you sustain with short wins.
- Ultimatums are last resort: keep them if you issue them; prefer warnings and options up the chain.
- Reflect and Diminish; yell almost never: cool heat; rarity makes volume mean something.
- Listen more; apologize cleanly; set the example: the less you talk, the more they hear; behavior preaches louder than briefs.
Frameworks and mental models
| Name | What it says | Use it when |
|---|---|---|
| All on you / Not about you | Own outcomes; serve team/mission | Careerism vs stewardship; tool misuse |
| Detach | Emotional distance before action | Anger, ego fights, cascading crises |
| Laws of Combat (ref) | Cover/Move, Simple, Prioritize, DC | Planning and execution under load |
| Extreme Ownership | Leader owns everything in the mission | Blame storms, missed targets |
| Preemptive Ownership | Own before the failure lands | Known risks, weak handoffs |
| Trust down / up / DC | Information and performance buy leeway | Micromanager; Decentralized Command |
| Span of control | Limits on direct reports | Overloaded boss; flat org chaos |
| Leadership-as-medicine | Dose responsibility to the symptom | Attitude, arrogance, confidence, development |
| Vacuum protocol | Pause, then fill; don't bunch up | Leadership voids; too many chiefs |
| Don't dig in | Keep an out; advance the best idea | Plan wars; ego stalemates |
| Iterative decision-making | Small reversible steps | Fog, incomplete intel |
| Easy Button | Stop being the team's shortcut | Learned helplessness under you |
| Tactical quit / strategic hold | Retreat from failing plans | Hallway of death; sunk-cost presses |
| Thread of Why | Tie task → mechanism → frontline benefit | Profit speeches; "because I said so" |
| Critique escalation ladder | Ownership → direct → write-up → remove | Performance problems |
| Reflect and Diminish | Mirror emotion lower; then solve | Hot subordinates or bosses |
| Patrol information gradient | Rear knows least unless you walk the map | Uninformed teams; rumor fuel |
Who's who
| Person / unit | Role in the book |
|---|---|
| Jocko Willink | Sole authorial voice; SEAL enlisted then officer; Task Unit Bruiser commander; Echelon Front co-founder |
| Leif Babin | Teammate; co-author of Extreme Ownership / Dichotomy; Echelon Front partner (context) |
| Task Unit Bruiser | Ramadi task unit; CQC praise crash; ROE simplification; many combat transfers |
| Freddie | Junior petty officer put in as ground force commander on a graded training op |
| Negative-attitude SEAL | Bathroom detail vs combat-swimmer FMP case (leadership-as-medicine) |
| Dick Winters | WWII airborne leader; helmet-in-hands stress signal; temporary rear duty |
| Master chief (CQC cadre) | "Best task unit ever" praise that preceded a kill-house disaster |
| Anonymized CEO (profit speech) | Thread of Why failure then retie (shareholders vs frontline growth) |
| Tech hardware CEO / engineers | "Because I said so" / ask-up-the-chain why test |
| Peer Leader A / Leader B | Blamer vs Extreme Ownership peer; who would you promote |
| Point / patrol leader / radioman / rear | Patrol information gradient cast |
About this book
Leadership Strategy and Tactics: Field Manual by Jocko Willink, 2020. This is a chapter-by-chapter study of the book, with summaries, maps, tables and diagrams; short quotations keep their page references. It is shared free for personal study, is not for sale, and is not endorsed by the author or publisher. Please read and buy the original.
Insight Editions · rajeshrmahapatra.com/insight-editions