Leadership is Language
David Marquet's argument, built from his time commanding a nuclear submarine, that the exact words a leader habitually uses either keep an organization stuck in command-and-control execution mode or genuinely open it up to better thinking. Most leaders have no idea which one their default language is doing.
Find this on the mind-map
Introduction
Marquet's case, grounded in his experience turning around the culture on a nuclear submarine, is that leadership language isn't neutral packaging around a decision. The words themselves encode either control or collaboration, and most organizations default to control-language without anyone choosing it deliberately. Fixing this isn't about being nicer; it's about recognizing that certain everyday phrases actively prevent better information and better thinking from reaching the decision.
Bluework and Redwork
Marquet splits work into two modes: redwork, the execution phase (doing the task, following the plan, moving fast), and bluework, the thinking phase (deciding what to do, questioning assumptions, reflecting on whether the plan still makes sense). Most organizational language defaults to redwork phrasing even in moments that actually call for bluework. "Just tell me what to do" treats a decision that needs genuine thought as if it were a task that only needs execution. Picture a manager facing an ambiguous, high-stakes call: Manager A barks a direction immediately, in execution-mode language, because the team is anxious for an answer. Manager B says "let's pause, this is a decision, not a task yet," and opens a real bluework conversation before anyone acts.
From "What Should I Do?" to "I Intend To..."
One of Marquet's concrete mechanisms: replacing passive, permission-seeking language with ownership language. "What should I do?" hands the thinking upward and leaves the senior person to do the actual deciding. "I intend to do X, for these reasons" forces the speaker to think it through first and gives the senior person something specific to either approve or challenge. It's a small language shift that changes who's actually doing the cognitive work.
Certainty Language Shuts Down Information; Curiosity Language Invites It
A leader who speaks in confident, declarative certainty ("this is definitely the right call") makes it socially costly for anyone to raise a doubt, even a well-founded one. A leader who asks "what am I missing?" as a genuine, repeated habit signals that doubts are wanted, not tolerated. The difference isn't sincerity, it's the specific words used to open the conversation.
Push Decisions to Where the Information Is, Not Where the Seniority Is
Hierarchical language defaults decisions upward regardless of who actually has the relevant information. The senior person decides because they're senior, not because they know more about this particular situation. Marquet's alternative is explicit: build language that routes the decision to whoever has the most relevant information in the moment, and treat seniority as irrelevant to that routing unless it happens to coincide with the information.
Putting It Together
Redwork and bluework name the two modes; the shift from passive to ownership language, and from certainty to curiosity language, are the specific mechanisms that move an organization's default language toward genuinely distributing the thinking rather than just distributing the tasks. None of it requires flattening the org chart. It requires changing which words get used inside it.

Why It Matters for Leaders
The test this book gives you is simple to run and easy to fail without noticing. Listen to your own language for one day and count how often you're giving an answer versus asking a question you actually want answered. Most leaders think of themselves as open to input. Most leaders' actual words, in the moment something needs deciding, sound like someone who already has the answer and is explaining it. The gap between the two is where a team's thinking stops showing up, without anyone deciding to shut it off.
The highest-value fix isn't a new meeting format. It's two small phrases. When your team asks "what should I do," the habit to build is handing the thinking back: "what do you intend to do, and why." When you're about to say "this is definitely the right call," the habit to build is adding "what am I missing" right after it, out loud, and actually waiting for an answer. Neither phrase costs you any authority. Both change who in the room is doing the thinking.
The harder discipline is telling redwork moments from bluework moments before you respond, not after. A team that brings you a genuinely open decision and gets a fast, confident directive back learns, correctly, that bringing you open decisions is pointless; next time they'll just tell you what they already decided and ask for a rubber stamp. The fix isn't slowing everything down. Execution still needs speed and clear direction. It's noticing which moments are actually decisions in disguise and giving those the pause they need before the words come out.
Picture a manager, Theo, whose most senior engineer walks in and says, "we're blocked, what should I do?" Theo's old habit is to give the fastest clear answer he has, because that's what being decisive looks like, and he's good at it. Instead, Theo says "what do you intend to do here, and what's your reasoning," and waits. The engineer, who actually has more context on the blocker than Theo does, lays out a plan Theo hadn't considered and one risk he hadn't thought of. Theo's job in that moment isn't to have the best answer. It's to make sure the person with the most information is the one doing the deciding.
What to do next
Reinforce your understanding of Leadership is Language
Books related to Leadership is Language
Crucial Conversations
A manager's guide to the book about the story you make up before you open your mouth. It's not really a book about talking, but about the half-second before you talk that decides whether the conversation goes well or badly.
Difficult Conversations
The Harvard Negotiation Project's case that every hard conversation you're avoiding is actually three conversations tangled together: a dispute over facts, a buried argument about feelings, and a quiet question about identity, and most people only ever engage the first one.
Games People Play
The psychiatrist who invented Transactional Analysis, explaining why so many conversations at work are really scripted performances with a hidden payoff. It's a guide to spotting the game before you're cast in a role you didn't agree to.
Getting to Yes
The original Harvard Negotiation Project playbook. Negotiate on interests and objective standards instead of trading positions back and forth, and you stop needing to choose between being "nice" and getting a good outcome.
Give and Take
Adam Grant's organizational-psychology case that how you handle reciprocity, giving, taking, or matching, predicts long-run success better than talent does, as long as you give the right way.
Good Leaders Ask Great Questions
John Maxwell's case that the single clearest sign a leader has stopped growing is that they've stopped asking real questions, and that the habit of asking, not the gift of answering, is what keeps a leader's judgment sharp over time.
How to Win Friends and Influence People
The original relationship-building classic, decades before "emotional intelligence" had a name. Carnegie's bet is that nearly every influence problem is actually an ego-management problem, yours and theirs.
Influence
A social psychologist's field guide to the handful of automatic triggers that make people say yes, written so you can recognize them when they're used on you, and use them honestly when you're the one asking.
Made to Stick
Why urban legends, conspiracy theories, and your most forgettable all-hands deck follow completely different rules, and the six ingredients Chip and Dan Heath found in every idea that actually sticks in people's heads, whether or not it deserves to.
Never Split the Difference
A former FBI lead hostage negotiator's case against "splitting the difference," negotiation isn't a logic problem you solve at the table, it's an emotional one you solve before you ever get there.
Quiet
Susan Cain's case against the modern workplace's "Extrovert Ideal": the unexamined assumption that the loudest, fastest-talking, most group-comfortable person in the room is automatically the most capable one, and what gets lost, specifically, when organizations build around that assumption.
Radical Candor
Kim Scott's case that most managers who avoid giving hard feedback think they're being kind, and are actually doing the least kind thing possible, because withheld feedback doesn't disappear, it just shows up later as a surprise.
Surrounded by Idiots
A blunt, color-coded field guide to why the person across the table from you seems to be speaking a different language, because, behaviorally, they basically are.
The 16 Undeniable Laws of Communication
John Maxwell's case that communication is not a personality trait some leaders are simply born with, it's sixteen learnable, named laws, grouped around who's speaking, what's said, how it's said, when it's said, and why it's said.
The 48 Laws of Power
Robert Greene's amoral compendium of how power actually moves through organizations and courts, stripped of any pretense that fairness or merit is what decides who wins. Useful as a decoder, dangerous as a playbook.
The 7 Habits of Highly Effective People
Stephen Covey's classic, read through a modern-manager lens. Many of the ideas taught today as "new" leadership frameworks were already captured here decades ago.
Skills related to Leadership is Language
Frameworks related to Leadership is Language
Aristotle's Rhetoric
Aristotle's persuasion rests on three appeals — ethos (credibility), pathos (emotion), logos (logic) — use all three or your message won't land.
Cleverness to Clarity
Drop corporate jargon for clear, direct language — three reasons (trust, speed, growth) and the 2N Formula for doing it.
STAR Technique
Turn an experience into evidence in four parts — Situation, Task, Action, Result — to advocate for your people, make the case.
The Hemingway Iceberg Technique
A communication method from Hemingway's writing — say less, cut the padding, use specifics — letting what's unsaid carry the weight.
The Hero's Journey
Joseph Campbell's story arc — struggle, growth, return — turned into a structure for leadership storytelling people remember and act on.
The Influence Flywheel
A model for building influence without authority — five reinforcing spokes: Credibility, Connection, Clarity, Communication, Courage — building on each other.
The Pyramid Principle
Barbara Minto's McKinsey-born rule: lead with your conclusion, back it with 2 to 4 grouped arguments, support each with evidence.
The Three Stages of Communication
Leadership communication runs in three stages — Inform (facts), Inspire (emotion), Influence (action) — the one you're stuck in reveals the problem.