Turn the Ship Around: From Command and Control to Leader-Leader

Before we dive in, I need to mention that this entire episode is AI-generated, including the voices you're hearing. Today's show is brought to you by FlowDesk, the fictional smart standing desk that adjusts to your mood and posture throughout the day. Please note that some information in this episode may be hallucinated, so I'd encourage you to double-check anything important.

I'm Maya, and today we're exploring 'Turn the Ship Around!' by L. David Marquet. With me is David, a former Navy submarine commander who's spent years implementing Marquet's leadership model in corporate environments. David, this book has become something of a leadership bible in many organizations.

It really has, Maya. What makes it powerful is that it's not theoretical leadership advice. It's a real story about transforming one of the worst-performing submarines in the Navy fleet into one of the best.

Let's set the stage. Marquet takes command of the USS Santa Fe in 1999, and this submarine is struggling. What kind of problems was he walking into?

The Santa Fe had the worst retention rates in the fleet. Crew members couldn't wait to leave. Morale was terrible, and operationally they were underperforming across the board.

And Marquet himself was in an unusual position. He'd spent months preparing to command a different submarine entirely, hadn't he?

Exactly. He'd been studying the USS Olympia for a year, learning every system and detail. Then thirty days before taking command, the Navy reassigned him to the Santa Fe, which had completely different equipment and procedures.

So he's walking into a struggling organization where he doesn't even know the technical details. Most leaders would probably double down on traditional command and control in that situation.

Right, and that's exactly what the Navy's leadership model was built on. The captain gives orders, subordinates follow them. It's a very top-down, leader-follower structure that had worked for centuries.

But Marquet realizes early on that this approach isn't going to work for him. There's a pivotal moment in the book where he gives an order that's literally impossible to follow, isn't there?

Yes, he orders 'ahead two-thirds' on the engines, but the Santa Fe doesn't have that setting. His officer just says 'ahead two-thirds, aye' and starts to implement an impossible order. That's when it hits Marquet that his crew is trained to follow blindly rather than think.

And that becomes the genesis for what he calls the leader-leader model. Can you break down what he means by that?

Instead of one leader at the top giving orders to followers, Marquet's model is about creating leaders at every level. Everyone takes ownership and makes decisions within their area of competence and authority.

The central thesis seems to be that traditional leadership actually makes organizations weaker, not stronger. How does Marquet make that case?

He argues that leader-follower structures create what he calls 'learned helplessness.' People become dependent on the leader for all decisions, even ones they're better positioned to make.

And the evidence he presents is compelling because it's not just philosophical. He's got concrete metrics showing how the Santa Fe's performance improved.

Absolutely. Retention went from worst to first in the fleet. The number of officers promoted ahead of their peers increased dramatically. And operationally, they started winning awards and commendations.

But what's really striking is that these improvements persisted after Marquet left. The submarine continued to perform at the highest levels under subsequent commanders.

That's the key test, isn't it? A lot of charismatic leaders can improve performance while they're present. But Marquet built a system that didn't depend on him being there.

He traces this back to some fundamental problems with how we think about leadership. What intellectual tradition is he pushing back against?

Really, it's centuries of military and industrial thinking that treats people as interchangeable parts. The idea that good leadership means having all the answers and distributing them down the chain.

And he's writing this in 2013, when there's already a lot of talk about empowerment and distributed leadership in the business world. What makes his approach different from what was already out there?

I think it's the systematic nature of it. A lot of empowerment efforts fail because they're piecemeal. Marquet shows how you have to change language, decision-making processes, and organizational structure all at once.

Let's dive into the practical framework. Marquet organizes his approach around three core pillars. The first is what he calls 'control.' What does he mean by that?

Control is about shifting decision-making authority to where the information and expertise actually live. Instead of pushing information up and waiting for decisions to come back down, you push authority down to where the information is.

And he's very specific about how to do this. One of the key tools is changing the language people use. Can you give us an example of how that works?

Instead of crew members saying 'Request permission to submerge the ship,' they say 'I intend to submerge the ship.' It sounds like a small change, but it shifts the entire dynamic.

How so?

When you request permission, you're asking someone else to think for you and take responsibility. When you state an intention, you're taking ownership of the decision and the outcome.

But this only works if people actually have the competence to make these decisions. That brings us to the second pillar, which is 'competence.' How does Marquet build that?

He's very systematic about it. Before anyone can make a decision, they have to demonstrate both technical knowledge and organizational clarity about their authority.

Give us a concrete example of how this played out on the submarine.

When someone says 'I intend to bring the reactor to criticality,' they have to be able to explain the technical process and confirm they have the authority to make that decision. No delegation without demonstrated competence.

And Marquet talks about 'don't brief, certify.' What's the difference?

Briefing is just information transfer. Certification means the person has to demonstrate they actually understand and can execute. It's much more rigorous.

The third pillar is 'clarity.' This seems to be about making sure everyone understands the organization's purpose and their role in it.

Right. You can't push decision-making down if people don't understand what they're optimizing for. Marquet spent a lot of time helping his crew connect their daily tasks to the submarine's mission.

He tells a story about the ship's cook that illustrates this beautifully. Can you share that?

The cook was just going through the motions, following recipes without thinking about the bigger picture. Marquet helped him understand that nutrition and morale were critical to the submarine's operational effectiveness.

And once the cook understood that connection, his performance transformed. He started innovating and taking ownership of meal planning in ways that went far beyond his job description.

Exactly. That's the power of clarity. When people understand how their work connects to something meaningful, they start thinking like owners instead of renters.

Now, these three pillars work together, but Marquet is clear that you can't just flip a switch and implement them overnight. What does the transition process actually look like?

It's gradual and requires constant reinforcement. Marquet talks about 'practicing' these new behaviors in low-stakes situations before applying them to critical operations.

Can you walk us through how someone might start implementing this in a typical workplace?

Start with the language piece. Instead of your team saying 'What should I do about this client issue?' encourage them to say 'I intend to handle this client issue by doing X, Y, and Z.'

And as the leader, how do you respond to that?

You resist the urge to immediately give your opinion. Instead, you ask questions that help them think through the implications. 'What happens if the client reacts negatively?' 'Do you have the authority to make that commitment?'

This requires a lot of discipline from the leader, doesn't it? Most managers are used to being the person with the answers.

It's probably the hardest part. Marquet talks about biting his tongue constantly in the early days. The instinct to just tell people what to do is very strong.

But there are also structural changes that need to happen. Marquet reorganized how meetings worked on the submarine, didn't he?

Yes, instead of him asking for reports from each department, the department heads would proactively share what they intended to do and what support they needed. It completely changed the dynamic.

Let's talk about a specific workplace scenario. Imagine you're a marketing manager and your team is planning a product launch. How would you apply Marquet's principles?

Instead of you creating the launch plan and assigning tasks, you'd have each team member come to you with their intentions. 'I intend to run the social media campaign with these three key messages.'

And then what's your job as the manager?

Your job is to ensure they have the competence to execute and the clarity about how their piece fits the overall strategy. You're checking their thinking, not doing their thinking.

But what if someone's intention is clearly wrong or suboptimal? Do you just let them make mistakes?

This is where the competence piece is crucial. If someone doesn't have the knowledge to make a good decision, you don't delegate it yet. You build their competence first.

Marquet is very clear about this. He says 'Don't empower, empower.' What does he mean by that?

Sorry, that should be 'Don't empower, enable.' Empowerment without competence is just abdication. You have to enable people by building their skills and understanding first.

Right. And there's a process for building competence. It's not just throwing people in the deep end.

Marquet talks about 'deliberate action.' Before anyone executes on their intention, they have to verbally walk through what they're going to do and why. It's a built-in quality check.

So in our marketing example, the social media person would say 'I intend to post content at 9 AM, 1 PM, and 5 PM because our analytics show highest engagement at those times.'

Exactly. And if their reasoning is sound and they have the authority, you simply say 'Very well' and let them execute. You're not approving the decision, you're acknowledging their authority to make it.

That phrase 'very well' comes up a lot in the book. It's not 'good idea' or 'I approve.' It's acknowledging that this is their decision to make.

Right. It reinforces that ownership stays with them. They're not implementing your decision, they're implementing their own.

Now, what about when things go wrong? Because inevitably, people are going to make mistakes when you give them more authority.

Marquet's approach is to focus on the thinking process, not the outcome. If someone made a good decision with bad results, you don't punish them. If they made a bad decision with good results, you address the decision-making process.

Can you give us an example of how that might play out?

Let's say someone launched a marketing campaign that performed poorly, but they had done solid research and had good reasons for their approach. You'd debrief what they learned, not criticize the decision.

But if someone got lucky with a poorly thought-through decision, you'd use that as a teaching moment about process.

Exactly. Because if you only look at outcomes, you're encouraging people to play it safe and avoid taking ownership of difficult decisions.

Marquet also talks about the importance of 'short, early conversations.' What does he mean by that?

Instead of waiting until something becomes a crisis, people should surface issues and intentions early when there's still time to adjust. It's about creating psychological safety for raising concerns.

This seems especially important when you're transitioning to this model. People need to know they won't be penalized for bringing up problems or uncertainties.

Right. And Marquet models this himself. He talks about admitting when he doesn't know something, rather than pretending to have all the answers.

Let's talk about some of the common pitfalls. What mistakes do leaders typically make when trying to implement this approach?

The biggest one is delegating authority without ensuring competence. You end up with people making decisions they're not equipped to make, and then you have to swoop in and fix things.

Which probably makes you less likely to delegate in the future. It becomes a vicious cycle.

Exactly. Marquet emphasizes that you have to be very gradual and systematic about it. Build competence first, then expand authority.

What about the flip side? Are there situations where this model doesn't work well?

Marquet acknowledges that in true emergencies, you might need to revert to command and control temporarily. If the submarine is flooding, there's no time for 'I intend to' statements.

But he's careful to say that leaders often overestimate how many true emergencies they face.

Right. Most of what we treat as emergencies are really just urgent decisions. And even then, if you've built competence properly, your people can often handle urgent situations without you.

How long does it typically take to see results from implementing this approach?

Marquet saw improvements within months on the submarine, but he's clear that building a truly leader-leader culture takes years. You're changing deeply ingrained habits and mental models.

And it requires consistency. You can't switch back to command and control when things get stressful.

That's the real test. It's easy to delegate when everything's going smoothly. The challenge is maintaining the approach when there's pressure and uncertainty.

If someone could only implement one piece of this framework, what would you recommend they start with?

The language change. Start asking your team to say 'I intend to' instead of 'Should I' or 'What do you want me to do?' It's simple but it immediately shifts the dynamic.

And for the clarity piece, what's the most important thing leaders can do?

Help people understand how their specific work connects to the organization's mission. Most people are doing tasks without understanding why those tasks matter.

Marquet tells the story of asking crew members what they thought the submarine's mission was, and getting wildly different answers.

Right. If people don't understand what you're trying to achieve, they can't make good decisions on their own. Clarity is foundational to everything else.

Let's talk about what this book gets right. What makes it particularly valuable in the leadership literature?

The specificity is what sets it apart. Most leadership books are full of platitudes. Marquet gives you exact phrases to use, specific processes to implement, concrete metrics to track.

And the fact that it's grounded in a real story with measurable results makes it much more credible than theoretical frameworks.

Plus, the submarine environment is so high-stakes that you know this isn't just feel-good management theory. This stuff has to work or people literally die.

But are there areas where the book oversimplifies or overpromises?

I think Marquet could do more to address the cultural and organizational barriers that make this transformation difficult. He makes it sound more straightforward than it often is in practice.

What do you mean by that?

Well, he had the authority as a submarine captain to make these changes unilaterally. Most managers are operating in organizations with entrenched hierarchies and competing priorities.

So a middle manager trying to implement this might face resistance from above and below.

Exactly. And Marquet doesn't give a lot of guidance for how to navigate those political realities. He focuses on what to do more than how to manage the change process.

Are there other limitations or blind spots in the approach?

The book is very focused on operational leadership but doesn't address creative or strategic work as much. The principles still apply, but the implementation looks different.

How so?

On a submarine, there are clear procedures and metrics. In creative work, success is more subjective and the path forward is less defined. You need different competence-building approaches.

What about scale? Marquet was leading about 140 people. Does this work in larger organizations?

That's a great question. The principles scale, but you need additional mechanisms for coordination and communication. Marquet touches on this but doesn't dive deep into it.

How does this book compare to other influential leadership works? Where does it fit in the broader conversation?

It's more practical than something like 'Good to Great' but not as comprehensive as 'The Fifth Discipline.' I'd say it's most similar to 'Multipliers' in terms of the core insight about developing others.

But Marquet's military background gives him credibility with audiences who might dismiss more touchy-feely approaches to leadership.

Absolutely. He's not talking about empowerment in an abstract sense. He's showing how to build what he calls 'intellectual firepower' throughout the organization.

What kind of impact has this book had since it was published in 2013?

It's become standard reading in many leadership development programs. I see the 'I intend to' language showing up in organizations across industries.

And Marquet has built a whole consulting practice around these ideas, working with companies to implement leader-leader models.

Right. What's interesting is seeing how the principles adapt to different contexts. The core ideas are robust, but the implementation has to be customized.

Has there been significant criticism of the approach over time?

The main criticism I hear is that it's too idealistic for most organizational cultures. Some argue that hierarchies exist for good reasons and shouldn't be flattened too much.

What's your take on that?

I think Marquet would say he's not eliminating hierarchy, he's optimizing it. The submarine still had ranks and ultimate accountability. But information and decision rights are distributed more effectively.

As we wrap up, what's the single most important insight from this book that you'd want listeners to walk away with?

That leadership isn't about having all the answers. It's about building the capability of your people to find answers and take ownership of outcomes.

And if someone's going to try one thing after listening to this conversation, what should it be?

Start paying attention to your language. Notice how often you give answers instead of asking questions. Notice how often your people ask for permission instead of stating intentions.

That's such a concrete starting point. You don't need to restructure your entire organization. You just need to change how you talk about decisions and ownership.

Exactly. And once you start noticing those patterns, you'll see opportunities everywhere to shift from leader-follower to leader-leader interactions.

David, this has been incredibly helpful. 'Turn the Ship Around!' really is a masterclass in practical leadership transformation. Thanks for walking us through it so thoughtfully.

Thanks, Maya. The book's core message is simple but profound: the best leaders create more leaders. That's how you build organizations that thrive long after you're gone.