Turn the Ship Around!

Summary

The Santa Fe's transformation from the Navy's worst-performing submarine to its most celebrated proves that the most counterintuitive leadership principle works: giving up control creates more control. When Captain L. David Marquet took command of this nuclear submarine, he faced a crew so demoralized that they had the worst retention rate in the fleet and a culture where sailors mindlessly followed orders without thinking. His accidental discovery—giving an impossible order that his crew tried to execute anyway—forced him to abandon traditional "leader-follower" hierarchies and build what he calls the "leader-leader" model. Marquet's approach centers on two fundamental mechanisms: Control (moving decision-making authority to where the information lives) and Competence (ensuring people have both the technical knowledge and organizational clarity to make good decisions). Rather than the traditional submarine command structure where the captain makes every decision, Marquet began asking "What do you think we should do?" instead of issuing orders. When his sonar supervisor requested permission to submerge the ship, Marquet replied "What's your intention?" This simple linguistic shift transferred ownership of the decision back to the person with the most relevant information. The results were immediate: crew members began thinking critically about their actions rather than simply executing commands. The Santa Fe's performance metrics skyrocketed—from worst to first in operational effectiveness and retention. The "Intent-Based Leadership" framework operates through three core practices that systematically transfer authority downward. First, "I intend to..." statements replace permission-seeking requests, forcing subordinates to state their plan and demonstrate competence before acting. Second, leaders resist the urge to provide solutions and instead ask "What do you see?" to develop their team's analytical capabilities. Third, the "thinking out loud" protocol requires team members to verbalize their reasoning, creating transparency and learning opportunities. Marquet discovered that when his crew had to articulate their intentions, they caught their own errors and developed stronger decision-making muscles. The practical architecture for implementing leader-leader requires dismantling what Marquet calls "disempowerment" mechanisms embedded in most organizations. He identifies specific organizational antibodies that kill distributed leadership: approval processes that train people not to think, briefing practices that reward regurgitation over analysis, and measurement systems that punish initiative. The Santa Fe eliminated these barriers systematically. They stopped requiring permission for routine decisions, changed meeting formats from status updates to problem-solving sessions, and created "awards for bold action" rather than just perfect execution. Most significantly, they instituted "certification" processes where team members had to demonstrate mastery before gaining decision rights in specific domains. For executives and founders, Marquet's model offers a scalable alternative to the bottleneck of centralized decision-making that kills growth in expanding organizations. The key insight: competence must precede control. You cannot simply delegate authority without ensuring people have the technical skills and organizational context to exercise it effectively. This means investing heavily in training systems, creating clear decision criteria, and building feedback loops that help people learn from their choices. The Santa Fe's success wasn't just about empowerment—it was about creating the infrastructure for empowerment to work safely and effectively in high-stakes environments.

Key Concepts

• Leader-Leader Model: A hierarchy where people at every level are empowered to make decisions and take action within their domain of competence, replacing the traditional leader-follower dynamic. Unlike delegation, this transfers actual ownership of problems and solutions to those closest to the work.
• Intent-Based Leadership: Decision-making framework where subordinates state 'I intend to...' followed by their proposed action, demonstrating both competence and ownership. This replaces permission-seeking with declaration of intent, forcing people to think through consequences before acting.
• Control and Competence Mechanisms: The two pillars of empowerment where Control refers to moving decision-making authority to information sources, while Competence ensures people have technical knowledge and organizational clarity to decide well. Both must exist for empowerment to work safely.
• Thinking Out Loud: Communication protocol requiring team members to verbalize their reasoning and observations rather than just conclusions. When the sonar operator said 'I think we should surface' instead of just 'surface now,' it created learning opportunities and error-catching mechanisms.
• Certification vs. Training: Moving beyond teaching people what to do toward validating they can make good decisions independently. The Santa Fe required crew members to demonstrate mastery and judgment in specific domains before gaining decision rights in those areas.
• Don't Brief, Certify: Replacing status-update meetings with competence validation sessions where people prove they understand problems deeply enough to solve them. This shifts focus from information transfer to capability building.
• Organizational Antibodies: Structural elements that kill empowerment including approval processes that train helplessness, briefing formats that reward regurgitation, and measurement systems that punish initiative. These must be systematically identified and eliminated.

Mental Models

• Leader-Leader vs Leader-Follower
• Control + Competence Framework
• Intent-Based Decision Making
• Push Authority to Information
• Certification Over Training
• Short-Term Pain for Long-Term Gain

Actionable Insights

• Replace 'What should I do?' questions with 'What do you think we should do?' to transfer ownership of problems back to your team. This linguistic shift forces people to engage their analytical capabilities rather than wait for instructions.
• Implement 'I intend to...' language for all significant decisions, requiring team members to state their planned action and reasoning before proceeding. This creates a pause for reflection and demonstrates competence before granting authority.
• Identify and eliminate organizational antibodies like unnecessary approval processes that train learned helplessness. Map every permission-seeking interaction in your company and ask whether it develops or diminishes people's decision-making capabilities.
• Create certification processes for key competencies rather than just training programs, requiring people to demonstrate mastery before gaining decision rights. Define specific criteria for what 'good judgment' looks like in each domain of your business.
• Transform status meetings into problem-solving sessions by asking 'What do you see?' instead of requesting updates. This develops analytical skills and surfaces issues that people might otherwise escalate unnecessarily.
• Build 'thinking out loud' protocols where team members must verbalize their reasoning, not just their conclusions. This creates transparency and helps others learn decision-making frameworks rather than just outcomes.
• Resist the urge to provide immediate solutions when people bring you problems; instead, develop their competence by asking what options they see and what they recommend. Short-term inefficiency creates long-term organizational capability.
• Establish clear decision criteria and boundaries so people know when they have authority to act versus when they need input. Ambiguity kills empowerment because people default to seeking permission rather than risking mistakes.