微信扫一扫Turn the Ship Around
Overview
Turn the Ship Around, developed by former submarine captain David Marquet, documents the transformation of USS Santa Fe from worst-performing to best-performing submarine in the fleet by inverting the traditional leader-follower model. The core insight: the best organizations don't create followers, they create leaders at every level. Intent-Based Leadership challenges the fundamental language of hierarchical command ("I request permission to...") by replacing it with distributed authority ("I intend to..."). Marquet discovered that moving authority to where the information lives - rather than moving information to where authority sits - unlocks initiative, ownership, and organizational excellence. The framework rests on three pillars: Control (distribute decision-making), Competence (build technical mastery), and Clarity (ensure organizational alignment). What made Santa Fe remarkable wasn't just performance improvements, but that a disproportionate number of its officers went on to become submarine commanders themselves - the organization created leaders, not just results.
When to Use
- Transforming hierarchical organizations where information flows up but decisions trickle down slowly
- Breaking dependency on heroic leadership where one person becomes the bottleneck
- Developing next-generation leaders who can think independently and take ownership
- Improving decision quality by empowering people closest to the information
- Increasing organizational resilience when key leaders are unavailable
- Building culture of ownership where people don't wait for permission to act
- Scaling leadership capacity beyond what single leader can provide
The Process
Step 1: Shift the Language from "Permission" to "Intent"
Replace request-based language with intent-based language. Instead of "I request permission to submerge the ship," train people to say "I intend to submerge the ship." This linguistic shift forces both leader and team member to think differently - the team member must think through the decision, and the leader must resist reflexive control. Start with low-stakes decisions to build the muscle. Example: Junior engineer announces "I intend to deploy the hotfix to production at 2pm" rather than asking "Can I deploy at 2pm?" Forces engineer to think through timing, risk, rollback plan rather than outsourcing judgment to manager.
Step 2: Give Control, Don't Take Control
Identify where decision-making authority currently sits versus where information lives. Systematically move authority down to where information exists. Resist the temptation to centralize decisions during stress - this is when distributed control matters most. Make it psychologically safe to exercise control by celebrating good decisions, not just punishing bad ones. Example: Instead of operations manager making all incident response decisions, train on-call engineers to make calls directly. Manager shifts from decision-maker to coach reviewing decisions afterward.
Step 3: Build Technical Competence
Recognize that you can't give control without competence - it's abdication, not empowerment. Invest heavily in training, certification, and mastery development. Create deliberate practice opportunities where people can build skills in progressively challenging scenarios. Ensure people understand both "how" (technical execution) and "why" (underlying principles). Example: Before giving junior developers authority over deployment decisions, require them to complete disaster recovery drills, understand rollback procedures, and explain the architecture dependencies of what they're deploying.
Step 4: Achieve Organizational Clarity
Ensure everyone understands the mission, objectives, and strategic intent. People can't make good decisions without knowing what success looks like. Communicate "commander's intent" - the purpose and desired end state, not just the tasks. Test clarity by asking people at all levels to explain the "why" behind their work. Example: Instead of telling customer support "resolve tickets quickly," clarify "our mission is customer retention, and every interaction is an opportunity to build loyalty or lose it - speed matters, but resolution quality matters more."
Step 5: Implement "Certify, Don't Brief"
Replace passive briefings (where leader is briefed by subordinate) with active certifications (where subordinate must demonstrate mastery). Before giving someone control, certify they have both technical competence and understanding of organizational intent. Make certification real - if they can't demonstrate mastery, they don't get control yet. This protects against premature delegation. Example: Before engineer leads infrastructure migration, require them to walk through the plan, identify failure modes, explain rollback procedures, and answer "what if" scenarios. Not a slide presentation - a technical interrogation proving they've thought it through.
Step 6: Practice "I Intend To" Responses
Train leaders to resist solving problems when someone brings them up. Instead of giving answers, ask "What do you intend to do?" or "What's your recommendation?" Push decision-making back down while providing guidance. When someone says "I intend to X," resist immediately approving or rejecting - ask questions that help them think through the decision. Example: Direct report: "We're over budget on the marketing campaign." Manager resists "Here's what we should do..." Instead: "What do you intend to do about it?" Forces ownership rather than dependency.
Step 7: Create Leader-Leader Culture
Model the behavior at every level - senior leaders practicing intent-based language with executives, middle managers with senior leaders, all the way down. Celebrate examples where people exercised good judgment independently. Address situations where people reverted to asking permission when they should have stated intent. Make "creating more leaders" an explicit organizational metric. Example: CEO tells board "I intend to acquire Company X" rather than asking approval. Board's role shifts from approving/rejecting to asking questions that test CEO's thinking. Models distributed authority at highest level.
Example
USS Santa Fe Transformation: When Marquet took command of Santa Fe, it was the worst-performing submarine in the fleet - failed inspections, low morale, poor retention. The previous captain had been relieved for performance issues. Marquet's planned submarine assignment changed, so he arrived knowing little about Santa Fe's systems - traditional command-and-control wouldn't work. During early drills, Marquet gave an order for "ahead two-thirds" speed - except Santa Fe's reactor couldn't do two-thirds, only ahead one-third or full. His officers were about to execute an impossible order rather than question it. This crisis became the catalyst: if officers wouldn't challenge bad orders, the ship was dangerous. Marquet started giving control to the team. Within months, Santa Fe went from worst to first - highest retention, best inspection scores, and crucially, produced more future submarine commanders than any other ship. Ten years later, the effects persisted even after Marquet left - the leader-leader culture became self-sustaining.
Anti-Patterns
Giving control without competence: Delegating decisions to people who lack technical mastery or understanding of organizational goals. This isn't empowerment, it's abdication leading to poor decisions and eroded confidence. Fix: Build competence first through training and certification before distributing control.
Taking back control during stress: Reverting to command-and-control when stakes are high. This teaches people that intent-based leadership is performance art, not real. Exactly when you want to take control is when you most need to resist. Fix: Explicitly coach through high-pressure decisions rather than making them yourself.
"I intend to" as theater: Adopting the language without shifting authority. People say "I intend to" but still wait for approval before acting. Linguistic change without cultural change. Fix: Hold yourself accountable for whether people actually feel empowered to execute their stated intentions.
Clarity without specificity: Vague mission statements that don't actually help people make decisions. "Be customer-focused" doesn't tell someone whether to refund an angry customer or enforce policy. Fix: Test clarity by asking people to apply organizational intent to specific decision scenarios.
Punishing mistakes from good decisions: Someone exercises good judgment, makes a defensible decision with available information, but outcome is bad - and they get punished. Kills intent-based leadership faster than anything. Fix: Evaluate decision quality based on information available at decision time, not outcome-based hindsight.
Skipping certification: Assuming people are competent without testing. Then surprised when distributed decisions go poorly. Fix: Make certification rigorous and real - demonstrate mastery, don't just attend training.
Related Frameworks
Team Topologies (Skelton & Pais): Describes organizational structures that enable autonomy. Turn the Ship Around provides the leadership model for making those structures work through distributed authority.
Radical Candor (Kim Scott): Focuses on feedback quality. Intent-Based Leadership creates the ownership culture where radical candor becomes essential - people need honest feedback to build competence for distributed control.
OKRs (Objectives & Key Results): Provides the clarity mechanism. OKRs clarify organizational intent, enabling people to make aligned decisions independently. Turn the Ship Around explains why that clarity is critical.
Extreme Ownership (Willink & Babin): Both frameworks emphasize ownership, but different mechanisms. Extreme Ownership pushes responsibility up to leaders; Turn the Ship Around distributes authority down to create leaders at every level.
The Five Dysfunctions of a Team (Lencioni): Addresses trust and accountability. Intent-Based Leadership builds trust by giving control and builds accountability by making people own their stated intentions.
High Output Management (Andy Grove): Grove's framework for managerial leverage through delegation. Turn the Ship Around takes delegation further - not just task assignment but authority distribution.