lev-os Leadership Is Language
Overview
Leadership Is Language, developed by David Marquet building on his Turn the Ship Around experience, argues that the words leaders use create either empowerment or compliance. The framework exposes how Industrial Age language patterns (inherited from manufacturing efficiency) actively undermine modern knowledge work that requires thinking, decision-making, and variability. The critical insight: even well-intentioned collaborative leaders unconsciously use coercive language that separates thinkers (managers) from doers (employees), creating passive teams that wait for direction. The book introduces six "plays" that shift from controlling outcomes to controlling decision-making processes. Central to the framework is distinguishing Redwork (doing, executing, reducing variability) from Bluework (thinking, deciding, embracing variability) - and recognizing that Industrial Age organizations optimize for Redwork while modern work demands both. The goal is letting "doers be the deciders" by changing how leaders communicate.
When to Use
- Teams execute plans blindly without questioning assumptions or adapting
- Employees wait for permission rather than making decisions
- Meetings focus on proving existing plans rather than improving them
- Urgent deadlines cause teams to skip thinking and rush to doing
- Leaders notice they're micromanaging but struggle to delegate effectively
- Organization talks about empowerment but uses command-and-control language
- High-risk environments where mistakes compound (aviation, military, healthcare, software)
- Transitioning from hierarchical culture to collaborative decision-making
The Process
Step 1: Understand Redwork vs Bluework
Recognize that work has two distinct modes requiring different approaches. Redwork is execution work: doing tasks, following procedures, reducing variability, working against the clock, proving that plans work. Bluework is cognitive work: thinking, making decisions, embracing variability as information, improving plans, learning. Industrial Age optimized for Redwork by separating blueworkers (managers who think) from redworkers (employees who do). Knowledge economy requires everyone to toggle between both modes. The language you use signals which mode you're in and which mode you're requesting from others. Example: "Execute the plan" triggers Redwork. "Pause - what are we seeing?" triggers Bluework.
Step 2: Play 1 - Control the Clock, Don't Obey the Clock
Pre-plan decision points where team pauses to assess conditions and decide whether to continue, adapt, or stop. Resist urgency bias that drives teams to rush from planning into execution without checkpoints. Give people permission and tools to "hit pause" when they notice concerning patterns. Treat every phase as series of decisions, not inevitable march toward deadline. Example: Software team planning sprint identifies three decision points: after design review (do designs solve the problem?), after first integration (are components compatible?), after QA pass (is quality acceptable?). At each point, team can adapt plan based on what they've learned.
Step 3: Play 2 - Collaborate, Don't Coerce
Replace "tell them what to do" with "engage them in deciding what to do." Shift from giving answers to asking questions that surface team's thinking. Use language that invites contribution: "What are you seeing?" instead of "Here's what I see." Make decisions together, not in hierarchy. Flatten the distinction between managers and workers - everyone thinks and does. Example: Instead of manager assigning tasks in standup, ask "What's blocking us?" and "What should we tackle next?" Team decides collectively based on their ground-level knowledge.
Step 4: Play 3 - Commit, Don't Comply
Replace "follow these specific directions" with "here's the goal, commit to achieving it your way." Explain the overall objective and constraints; let team determine approach. Get explicit commitment to outcomes, not compliance with methods. People who commit to goals they helped shape show dramatically higher ownership than those complying with orders. Example: Don't say "Call 50 prospects using this script." Say "We need 10 qualified leads by Friday. How will you get them?" Get team's commitment to the outcome and their chosen method.
Step 5: Play 4 - Complete, Not Continue
Frame work as distinct projects with clear start and end dates, not perpetual processes. Completion creates learning - what worked, what didn't, what to do differently. Continuation creates monotony and prevents reflection. Announce "this phase is complete" to create pause for Bluework before starting next phase. Celebrate completions; analyze them; don't just roll into next thing. Example: Instead of "keep coding features," frame as "Complete user authentication by Thursday, then we'll assess and decide next phase." Thursday becomes decision point, not just deadline.
Step 6: Play 5 - Improve, Not Prove
Ask people to improve the plan rather than prove the plan works. Shift from defending existing approach to discovering better approach. Create safety for raising concerns, proposing alternatives, admitting mistakes. Language of proving: "We can make this work" (commitment to existing plan). Language of improving: "How could this work better?" (invitation to challenge plan). Example: In project review, don't ask "Are we on track?" (proves plan). Ask "What have we learned that should change our approach?" (improves plan).
Step 7: Play 6 - Connect, Don't Conform
Flatten hierarchy to connect with people's authentic thoughts rather than forcing conformity to role. Create space for dissenting views and contrary data. Encourage people to speak up when they see problems, regardless of rank. Replace "stay in your lane" with "contribute your perspective." Connect human-to-human rather than role-to-role. Example: Senior leader in product review says "I'm going to share my opinion last so I don't anchor everyone. What are you each seeing?" Creates space for junior people to share concerns that would be suppressed if leader spoke first.
Example
The El Faro Disaster: Cargo ship El Faro sank in 2015 hurricane, killing all 33 crew. Recovered voice recordings show captain and crew using Industrial Age playbook: captain gave order to sail into hurricane path (Redwork - execute plan), crew complied despite concerns (no permission to challenge), time pressure prevented pause to reassess (obey clock), hierarchical communication prevented crew from voicing safety concerns (conform not connect). Captain's language: "We can make this work" (prove not improve). What New Playbook would look like: Pre-planned decision point: "If weather worsens, we pause and reassess" (control clock). "What are you seeing?" asked of each crew member (collaborate). "I need your honest assessment - should we proceed or delay?" (connect not conform). "What would make this safer?" (improve not prove). The tragedy demonstrates deadly cost of Industrial Age language in high-variability, high-stakes environment.
Anti-Patterns
Using Plays as Tactics Not Transformation: Asking "What are you seeing?" but ignoring answers and imposing your solution anyway. Language shifts without mindset shift create cynicism. Fix: Genuinely be open to changing your mind based on team input. If you're not willing to adapt, don't ask.
Bluework Without Redwork: Endless discussion and improvement without committing and executing. Analysis paralysis. Fix: Toggle between modes. Use Bluework at decision points; use Redwork between them. Complete phases to create learning.
Redwork Urgency Overwhelming Bluework Pauses: Time pressure causes team to skip decision points and rush into execution. "We don't have time to think, just do it." Fix: Build decision points into timeline. Pausing to assess saves more time than costly mistakes from blind execution.
Connect Without Consequence: Encouraging dissenting views but never acting on them. Team learns that speaking up is performative, not valued. Fix: Explicitly change plans based on team input. Show that connecting influenced decisions.
Improving Forever Without Committing: Perpetual refinement without ever committing to execute. Fix: Set decision deadlines. "We improve the plan until Thursday; then we commit and execute."
Language Change Without Authority Change: Using collaborative language but keeping hierarchical decision authority. "What do you think?" followed by "Thanks for input, here's what we're doing." Fix: Distribute decision authority to match language. If you ask for input, give people real influence over outcome.
Related Frameworks
Turn the Ship Around (Marquet): Marquet's earlier framework on intent-based leadership provides the leadership philosophy. Leadership Is Language provides the specific communication tools to implement it.
Radical Candor (Kim Scott): Scott's framework focuses on feedback (challenging directly + caring personally). Leadership Is Language focuses on operational communication (questions, decision language, collaboration patterns). Both emphasize psychological safety.
The Advantage (Lencioni): Lencioni's organizational health requires productive conflict on leadership teams. Marquet's "collaborate not coerce" provides language tools to make that conflict productive rather than destructive.
Team Topologies (Skelton & Pais): Skelton's framework defines team structures and interaction patterns. Marquet's plays provide communication patterns that make those interactions effective within each topology.
Thinking in Bets (Annie Duke): Duke's framework for decision-making under uncertainty complements Marquet's "control the clock" and "improve not prove" - both emphasize creating decision points and learning from outcomes.
OODA Loop (Boyd): Boyd's observe-orient-decide-act cycle maps directly to Marquet's plays. Control clock = create decision points in OODA loop. Collaborate = better observation. Improve = better orientation. Commit = decide. Complete = act and learn.