Turn the Ship Around!
A submarine captain's account of giving up the one thing every leader is taught to protect, being the person who gives the orders, and turning the worst-performing submarine in the fleet into one of the best by making every sailor think like a captain instead.
Find this on the mind-map
Introduction
David Marquet took command of the USS Santa Fe, a nuclear submarine with a demoralized crew and one of the worst retention and performance records in its fleet, and inherited a leadership model he'd been trained in his entire career: leader-follower, where the captain thinks and the crew executes. His account of what he changed isn't really about submarines. It's about what happens when a leader stops being the single point of thought for an entire organization, and starts building an organization where everyone thinks.
Leader-Leader, Not Leader-Follower
The traditional model treats competence as something concentrated at the top. The leader knows best, so the leader decides, and everyone else's job is to execute well. Marquet's alternative treats every person in the organization as capable of leadership-level thinking about their own piece of the work, with decision authority pushed down to whoever actually has the relevant information. On a submarine, that's rarely the captain, who's often several decks and several steps removed from the actual gauge, valve, or sensor in question.
"I Intend To," Not "Permission to..."
The specific mechanism that made this real, not just aspirational, was a change in language. Crew members stopped asking "Captain, may I..." and started saying "Captain, I intend to...", stating their plan, their reasoning, and then executing once the captain either confirmed or redirected. The shift looks small. Its effect isn't: asking permission keeps the thinking with the person who grants it, while stating intent keeps the thinking, and the ownership, with the person doing the work. The captain's role changes from decision-maker to check, which is a much faster and more scalable position to occupy.
Control Requires Competence and Clarity First
Pushing decision authority downward without first building the technical competence to use it well, and the organizational clarity about what the mission actually requires, just produces confident, badly-informed decisions faster. Marquet's model has three legs, not one: give people competence (real technical mastery of their area), give them clarity (a genuine understanding of the organization's purpose and priorities), and only then give them control. Skip either of the first two and the third one backfires.
Deliberate Action Beats Rushed Reflex
Under a submarine's version of pressure (depth, speed, timing, systems everyone depends on working correctly) the crew adopted a practice of verbalizing an action before performing it: say what you're about to do, out loud, before you do it. This simple pause catches a surprising number of errors before they happen, because stating an intended action out loud forces a half-second of actual thought that a purely automatic, practiced motion skips.
A Culture of Watching for Each Other, Not Watching Each Other
Picture two crews under the old and new models facing the same unexpected mechanical fault. Under leader-follower, a junior sailor who notices something slightly off waits for someone senior to notice it too, because flagging it isn't clearly their job and being wrong carries real cost. Under leader-leader, the same sailor says what they intend to check and why, immediately, because the culture has made it clear that competence and initiative are rewarded, not just compliance. The fault gets caught in minutes instead of hours in one version, and that's the entire difference the book is actually about.
Putting It Together
None of this was a motivational speech or a new org chart slide. It was a specific, repeatable set of mechanisms (a language change, a competence-then-clarity-then-control sequence, and a habit of verbalizing intent) that converted a crew trained to wait for orders into a crew that each, individually, thought and acted like the person in charge of their own piece of the mission.

Why It Matters for Leaders
The usual failure mode for a leader who wants to delegate more isn't malice, it's habit. Someone brings you a problem, and answering it feels like the helpful thing to do, because you probably can answer it faster than they can solve it themselves. What that habit actually trains is a team that brings you every problem forever, because solving it was never really their job to begin with.
The language shift is the part worth stealing even if nothing else changes. "What do you intend to do?" takes the exact same two seconds as "here's what you should do," but it keeps the thinking with the person who has to live with the decision. Said often enough, it stops being a trick and starts being how the team actually operates: people show up with a plan, not a question.
None of this works as a one-time announcement that the team is "empowered now." Pushing decisions down before people have the competence and the context to make them well just produces fast, confident, bad calls, and a leader who gets burned by one of those usually swings back to deciding everything personally, which undoes the whole experiment. The sequence matters: build the skill, explain the actual priority behind the work, and only then hand over the decision.
Picture an engineering manager, Priya, whose on-call engineer pages her at 2 a.m. about a production issue and asks, "should I roll back the deploy?" The old habit is to just say yes or no from bed. The better response is "what do you intend to do?" If the answer shows real reasoning, she says "sounds right, go ahead," and goes back to sleep. If it doesn't, she's just found a gap in competence or clarity worth closing in daylight, not a decision she needs to keep making for them at 2 a.m. forever.
What to do next
Reinforce your understanding of Turn the Ship Around!
Books related to Turn the Ship Around!
Coaching for Performance
Sir John Whitmore's foundational case for coaching-style management over command-and-control, built on a single idea: performance is limited less by skill than by interference, and a manager's job is to remove the interference, not supply the answer.
Elevate
Robert Glazer's case, from his book "Elevate: Push Beyond Your Limits and Unlock Success in Yourself and Others," that performance isn't a willpower problem. It's a capacity problem across four specific domains, built like a muscle, not willed into existence overnight.
First, Break All The Rules
A large-scale look at what the best managers actually do differently, and the uncomfortable finding that most of it runs against conventional management wisdom, starting with the idea that you shouldn't try to fix people's weaknesses.
Multipliers
Liz Wiseman's case that the biggest lever on a team's output isn't headcount or talent density, it's whether the leader in the room makes people smarter or slowly makes them smaller.
Team Topologies
Skelton and Pais's case that most team structures are drawn to fit an org chart, not the actual flow of work, and a small set of team shapes and interaction rules for fixing that, built around a resource every leader habitually overspends: people's cognitive load.
The Coaching Habit
Michael Bungay Stanier's pitch that most managers have an "advice monster" problem, and a short list of deceptively simple questions designed to starve it, a little at a time, in conversations that already happen every day.
The First-Time Manager
The unglamorous, practical handbook for the specific week your job title changed and nothing else came with instructions. Less a framework, more a set of answers to the questions new managers are usually too embarrassed to ask out loud.
The Five Dysfunctions of a Team
Patrick Lencioni's pyramid of the five behaviors that sink teams without much notice, stacked so that each one is actually caused by the dysfunction beneath it, which means fixing results or accountability first almost never works.
The Making of a Manager
Julie Zhuo's field notes from becoming a manager in her twenties with no idea what the job actually was. A clear-eyed answer to the question most new managers are too embarrassed to ask out loud: what am I actually supposed to be doing all day?
The Manager's Path
Camille Fournier's map of the actual career ladder from doing the work to leading an organization of leaders, written for engineering managers, but mostly a clear-eyed account of how the job itself changes at every rung, which almost nobody explains to you before you climb it.
Skills related to Turn the Ship Around!
Frameworks related to Turn the Ship Around!
Dunning-Kruger Effect
Knowing little makes you feel unstoppable; knowing more makes you hesitate — the loudest voice is rarely the most reliable one.
Goldilocks Principle
Support runs on a dial between micromanagement and abdication — enough direction for clarity, enough space for ownership, always moving.
Hawthorne Effect
People change how they behave when they know they're watched — your attention is an intervention that changes what you see.
Maslow's Hierarchy of Needs
Abraham Maslow's five-level model of motivation, applied to leadership as a stack — mastery, trust, belonging, up through recognition and vision.
McKinsey 9-Box Model
A 3x3 grid that plots each person on performance against potential, giving nine distinct calls instead of one blurry verdict.
Multipliers and Diminishers
Liz Wiseman's split between leaders who bring out best thinking in people around them, and those who shut it down.
Situational Leadership
There's no right way to lead — only the right way for this person right now: direct, coach, support, or delegate.
The 6 Human Needs
Every behavior at work is really an unmet need in disguise — six needs, popularized by Tony Robbins, worth checking first.
The Architecture of High-Performing Teams
Six elements, built like a temple — culture as the base, four pillars, vision as the roof — name the missing piece.
The Bannister Effect
One person breaking a barrier makes it stop being fixed for everyone else — break the unspoken belief in public first.
The Five Dysfunctions of a Team
Lencioni's pyramid of five team-killing behaviors — a lack of trust at the base drags everything above it down.
The Inner Drive
A leadership take on Daniel Pink's *Drive* that turns three conditions for motivation — autonomy, mastery, purpose — into habits for 1:1s.
The Pygmalion Effect
What you expect from someone leaks into how you treat them, which shapes what they become — for better or worse.
The Thomas-Kilmann (TKI) Model
Five conflict styles, two dials — how hard you push, how much room you give — chosen on purpose, not by default.
Tuckman's Stages of Team Development
Every team moves through five predictable stages — forming, storming, norming, performing, adjourning — each demanding a different move from you.