Published in 2013, the book tells the story of Marquet’s command of the USS Santa Fe, a Los Angeles-class nuclear-powered submarine ranked dead last in the Pacific Fleet for performance, crew retention, and morale when he took over. Roughly a year later, with the exact same crew — the same people who’d been producing last-place results under different leadership — the Santa Fe had become one of the best-performing submarines in the fleet. Marquet didn’t pull this off through personal charisma, better people, or some outside intervention. He did it by fundamentally rewiring the relationship between authority, information, and decision-making throughout the submarine’s organization — systematically replacing a system where people waited for instructions with one where people exercised judgment, took ownership, and held themselves accountable.
The Wrong Ship and the Moment That Changed Everything
The book’s conceptual origin is a story of institutional randomness that turned out to be a gift, oddly enough. Marquet had spent a year mastering every technical detail, operational procedure, and strategic nuance of the USS Olympia — the submarine he expected to command. Reactor systems, weapons systems, navigation systems, its history, the specific quirks separating it from other boats in the fleet — all of it. Two weeks before he was set to take command, the assignment changed. The Olympia went to another officer, and Marquet got the Santa Fe instead — a completely different class of submarine he’d studied only in the most general terms.
That created an immediate, unavoidable problem. The conventional model of submarine command depends on the Commanding Officer being the most technically knowledgeable person aboard — the expert at the top of the hierarchy who can authoritatively answer any question that comes up. Marquet was not that person. He was commanding a vessel whose systems he knew worse than officers who’d served aboard it for months or years. The normal foundation of authority — superior knowledge expressed through confident direction — had been kicked out from under him before he even set foot on the boat.
The moment that crystallized the problem hit during an early training exercise, when Marquet gave an order to the Officer of the Deck, who relayed it to the helmsman. The helmsman started to execute — then stopped. Hesitated, in a way that made it obvious something was off. The Officer of the Deck quietly told Marquet the order was technically impossible on the Santa Fe — the capability he’d ordered was standard on the Olympia but simply didn’t exist on this class of submarine. Marquet had given a nonsensical order. And the helmsman, who’d known immediately it made no sense, had started executing it anyway. Not from lack of intelligence. Not from lack of knowledge to spot the problem. Because the system he operated in rewarded compliance over judgment, and executing orders was simply what subordinates did.
That moment exposed the fundamental flaw of the leader-follower model with a clarity no theory could have delivered. The people on the submarine held knowledge their commanding officer lacked. The system demanded they suppress that knowledge and execute authority’s directives rather than exercise their own judgment. On a nuclear submarine — where errors range from mission failure to catastrophic physical disaster — that isn’t an efficiency problem. It’s a safety and performance problem of the most serious kind there is. And Marquet realized it wasn’t unique to that one moment. It was the inherent logic of the whole system he’d inherited.
The Leader-Leader Model
Marquet’s alternative — developed not from theory but from practical necessity, in real time, with real consequences on the line — is what he calls the leader-leader model. The premise: every person in the organization should be developed to the point where they can make good decisions within their own area of responsibility, and the commanding officer’s actual job isn’t to be the decision-maker but to create the conditions that make distributed, high-quality decision-making possible across the whole organization. Two conditions have to be present for this to work safely: competence, meaning enough technical knowledge to make good decisions about the specific situation faced, and clarity, meaning enough understanding of the organization’s goals, values, and priorities that individual decisions tend to align with collective purpose on their own.
The practical rollout started with a single language change that seemed superficial at first and turned out to be anything but. Instead of the standard Navy formula “Request permission to…” — through which subordinates asked for authorization before any significant action — Marquet trained the crew to say “I intend to…” followed by a brief statement of reasoning. The surface change is vocabulary. The real change is the entire structure of who holds initiative and who bears responsibility for outcomes.
Old model: “Request permission to submerge to four hundred feet.” The CO now has to evaluate that request against everything he knows about current conditions, mission parameters, tactical situation, then authorize or refuse. Decision-making authority sits at the top. The subordinate contributed information but withheld judgment. New model: “I intend to submerge to four hundred feet. We’ve reached the test depth marker on schedule, the water temperature gradient is favorable for our current mission profile, and I’ve confirmed no scheduled contacts in the area.” The CO’s role isn’t to authorize — it’s to listen for any gap in the officer’s reasoning. No gap, silence is authorization, action proceeds. The subordinate owns the decision. Owns the reasoning. Owns the outcome. The CO becomes a quality check rather than the source of decisions.
Building Competence from the Bottom Up
The “I intend to” model is only safe if the people using it genuinely have the competence to exercise the judgment it demands. Handing decision-making to people who lack the knowledge to make good calls isn’t empowerment. It’s abdication — and on a nuclear submarine, abdication can be catastrophic. Which meant the leader-leader model was never primarily about changing who made decisions. It was primarily about building the technical knowledge and situational understanding across the whole crew that would make distributed decision-making safe enough to actually pursue.
Marquet went after this with specific, deliberate practices. He pushed technical training further down the organization than was typical, making sure junior sailors understood not just how to execute procedures but why the procedures existed in the first place — what they accomplished, what conditions would make them inappropriate, what signs should make someone stop and question rather than plow ahead. That’s a qualitatively different kind of knowledge than procedural knowledge. Procedural knowledge produces reliable execution under standard conditions. Understanding produces adaptability — the ability to recognize when conditions have stopped being standard, and respond appropriately instead of continuing to execute a procedure that no longer serves its purpose.
He also rebuilt how certifications and qualifications worked, making them more substantive and genuinely demanding rather than box-checking rituals. A sailor certified for a particular watch station had to demonstrate real understanding, not just procedural compliance. The bar was real, and people were expected to clear it before getting trusted with the decisions it protected. That combination — genuine expectation of competence, paired with genuine trust once competence was demonstrated — created a developmental environment where people were motivated to build real capability rather than just perform the appearance of it.
Clarity: The Other Essential Condition
Competence alone doesn’t make the leader-leader model work. The second essential condition is organizational clarity — shared understanding of mission, values, and priorities deep enough that decisions made independently by hundreds of individuals tend to reinforce each other rather than collide. Without that clarity, distributed decision-making just produces chaos: people making technically competent choices that serve their own local situation but conflict with the organization’s broader needs.
Marquet built clarity through a practice he calls “briefings up” — a total inversion of the conventional military briefing flow. In traditional briefings, the commanding officer or a senior staff member briefs the organization on what’s happening, what the plan is, what everyone’s expected to do. Information and direction flow downward. In Marquet’s approach, junior officers and crew members briefed him — laying out what they understood the mission to be, what they planned to do to execute it, and what considerations had shaped their thinking. His job was listening for misalignment and asking questions that surfaced gaps in understanding — not correcting people, but helping them see what they might have missed.
The reversal served two functions at once. It revealed, in real time, whether the clarity that was supposed to exist actually did — whether each person operating in a distributed decision-making environment genuinely understood the mission and priorities well enough to make aligned choices on their own. And it reinforced, at a psychological level, the entire orientation of the leader-leader model: the person briefing upward is already in the posture of someone who owns the decision, has thought through the reasoning, and is prepared to act and account for it. The person receiving a briefing downward is in the posture of someone preparing to execute someone else’s decision. That gap in ownership isn’t incidental.
The Permission Culture and Its Costs
One of the more psychologically interesting parts of the Santa Fe transformation was the resistance Marquet ran into from the crew itself — not hostility, exactly, but the genuine difficulty of changing habits of mind trained deeply over years of military service. The sailors and officers aboard had been selected, screened, and trained to operate a specific way: receive orders, execute precisely, ask permission before doing anything outside explicit prior authorization. Not laziness. Not passivity, either — a sophisticated, demanding skill set the Navy had spent years developing. But a skill set built on a fundamentally different premise about who was supposed to think and who was supposed to act.
Changing that took more than telling people they were newly empowered to exercise judgment — it required building the specific conditions that made it psychologically safe to actually do it. The fear driving a permission culture is rational: act without authorization and the action goes wrong, full responsibility lands on you. Ask for authorization first and it goes wrong anyway, responsibility spreads upward. The incentive to wait for permission rather than exercise judgment is powerful when the organizational culture has consistently punished unauthorized errors harder than it’s punished unauthorized inaction. Reversing that takes demonstrating, through specific responses to specific situations over time, that honest good-faith errors get treated as learning events rather than career-damaging failures.
Marquet did this deliberately, and kept doing it. When mistakes happened — and they did, as they inevitably will in any organization genuinely experimenting with distributed decision-making — he steered the post-incident review toward what the situation had actually required and what could be learned, rather than who’d deviated from authorization. The goal wasn’t eliminating accountability. It was redirecting it: from accountability for getting permission toward accountability for getting outcomes, from accountability for procedural compliance toward accountability for the quality of judgment exercised in applying or adapting procedure to real conditions. Sounds subtle on paper. The practical effects were not.
Avoiding the Short-Term Leadership Trap
The pull of “I” leadership is real and shouldn’t be underestimated. Giving clear orders feels like leadership. Handing someone the answer when they bring you a problem feels productive, feels helpful. Solving it yourself is usually faster than helping someone work through it. Short-term, these behaviors produce better immediate outcomes in the exact situations where they’re applied. Long-term, they produce an organization that can’t function without the CO’s continuous direction — an organization whose collective capability is bounded by one person’s individual capacity, which is always smaller than the collective capacity of an organization full of genuine leaders.
Marquet’s response to this trap was deliberately training himself to ask questions instead of hand over answers. Officer brings him a problem, his default becomes “What do you think?” instead of “Here’s what to do.” Someone proposes a course of action, his default becomes “Walk me through your reasoning” instead of “Approved.” Slower, in the moment. But it produced something fast answers never could: subordinates who’d exercised judgment, articulated their reasoning, gotten honest feedback on the quality of it, and built genuine capability in the process. The time invested in each interaction compounded into organizational capability no amount of fast direction-giving could ever build.
The Results That Validated the Model
The numbers from Marquet’s command are the proof of concept giving the theory its credibility. Under him, the Santa Fe finished its operational deployment successfully and with distinction. Reenlistment rates, among the lowest in the fleet before, became among the highest. The submarine’s standardized assessment scores went from dead last to among the highest in the Pacific Fleet. Those numbers alone tell a compelling story.
But the most remarkable outcome was one Marquet hadn’t specifically chased and couldn’t have fully anticipated: how many Santa Fe officers went on to command their own submarines afterward. In the years following his command, an unusually high share of the officers who’d served under him became commanding officers themselves. The leader-leader model hadn’t just improved one submarine’s performance during one command tour. It had grown a cohort of leaders who carried its principles forward and multiplied its effects across the whole fleet. The return on investment wasn’t bounded by Marquet’s own tenure — it compounded through the careers of everyone developed under the model.
Which is the deepest argument for the leader-leader model. Its benefits aren’t purely organizational, aren’t limited to one unit’s performance during one period. They’re developmental — they build human capability that outlasts any specific organizational context and keeps generating returns for years and decades after the original investment. An organization applying the leader-leader model consistently over time creates a pipeline of genuine leaders — people who’ve actually exercised judgment under real conditions and learned from the results — that no amount of training or development programming can replicate at the same depth.
Applying the Model Beyond the Navy
Marquet is thoughtful, appropriately humble, about how well his specific practices translate to civilian organizational contexts. The military environment carries features — the gravity of physical risk, the clarity of command structure, the culture of disciplined execution, the professional commitment of a career military officer — that don’t have direct equivalents in most businesses, nonprofits, or government agencies. What worked on the Santa Fe was developed for that specific environment, and applying it wholesale, unmodified, to a software company or a hospital or a government bureau would be naive.
But the underlying principles — decision-making quality improves when authority moves toward the person closest to the relevant information, that requires genuine investment in both technical competence and organizational clarity, the transition requires sustained change in who’s expected to exercise judgment versus who’s expected to check quality — translate across contexts with remarkable fidelity. An organization wanting to build distributed leadership capacity has to be willing to seriously invest in developing the competence that makes it safe. It has to ensure clarity about mission, values, and priorities runs deep and genuine enough to align independent decisions without constant top-down direction. And it has to build a feedback culture treating honest good-faith errors as developmental events rather than grounds for blame.
The question Marquet leaves the reader with is one anyone can apply right away: when someone on the team brings a question about what they should do, what’s the response? Default to telling them — providing the answer, making the decision, giving the direction — and dependency is what’s getting built. Default to asking what they think, engaging with their reasoning, and capability is what’s getting built. The first feels more productive in the moment. The second is more productive over any time horizon past the current conversation. Every leader gets to choose which one wins, many times a day, and the accumulated choices decide what kind of organization actually gets built.
The Language of Intent
One of the more immediately actionable takeaways is the power of language in shaping psychological ownership. The shift from “Request permission to…” to “I intend to…” isn’t merely stylistic — it reorients the entire psychological posture of whoever’s speaking. The person asking permission has externalized decision ownership. The person declaring intent has internalized it — thought through the situation, reached a conclusion, prepared to act and be accountable for the outcome. The declaration invites challenge and dialogue while holding onto the ownership that enables genuine learning once the outcome gets assessed.
Marquet found this language shift one of the fastest-acting changes he made aboard the Santa Fe. Unlike culture changes that take years to show up in behavior, the shift in language produced visible effects within days, because it forced officers to prepare before opening their mouths. Declaring intent required reasoning that could survive scrutiny. That preparatory work was itself developmental — it forced deeper engagement with situations before acting, and produced articulated reasoning that could be examined and sharpened over repeated iterations.
Measuring Lasting Performance, Not Just Current Performance
Marquet draws a distinction between two ways of measuring leadership effectiveness that cuts to the heart of why leader-follower organizations persist despite their limits. The first measure is immediate performance: how’s the unit doing while this leader’s in command? That’s the dominant, nearly universal measure in organizational systems — current results, current scores, current outputs. Easy to track, easy to reward, and leaders who optimize for it get recognized and promoted constantly.
The second measure is lasting performance: how does the unit perform after the leader leaves? Does the successor inherit an organization more capable than the one the leader received — one that can sustain and build on what got established? Or do they inherit an organization that was performing because of one specific person’s presence and direction, and starts struggling the moment that person moves on? This second measure almost never gets tracked and almost never gets explicitly rewarded — but it’s a far more accurate read on genuine leadership quality. The leader who produced great immediate results while building dependency optimized for recognition during their own tenure at the cost of the organization’s long-term capacity. The leader who produced great immediate results while building distributed capability created compounding returns that reach well past any single command period.
The Courage to Challenge What Works
Maybe the most underappreciated part of Marquet’s achievement is the specific courage it took. The Santa Fe was ranked last — the existing model’s failure created pressure and lowered the risk of trying something different. But Marquet wasn’t just rescuing one failing submarine. He was challenging an institutional model that worked adequately across an entire service branch, implying the standard approach was limiting every submarine it touched. That claim demanded a willingness to be publicly wrong in a professional culture where public error carries real consequences.
The broader lesson concerns innovation inside functioning systems. The hardest changes aren’t the ones needed to save an organization that’s clearly failing — failure generates its own pressure and justifies the disruption on its own. The hardest changes are the ones needed to make an already-adequate organization significantly better, because adequacy is a continuous argument against disrupting whatever appears to be working fine. The leader who sees that a functioning system is nevertheless limiting performance, and has the clarity and nerve to challenge it while it still looks fine from the outside, is the rarest and most valuable kind there is.
The Importance of Genuine Certification
Marquet is unusually specific about one piece of his implementation that’s easy to gloss over in summary: the deliberate investment in making certifications and qualifications genuinely demanding rather than procedurally compliant. In plenty of organizations — military and civilian alike — qualification processes turn into box-checking exercises over time. The form of certification survives while the substance quietly drains out under the accumulated pressure to certify people fast, keep staffing levels up, and avoid the organizational friction of genuinely failing someone who’s close to a standard but not quite there.
On the Santa Fe, Marquet insisted qualifications actually mean something. A sailor certified for a watch station had to demonstrate real understanding, not just procedural compliance. The technical knowledge needed to support distributed decision-making had to be genuine, not performed. That commitment to authentic certification built a development environment where the growth of real capability was expected, supported, and recognized — where the gap between what someone could currently do and what the standard required was treated as useful information for development rather than a problem to manage away. The certification became a genuine landmark instead of a bureaucratic hurdle, carrying meaning purely procedural certifications simply can’t generate.
What Turn the Ship Around Offers Every Organization
The book’s setting — a nuclear-powered submarine in the United States Navy — is exotic enough that some readers might underestimate how directly its lessons apply to their own organizations. The fundamental dynamics Marquet documents aren’t specific to military hierarchies or high-stakes physical environments. They’re fundamental to how human beings respond to authority, to how capability develops (or atrophies) under different leadership conditions, and to how the design of decision-making systems shapes both the quality of individual decisions and the development of the people making them.
Any organization where people regularly bring problems to leaders who hand back solutions rather than developing the asker’s own capacity to find solutions is running the leader-follower model — whatever the values statement says about empowerment. Any organization where people wait for direction before acting, because acting without direction has been punished often enough that waiting is the rational, self-protective choice, is running a permission culture — whatever the leadership development curriculum says about initiative. Any organization where a key leader’s departure produces a performance crisis had a leader building dependency rather than capability, however excellent the performance metrics looked during their tenure.
Spotting these patterns in an organization is the starting point for the kind of deliberate change Marquet documents. Not easy change — it demands sustained investment in developing the competence and clarity that make distributed decision-making safe, sustained consistency in changing the language and behavior that shape who holds initiative, and sustained patience with the slow work of building the psychological safety that lets people exercise judgment without constant anxiety about punishment for honest error. But the evidence is clear about where that investment leads: to organizations where the collective capability of all the people consistently exceeds what any single leader, however excellent, could ever have produced alone. That’s the ultimate promise of the leader-leader model, and the Santa Fe’s climb from last to best is the proof of concept that makes the promise credible.
The Accountability Structure That Enables Distributed Leadership
One practical piece of Marquet’s model that’s easy to overlook amid all the talk of empowerment is the accountability structure that makes distributed decision-making safe and sustainable. The “I intend to” formulation isn’t only about pushing initiative downward — it’s simultaneously a commitment to transparency. When an officer declares intent with reasoning attached, they’ve created a record of their decision process that can get reviewed afterward. That builds a form of accountability actually more thorough than the accountability in a pure authorization system, where the authorizing officer bears formal responsibility but may have rubber-stamped an approval without fully engaging the subordinate’s reasoning at all.
When the subordinate owns the decision — articulated the reasoning, got no objection, proceeded on their own judgment — they’re genuinely accountable for the outcome in ways that build real professional development. An officer who makes a poor decision they owned, one that led to a bad outcome, has a specific, learnable lesson: the reasoning was flawed in a specific, identifiable way, and fixing that reasoning improves future outcomes. An officer who just executed an order that produced a bad outcome has a much fuzzier relationship to the failure. The accountability structure of the leader-leader model, in other words, isn’t merely permissive. It’s developmental. It creates conditions where genuine learning from experience is possible, because the causal chain between individual judgment and outcome stays transparent instead of getting buried inside the authorization process.
The Sustainable Legacy of Intent-Based Leadership
Marquet’s influence has reached well past the Navy and well past the immediate circle of military and organizational leadership readers who first found the book. Intent-based leadership has been adopted and adapted across sectors — technology companies building agile development teams, healthcare systems trying to improve front-line clinical decision quality, educational institutions trying to build teacher judgment rather than teacher compliance, manufacturing operations chasing faster, better front-line problem-solving. In every case, the adaptation means working out what competence and clarity actually mean in that specific context and building the sustained investment in both that makes distributed authority genuinely safe. The specific mechanisms vary a lot by context. The underlying logic — the people closest to the work hold critical information leaders at a distance simply can’t have, and building their capacity to act well on that information is the highest-use investment any leader can make — translates with remarkable consistency across all of them.
The book’s most important legacy might be its contribution to how a whole generation of organizational leaders thinks about what they’re actually doing when they lead. If leading means directing — providing answers, making decisions, telling people what to do — then leadership is fundamentally bounded by one leader’s individual cognitive capacity. If leading means developing — building competence, creating clarity, establishing the accountability culture that lets everyone in the organization exercise excellent judgment independently — then leadership is fundamentally unbounded. The second conception asks a lot more of a leader than the first, because it demands genuine investment in other people’s development rather than confidence in one’s own capacity. But it’s the conception that produces organizations capable of greatness, rather than merely capable of competently executing a smart leader’s instructions.
Related: Indistractable Summary
Related: Supercommunicators Summary
Related: Educated Summary
The Practical Framework: Applying Turn Ship Around Summary In Real Life
NOT JUST READING ABOUT IT ›
Join the Wolf Pack — mentorship and accountability for men who are done thinking about change
References
Editorial StandardsCorrectionsMedical DisclaimerAbout Our ContentAffiliate DisclosureSite Map