Aibrary Logo
Podcast thumbnail

Leadership Is Language

11 min

The Hidden Power of What You Say--and What You Don't

Introduction

Narrator: In late September 2015, the cargo ship El Faro sailed from Jacksonville, Florida, directly into the path of Hurricane Joaquin. On the bridge, the captain dismissed the growing storm with fatalistic confidence, telling his officers, “So we’ll just have to tough this one out.” Despite their experience and growing anxiety, the crew felt powerless to challenge the plan. Their suggestions to alter course were hesitant and easily dismissed. This adherence to a flawed plan, driven by a culture of compliance, led to a catastrophic outcome: the ship sank, and all 33 crew members were lost. What went wrong on that bridge was not a failure of seamanship, but a failure of leadership.

In his book, Leadership Is Language, former nuclear submarine commander L. David Marquet argues that the tragedy of the El Faro is a stark symptom of an outdated leadership model—an Industrial Age playbook that continues to fail us in the complex modern world. He reveals that the key to preventing such disasters and unlocking a team's true potential lies not in grand strategies or charismatic authority, but in the small, powerful words leaders use every day.

The Industrial Age Playbook Is Failing Us

Key Insight 1

Narrator: The core problem identified in the book is our reliance on an obsolete "playbook" for leadership, one inherited from the Industrial Age. This old playbook was designed for a world of predictable, physical labor, where efficiency was achieved by separating thinkers from doers. Managers made decisions, and workers complied. This system is built on a few core plays: "obey the clock" to maximize output, "conform to your role" to maintain hierarchy, and "prove your ability" to justify your position.

The final voyage of the El Faro serves as a tragic case study of this playbook in action. The captain, operating as the sole thinker, created a culture of coercion, not collaboration. His language of invulnerability—phrases like "We're good"—suppressed dissent. The crew, trapped in a "prove-and-perform" mindset, complied rather than committing their full intelligence to the problem. An analysis of the bridge voice recorder revealed a massive imbalance in the "share of voice," with the captain dominating conversations and junior officers barely speaking. They were following the old plays: obeying the clock to stay on schedule and conforming to their roles by not forcefully challenging the captain. This playbook, designed for the factory floor, proved deadly in the face of a complex, rapidly changing crisis at sea.

Differentiating Redwork from Bluework

Key Insight 2

Narrator: To build a new playbook, Marquet introduces a critical distinction between two modes of work: Redwork and Bluework. Redwork is the "doing"—execution, production, and reducing variability to achieve consistent results. Think of an assembly line worker performing a specific task or a pilot running through a pre-flight checklist. Bluework is the "thinking"—decision-making, planning, and embracing variability to foster creativity and innovation. It’s the work of collaborating on a new strategy or brainstorming solutions to a novel problem.

The Industrial Age, particularly through the "scientific management" of Frederick Winslow Taylor, created a class system around these modes. Managers were designated as the "blueworkers," the thinkers who designed the one best way to do a task. Laborers were the "redworkers," expected to execute without question. Taylor famously told workers, "We do not want any initiative. All we want of them is to obey the orders we give them... we have other men for thinking." This division created efficient but fragile systems, stripping workers of autonomy and the organization of their full cognitive potential. The new playbook aims to tear down this wall, enabling everyone to participate in both Redwork and Bluework.

Control the Clock to Exit Redwork

Key Insight 3

Narrator: The first play in the new playbook is to "Control the Clock," which means deliberately pausing Redwork to create space for Bluework. In high-pressure situations, people often get trapped in a "task-completion" mindset, blindly following a procedure even when something feels wrong.

The 2017 Oscars Best Picture mishap is a perfect, low-stakes example. When Warren Beatty opened the envelope, he saw the wrong winner's name. His brain registered an error, a signal to shift into Bluework. He paused, hesitated, and looked for help. However, the pressure of live television—the ultimate clock to obey—kept the system in Redwork. Faye Dunaway, impatient with the delay, grabbed the card and announced the wrong winner, La La Land. A simple, sanctioned pause—a moment to "control the clock" and ask, "What am I missing?"—would have prevented the embarrassing global spectacle. This play is about making it safe and normal to stop the assembly line, whether it’s on a stage or in an operating room, to think before acting.

Collaborate, Don't Coerce, in Bluework

Key Insight 4

Narrator: Once a team has paused, the next play is to "Collaborate." This stands in stark contrast to the old play of "coercion," where a leader pushes for their preferred solution. True collaboration aims to make the team's collective knowledge visible and leverages the "wisdom of the crowd."

A classic story illustrating this principle comes from scientist Francis Galton in the 1800s. At a county fair, he observed a contest to guess the weight of an ox. After collecting all 787 guesses, he found that while almost no individual guess was correct, the average of all the guesses was astonishingly accurate—just one pound off the ox's actual weight of 1,198 pounds. This is the power that collaboration unlocks. To achieve it, Marquet suggests techniques like "vote first, then discuss." This prevents the first or most senior person's opinion from anchoring the group. It encourages curiosity over persuasion and actively invites dissent to uncover risks and blind spots, ensuring the final decision is informed by the entire team's intelligence, not just the leader's.

Commit to Action and Complete the Cycle

Key Insight 5

Narrator: After Bluework collaboration, the team must transition back to Redwork. This requires the "Commit" play, which is fundamentally different from demanding compliance. Compliance is external; it’s doing what you’re told. Commitment is internal; it’s a choice to support a course of action. On the USS Santa Fe, Marquet learned this lesson when his crew followed his orders precisely but ended up in the wrong location because they lacked the context to adapt to unforeseen obstacles. They were compliant, not committed.

To foster commitment, leaders should frame action as learning and chunk work into smaller increments. This is the "Complete" play. Instead of a single, monolithic plan like the El Faro's voyage to Puerto Rico, work should be broken into phases with built-in decision points. This approach prevents "escalation of commitment"—the dangerous tendency to stick with a failing plan because of the initial investment. By completing smaller chunks, teams create natural moments for reflection and course correction.

Connect to Enable All Other Plays

Key Insight 6

Narrator: The final and most crucial play is "Connect." It is the enabling play that makes all others possible by fostering psychological safety and flattening the power gradient. Steep hierarchies stifle the flow of information, often with disastrous results.

During the 2003 Space Shuttle Columbia mission, engineer Rodney Rocha suspected that foam striking the wing during launch had caused critical damage. He drafted an email to request satellite imagery but hesitated. He later said, "I didn’t want to jump the chain of command." His fear of overstepping his authority—a direct result of a steep power gradient—prevented critical information from reaching decision-makers. The shuttle disintegrated upon reentry, killing all seven astronauts. Connection is the antidote to this fear. It is built when leaders admit they don't know, show vulnerability, and trust their teams first. It’s about caring what people think and feel, creating an environment where a junior engineer like Rocha feels not just permitted, but obligated, to speak up.

Conclusion

Narrator: The single most important takeaway from Leadership Is Language is that leadership is not a position of authority but a continuous act of communication. The goal is not to have all the answers and issue perfect orders, but to create an environment where the team can find the best answers together. This is achieved by consciously shifting away from the language of the Industrial Age—the language of command, compliance, and certainty—and adopting the language of the modern workplace: the language of curiosity, collaboration, and connection.

The book's ultimate challenge is for leaders to become intensely aware of their own words. Are you creating a team of compliant "redworkers" who simply follow instructions, or are you cultivating a team of engaged thinkers who can perform both Redwork and Bluework? The difference, as the story of the El Faro shows, can be a matter of life and death, success and failure. The real work of leadership begins the moment you start listening to what you say—and what you don't.

00:00/00:00