Three Steps to Dismantle Command-Control Leadership Today

From Theory to Tuesday: Your Concrete Roadmap to Apply Turn the Ship Around

David Marquet walked onto the USS Santa Fe—the worst-performing submarine in the U.S. Navy—without the advantage of deep technical knowledge. That limitation forced him into a radical decision: he couldn't pretend to know everything, so he had to trust others to think. In under a year, the Santa Fe became the fleet's top performer and produced more commanding officers than any ship in decades.

But here's what matters to you: Marquet's transformation wasn't built on inspiration talks or motivational posters. It was built on concrete structural changes—specific shifts in how decisions flow, how language works, and how competence gets built. This is not a blueprint for submarines. It's a blueprint for any organization where people wait for permission instead of acting, where passivity costs you speed and talent, and where the leader has become the bottleneck.

The question isn't whether Marquet's model works. The question is: what do you change on Monday morning to make it work in your context?

Step One: Diagnose Your Current System (This Week)

Why This Matters First

The command-control model doesn't need a villain to function. It runs on inercia—on the daily structures, approval processes, and habits that nobody consciously chose but everyone reproduces. Until you see exactly where power is concentrated and where thinking stops, you can't redirect either one.

The Three Concrete Actions

Action 1.1: Observe Your Next Three Meetings (No Intervention)

Sit in your next meeting and count silent moments—how many times does someone look at you before speaking or deciding? How many times do people state something as a question to you when it should be their call? Write the number down. That number is your baseline dependency level. It tells you exactly how much your presence has become the permission mechanism in your team.

Action 1.2: Inventory One Week of Your Decisions

For five business days, write down every decision you made. Then ask yourself honestly: "Could someone closer to this problem have decided this better than me?" Mark those decisions. That pile is your redistribution list—the first source of control you're going to push down.

Action 1.3: Ask Three People This One Question

Call three team members separately and ask: "How would you describe your job in one sentence?" If answers sound like "I do what I'm told" or "I implement decisions made above," you have evidence of your current culture. If they sound like "I own the quality of X" or "I decide how we approach Y," your system already has pockets of real ownership to build from.

What You'll Know After This Week

You'll have the exact temperature of your organization: how centralized power actually is, how many decisions could move down, and which people already think like owners versus which ones have learned to wait. This diagnosis is not optional—you can't redesign what you don't see clearly.

Step Two: Change One Language Pattern and One Process (Next Two Weeks)

Why Language Matters

Marquet discovered that replacing "I request permission to do X" with "I intend to do X" changed everything. The first phrasing keeps people passive, waiting for approval. The second makes them responsible for the decision. One sentence structure. Massive shift in who owns the outcome.

The Two Concrete Changes

Change 2.1: Introduce "I Intend To" in Your Next Team Meeting

This week, tell your team this explicitly: "From now on, I want to hear 'I intend to' instead of 'Can I?' or 'Should I?' When you tell me your intention, you're telling me you've thought it through and you own it. My job isn't to approve—it's to help you succeed with what you've decided."

Then model it. In your next decision, say aloud: "I intend to change our Tuesday meeting time to 9 AM because it works better with the client's schedule." Own the decision publicly. This is permission for your team to do the same.

Change 2.2: Delegate One Complete Decision (Not a Task, a Decision)

Pick a routine decision that currently flows through you—hiring for a role, choosing a vendor, deciding how to structure a process, selecting priorities for a sprint. Tell the person responsible: "I'm not going to be consulted on this. You have the authority and the information. Decide it. Tell me what you decided and why, but I'm not approving or second-guessing."

This is not delegation of execution. This is delegation of authority. The person doesn't ask you before they decide—they tell you after they've decided. That structure shift trains your organization that decisions happen at the lowest level where information lives, not at the top where power sits.

What You'll Notice After Two Weeks

People will hesitate at first. They've been trained to wait. Some will keep asking permission out of habit. You'll feel the urge to jump in and decide faster. Don't. The discomfort is the sound of the system changing. Within two weeks, you'll see people starting to own decisions. That's when you know the language shift is working.

Step Three: Build Competence and Redistribute Control (Month One Onward)

Why This Order Matters

Marquet's key insight: giving control without building competence is irresponsible. Giving competence without control is frustrating. You need both. This step pairs decision authority with the skills and information people need to succeed.

The Three Concrete Actions

Action 3.1: Create Clarity on Criteria, Not Outcomes

For each decision you're distributing, write down the criteria that should guide it. Don't prescribe what decision they should make—prescribe what matters when they decide. For example, if someone is choosing between vendors, the criteria might be: "speed of implementation, cost under $50K, and reference from someone we know." The person decides which vendor best fits those criteria. You don't decide the vendor; you ensure the thinking is sound.

Action 3.2: Train Specifically for the Decisions You're Pushing Down

Before you fully delegate a decision, invest time in building the competence behind it. Walk through two decisions together. Show your thinking, not your conclusion. Explain why these criteria matter and how you weight them. Then let them decide the third one alone with you watching, available to debrief after. This is training for leadership at their level, not just doing their job faster.

Action 3.3: Establish a Weekly "Intent" Forum

Create a brief standing meeting (15 minutes max) where people tell you their intentions for the week—decisions they're planning, directions they're heading, risks they're managing. You listen. You clarify criteria if you see a gap. You ask questions. You don't approve or redirect unless the decision violates the criteria or puts the organization at real risk. This is your control mechanism in a distributed system: not preventing decisions, but ensuring they're informed and aligned.

What You'll Build Over One Month

You'll create pockets of real leadership throughout your organization. People will start to think before they act instead of waiting for direction. Your calendar will get lighter because you're not the bottleneck anymore. Decisions will happen faster. And most importantly, your organization will have more leaders, not more followers.

The Real Payoff: What Changes When You Actually Do This

Marquet's USS Santa Fe didn't become the best submarine because the crew suddenly got smarter. It became the best because the structure finally let them use the intelligence they already had. The same thing will happen in your organization.

When you change the system—the language, the processes, the approval chains—three things shift:

• Speed increases because decisions don't travel up and down the hierarchy anymore. They happen where the information is.
• Quality improves because the person making the decision is the one closest to the real constraints and context, not the person furthest from them.
• Retention and engagement change because people stop being passengers in their own work. They become owners.

Start This Week: Your Immediate Action List

By Wednesday: Observe your next meeting. Count the moments of waiting for permission.

By Friday: Make your decision inventory. Identify five decisions you can push down.

By Monday of Week Two: Introduce "I intend to" in your team meeting and model it yourself.

By End of Week Two: Delegate one complete decision to someone on your team with no approval step required.

By End of Month: Establish your weekly intent forum and see who starts thinking and deciding differently.

This isn't theory. This is structure. And structure is what actually changes how organizations work.

Download BOOKOS and listen to the full audio summary: https://bookosapp.com