Capitolo 1
From Command to Conversation: How Language Shapes Leadership
Leadership is Language isn't just another leadership book-it's a revolution in how we communicate at work. When former submarine captain L. David Marquet took command of USS Santa Fe, the worst-performing submarine in the fleet, he made a startling discovery: the problem wasn't his bad orders, but that he was giving orders at all. By changing just a few words-shifting from "request permission to" to "I intend to"-his crew transformed from passive followers into active leaders, taking the submarine from worst to first in record time. This Wall Street Journal bestseller has become required reading at companies like Google and has been praised by leaders like Simon Sinek, who called it "a masterpiece that will make you a better human being." Through examining the tragic case of container ship El Faro, which sailed directly into Hurricane Joaquin with the loss of all 33 crew members, Marquet shows how our Industrial Age language patterns create workplace disasters both dramatic and everyday-and offers a practical new playbook for breaking free.
Capitolo 2
The Fatal Legacy of Industrial Age Leadership
When the container ship El Faro departed Jacksonville for Puerto Rico in September 2015, Tropical Storm Joaquin was strengthening into a hurricane directly in its path. Despite this, Captain Michael Davidson chose the standard Atlantic route rather than the protected Old Bahama Channel. This decision would prove fatal.
The transcripts from El Faro's voyage recorder reveal a disturbing pattern. When officers expressed concerns about the deteriorating weather, the captain responded with dismissive statements like "We're good" and "We are gunna be fine." He mocked mariners who deviate course "for every single weather pattern" and flatly stated "We're not gunna turn around."
This language pattern-what Marquet calls "the language of invulnerability"-effectively shut down questioning and alternative viewpoints. The crew complied with the captain's decisions despite their misgivings. As conditions worsened, junior officers discussed their concerns among themselves but felt powerless to challenge the captain's authority.
When the second mate called the captain at 1:20 a.m. to report deteriorating conditions and suggest a southern route, her language was hesitant and deferential. The captain must have rejected this suggestion, as she simply replied "OK" and continued on course. By the time the captain returned to the bridge at 4:10 a.m., it was too late. The ship would sink within hours with the loss of all hands.
What's most striking about the El Faro disaster is that it wasn't caused by incompetence or lack of information. It was caused by communication patterns that prevented the crew from effectively collaborating and making good decisions. These patterns weren't unique to this ship-they reflect the legacy of Industrial Age leadership that still dominates our workplaces.
The transcripts reveal a severely skewed "share of voice"-the proportion of words spoken by each person. Using the Team Language Coefficient (TLC), where 0.0 represents perfectly balanced conversation and 1.0 represents one person doing all the talking, El Faro's bridge conversations consistently showed values around 0.5, indicating severe imbalance. The captain dominated conversations (50-57% of words), officers spoke significantly (39-45%), while seamen were nearly silent (2-5%).
This pattern is so predictable that knowing only the word count distribution would allow perfect prediction of the hierarchy. The solution is counterintuitive: leaders must talk less first, then others will talk more-not the reverse.
Capitolo 3
Redwork and Bluework: The Two Modes of Human Activity
At the heart of Marquet's framework is a simple but profound insight: human activity divides into two fundamentally different modes that require different approaches and different language.
"Redwork" is doing-the physical, active, execution-focused work that benefits from reducing variability. In redwork, we're focused on completing tasks efficiently, following procedures, and delivering results. We operate with a prove-and-perform mindset where stress can actually enhance performance up to a point. Redwork is our default mode because it's more efficient and less cognitively taxing.
"Bluework" is thinking-the cognitive, reflective, decision-making work that benefits from embracing variability. In bluework, we're focused on exploring options, questioning assumptions, making decisions, and learning from experience. We operate with an improve-and-learn mindset where stress severely impairs performance. Bluework requires deliberate effort because it's cognitively demanding.
The Industrial Revolution created a pernicious management approach that separated bluework and redwork by class-blueworkers (managers) made decisions while redworkers (laborers) executed them. This approach was exemplified by Frederick Winslow Taylor's 1911 book "The Principles of Scientific Management," which explicitly stated: "We do not want any initiative. All we want of them is to obey the orders we give them."
While this system benefited factory owners by allowing them to hire uneducated workers for specific tasks, it proved fragile and non-adaptive. It resulted in minimum effort, took a psychological toll on workers, and created environments that were taxing and depleting. The legacy remains in our cultural labels: leader or follower, salary or hourly worker, white hard hat or blue hard hat.
The problem today is that organizations need everyone to alternate between redwork and bluework, yet our language and organizational structures remain heavily biased toward redwork. We still use phrases like "all hands" meetings, divide between "leaders and followers," hold special "innovation sessions" (implying creativity isn't part of normal work), celebrate "can-do" teams, and maintain boss-subordinate relationships.
Capitolo 4
Control the Clock: The First Play in the New Playbook
The first play in Marquet's new leadership playbook is CONTROL THE CLOCK rather than OBEY THE CLOCK. This means deliberately pausing redwork to create space for bluework.
The 2017 Oscars envelope mix-up illustrates what happens when we fail to control the clock. When Warren Beatty received the wrong envelope and saw "EMMA STONE" and "LA LA LAND" instead of the Best Picture winner, he was confused but couldn't bring himself to stop the proceedings. He was trapped in redwork-following a predetermined sequence without questioning-and under stress, his prefrontal cortex shut down. Without tools to pause or question authority, he passed the card to Faye Dunaway who announced the wrong winner.
To run the CONTROL THE CLOCK play effectively, leaders need to:
1. Make a pause possible by explicitly creating space with statements like "We have time to do this right" or "I invite you to call pause if necessary."
2. Give the pause a name-create pre-planned phrases or signals that allow anyone to create an operational pause. On USS Santa Fe they used "hands off," while Toyota uses the Andon cord system. The key is practicing these pauses even when unnecessary, removing the stigma around calling them.
3. Call a pause when you notice team members showing signs of distress-hesitation, double-checking, or furrowed brows-even if they don't use the exact right code words.
4. Preplan the next pause by setting a timer, planning formal pauses, or incorporating regular reviews. By knowing a pause is coming, teams can focus 100% on execution without holding cognitive resources back for process monitoring.
Agile management effectively structures work in sprints with bluework bookending each production period-planning at the beginning and reflecting at the end. During sprints, leadership is prohibited from redirecting the team's work, allowing deep focus. The sprint cycle follows a continuous pattern of /blue-red-blue//blue-red-blue/ that ensures regular exits from redwork.
Capitolo 5
Collaborate: Embracing Variability for Better Decisions
The second play in Marquet's playbook is COLLABORATE rather than COERCE. While we often label our interactions as "collaboration," they're frequently coercion in disguise, with leaders stating opinions and others falling in line.
True collaboration requires letting the doers be the deciders and embracing the variability that comes from diverse perspectives. The COLLABORATE play aims to broaden perspectives, make visible the collective knowledge of the group, and establish a hypothesis before launching into the next period of redwork.
To run the COLLABORATE play effectively, leaders should:
1. Vote first, then discuss. To capture diverse thinking, participants should express their views independently before group discussion anchors opinions. Methods include anonymous electronic polling, asking probabilistic "how" questions instead of binary yes/no questions, using probability cards (1-99%) to identify outliers with strong opinions, dot voting for multiple options, and fist-to-five voting for quick assessments.
2. Be curious, not compelling. When people see things differently, leaders should be curious about what others see that they don't, rather than defending their own positions. The higher you are in the organization, the more important it is to speak last, as your opinion will likely anchor others.
3. Invite dissent rather than drive consensus. When groups appear unified, leaders must actively invite dissent to prevent groupthink. Solomon Asch's vision test study showed that one-third of participants would choose an obviously wrong answer when conforming to the group. Even more telling, when just one person dissented (even with another wrong answer), participants felt safe to voice their true opinions.
4. Give information, not instructions. Telling people what to do undermines collaboration. Instead, provide information and let people choose their actions based on understanding consequences. Rather than saying "Park there," try "I see a parking spot there." Instead of "Be back at 10:00 a.m.," say "I will start at 10:00 a.m."
With coercion, we get compliance and mere effort. With collaboration, we get commitment-signaling the end of bluework (embracing variability) and the start of redwork (reducing variability).
Capitolo 6
Commit: From Compliance to Ownership
The transition from bluework to redwork requires commitment, not mere compliance. While compliance is externally imposed, commitment comes from within as an intrinsic motivator that invites full participation and discretionary effort.
Commitment turns decisions into action. It's personal and requires genuine choice-without choice, we only get compliance. While compliance relieves people from thinking and responsibility ("I was just following orders"), it creates fragile situations where context is missing.
To run the COMMIT play effectively, leaders should:
1. Commit to learn, not (just) do. When transitioning from bluework to redwork, we should commit to testing hypotheses rather than just executing decisions. This learning mindset makes the redwork itself more engaging and heightens our awareness since we know our observations will matter for future decisions.
2. Commit actions, not beliefs. When seeking commitment, we shouldn't try to get people "on board" by changing their mindsets. Instead, focus on aligning their actions and behaviors. For significant decisions, some team members would have chosen differently, but what matters is that everyone commits to the actions needed to support the decision.
3. Chunk it small but do it all. For significant decisions, break commitments into smaller pieces with natural decision points between periods of redwork. El Faro's captain made the mistake of committing to the entire Atlantic route at once rather than breaking the journey into natural decision points with bluework pauses between periods of redwork.
Breaking redwork into small pieces helps counter "escalation of commitment"-our tendency to stubbornly stick to chosen courses of action despite evidence of failure. This psychological phenomenon was evident in America's deepening involvement in the Vietnam War, Theresa May's Brexit approach, and aboard El Faro, where the captain made statements like "We're not gunna turn around" despite dangerous conditions.
To counter escalation of commitment, organizations should separate decision-makers from decision-evaluators. Intel's Andy Grove and Gordon Moore demonstrated this through a thought experiment where they imagined being fired and new leaders deciding the company's direction. This psychological separation helped them pivot from memory chips to microprocessors.
Capitolo 7
Complete: The Deliberate End of Redwork
The Industrial Age playbook maximized production time by avoiding interruptions, but this creates three significant problems. First, failure to treat completion as deliberate leads to escalation of commitment, making organizations less likely to change course when needed. Second, without completion moments, there are no celebration opportunities, causing humans to become dispirited as days merge together without a sense of progress. Finally, completion serves to control the clock, creating operational pauses for reflection and improvement.
To run the COMPLETE play effectively, leaders should:
1. Chunk work for frequent completes early, few completes late. Early in projects when decision options are plentiful, the redwork-bluework rhythm should emphasize bluework and learning through frequent interruptions. As the project matures and decision space narrows, emphasis shifts toward execution with longer redwork periods and less frequent bluework.
2. Celebrate with, not for. Traditional praise ("Good job," "I'm proud of you") is controlling and manipulative. It positions the leader as judge and transfers the psychological reward to the leader rather than the performer. Instead, appreciate without evaluating, observe without judging, and prize without praising. Use descriptive statements that start with "I see," "I noticed," or "It looks like."
3. Focus on behavior, not characteristics. Carol Dweck's research shows that praising intrinsic attributes ("You're so smart") makes people avoid challenges that might threaten their identity. As a leader, acknowledge controllable behaviors (dedication, careful review, inviting feedback) rather than praising intrinsic characteristics ("deep thinker," "natural leader").
4. Focus on journey, not destination. In today's distributed workplace, leaders often lack direct observation of team members' work processes. To celebrate effectively, invite people to tell their stories about the journey. Research from Stanford shows that people who describe accomplishments using journey metaphors are more likely to continue goal-aligned behaviors.
Capitolo 8
Improve: The Heart of Bluework
The IMPROVE play-which comes from egoless scrutiny of past actions and deep reflection about what could be better-is the core purpose of bluework. It requires open-minded curiosity from everyone and directly connects mental activity to the desired outcome: improving redwork.
The challenge is that the IMPROVE play creates internal conflict between our "be good" self (which defends past work and protects our reputation) and our "get better" self (which seeks learning and growth). The "be good" self responds defensively with statements like "I didn't do anything wrong" or "We've always done it that way." The "get better" self asks curious questions like "How might we see it differently?" or "What could we do differently?"
To run the IMPROVE play effectively, leaders should focus:
1. Forward, not backward. Questions like "What do we want to do differently next time?" or "What worked well that we want to keep?" help teams look ahead rather than dwell on past mistakes.
2. Outward, not inward. Questions like "If someone else had to take over this project, what would you say to them?" or "What could we do to better serve our customers?" shift focus outward.
3. Process, not people. Questions like "How could this be done better?" or "What improvements could we make to the process?" help separate identity from outcomes.
4. Achieve excellence, not avoid errors. Avoiding errors creates a bias for inactivity-the best way to avoid mistakes is to avoid decisions altogether. People are motivated by achieving something great, not just being less bad than before.
For significant operational errors, the IMPROVE play becomes a formal organizational learning event starting with timeline creation. The basic redwork timeline captures what physically happened, while the bluework timeline identifies key decisions and who made them-the results of thinking processes.
Capitolo 9
Connect: The Enabling Play
The CONNECT play is the foundation that enables all other plays. Unlike other plays, it doesn't fit into the blue-red-blue cycle sequence but instead serves as the enabling building block for effective collaboration, commitment, completion and improvement.
The 2010 Deepwater Horizon disaster illustrates what happens when connection fails. Despite alarms indicating dangerous gas levels on the oil rig, workers waited for permission to activate the emergency disconnect switch, resulting in eleven deaths and a massive oil spill. This raises a crucial question: How could someone be more afraid of pushing a button without permission than dying in a fiery explosion?
Despite claims of "safety first," many organizations actually operate as "hierarchy first." The power of fear in control-oriented environments completely distorts common sense. The CONNECT play is the antidote to fear, creating psychological safety that allows people to speak up and move from paralysis to action.
To run the CONNECT play effectively, leaders should:
1. Flatten the power gradient by avoiding phrases that reinforce authority and instead create connection. Rather than doing things to or for people, do things with people. This means shifting language from "I need you to make a decision" to "We need to decide about this."
2. Admit you don't know. When leaders acknowledge uncertainty, they allow team members to admit they don't know-or importantly, to step forward when they do know something the leader doesn't. All learning starts with "I don't know" followed by "let's look it up," "how can we test it?" or "let's run an experiment."
3. Be vulnerable. Those in positions of power often cling to an aura of invulnerability, as demonstrated by El Faro's captain. Had he shown vulnerability with statements like "I'm a little freaked out" or "How is everyone feeling about this?" crew members would have felt empowered to express their own concerns.
4. Trust first. Instead of requiring people to prove themselves trustworthy before extending trust, leaders should trust first. Trust people first because your trust affects their behavior-they'll work harder, stay longer, and unlock more discretionary effort when trusted.
Capitolo 10
The Red-Blue Operating System for Modern Organizations
Human activity fundamentally divides into two distinct modes: thinking (bluework) and doing (redwork). Bluework encompasses cognitive, complex, and creative activities that embrace uncertainty and variability. It involves strategic planning, innovation, problem-solving, and collaborative learning. During bluework, teams engage in open-ended discussions, challenge assumptions, and explore multiple possibilities. Examples include strategic planning sessions, post-project reviews, and innovation workshops. Redwork, in contrast, involves physical, skill-based, and focused execution. It demands precision, consistency, and measurable performance, such as implementing established procedures, meeting production targets, or delivering defined services.
Leaders must orchestrate these modes across three critical domains. First, they determine the rhythm between red and blue phases, typically requiring more frequent bluework during project initiation and planning stages. Second, they actively manage bluework periods to maximize creative potential and inclusive participation, using techniques like structured brainstorming and facilitated discussions. Third, they establish appropriate goals and metrics during redwork phases to ensure efficient execution while avoiding excessive rigidity.
Research consistently demonstrates that specific performance goals, while effective for straightforward tasks, can actually inhibit performance in complex situations requiring innovation or adaptation. For instance, studies in product development teams show that "do your best" instructions often yield superior results compared to specific metric-based targets, particularly when dealing with novel challenges. This occurs because precise goals create psychological tunneling - people become so focused on meeting specific targets that they miss important peripheral information and opportunities for innovation.
Traditional annual planning cycles exemplify outdated Industrial Age thinking that assumes future conditions can be accurately predicted and planned for. These processes typically occur during high-pressure periods when organizations are deeply engaged in redwork (execution mode), leaving little cognitive space for meaningful reflection and strategic thinking. Many organizations conduct strategic planning alongside regular operations, resulting in superficial analysis and missed opportunities for genuine innovation.
The rhythm between redwork and bluework manifests at multiple organizational levels - from strategic corporate planning to daily team operations and individual work patterns. At the strategic level, organizations might alternate between execution quarters and planning/innovation periods. Operationally, teams might switch between focused delivery sprints and retrospective/planning sessions. Individuals need to balance task completion with learning and skill development.
Modern careers demand a fundamental shift from the traditional linear progression of education-career-retirement. Today's rapidly evolving workplace requires continuous learning and adaptation. Professionals must regularly alternate between skill application (redwork) and learning phases (bluework) throughout their careers. This might involve periodic sabbaticals, professional development programs, or dedicated learning sprints integrated into regular work schedules. For example, software developers might spend six weeks in focused development followed by two weeks of learning new technologies, while healthcare professionals might alternate between clinical practice and continuing education periods.
Capitolo 11
Saving Lives Through Better Language
What if El Faro's crew had used this new leadership playbook? Marquet reimagines how the tragedy might have been averted through better communication patterns.
Before departure, the captain would employ the CONNECT play rather than demanding conformity. He would establish rapport with officers and crew while serving as a filter for stress. With a "care, don't care" mindset-caring deeply about people and cargo but not bureaucratic consequences-he would work to lower the power gradient, particularly with the second mate (navigator).
As El Faro approached the Bahamas and Tropical Storm Joaquin was upgraded to a hurricane, the officer on watch would implement the CONTROL THE CLOCK play, calling a meeting to discuss routing options. The second mate would lead the meeting while the captain deliberately stood back to observe without influencing.
Using the fist-to-five voting method, the officers would display varying opinions about taking the Atlantic route versus the safer Old Bahama Channel. After thoughtful discussion, they would commit to the Atlantic route but only as far as Rum Cay, where they'd reassess at midnight. This shorter commitment would allow for learning while maintaining an escape option.
At the midnight meeting, with the storm intensifying and the ship already rolling hard, they would propose diverting to the safer Old Bahama Channel despite knowing it would delay arrival. The captain would approve this decision, and they would notify headquarters. When El Faro arrived in San Juan, there would be some topside damage, but all thirty-three crew members would survive.
This alternative narrative demonstrates how applying the new playbook-establishing psychological safety, empowering anyone to control the clock, maintaining a learning mindset, having junior officers lead decision meetings, and using voting before discussion-creates resilient decision-making that prioritizes safety over efficiency.
The power of leadership language isn't just about preventing disasters-it's about creating workplaces where people can be their best selves, where thinking and doing are valued equally, and where the rhythmic oscillation between redwork and bluework produces continuous learning and improvement. By changing how we talk to each other, we can transform our organizations from Industrial Age hierarchies into adaptive, innovative communities of leaders at every level.
