How leaders ask questions shapes team safety and decisions

Executive overview

Most leaders unknowingly use questioning patterns inherited from industrial-age management — patterns that suppress honest input and lock teams into bad decisions. The El Faro disaster, where 33 crew members died after sailing into a hurricane, is documented in 25 hours of bridge transcripts that show exactly how this plays out in real time.

The problem is not that people stay silent — it's that the questions leaders ask make honesty structurally hard.

David Marquet's framework identifies seven questioning failures and their practical replacements, grounded in both the El Faro transcripts and his own turnaround command of the USS Santa Fe.

Red work vs. blue work

• Red work: execution — following the process, running the chosen route. Benefits from reduced variability.
• Blue work: deciding — choosing the route, weighing risk, making judgment calls. Benefits from embracing variability.
• Industrial-age management assigned thinking to managers, doing to workers. Modern teams need everyone doing both.
• Labeling people as thinkers or doers — via salary tier, job title, or uniform — is the core problem.
• The El Faro crew who saw the danger could not break through the conversational structure to change the captain's decision.

The seven sins of questioning

1. Stacking questions — asking several questions in a row leads the other person down your logic path. Ask one question, then stop.
2. Leading questions — "Have you thought about the customer?" signals you've already decided they're wrong. Replace with: "Tell me your thinking."
3. Why questions (tactical) — "Why would you want to do that?" signals disapproval and triggers defensiveness. Replace with "What's in the way?" or "What factors did you weigh?"
4. Dirty questions — questions that embed assumptions ("Do you have the courage to stand up to them?") project your bias as neutral inquiry. Strip the embedded claims.
5. Binary questions — "Is it safe?" invites only yes or no, and the default is yes. Replace with "How safe is it?" to get genuine input across a spectrum.
6. Self-answered questions — asking then answering your own question ("We're going to keep going straight, right?") makes disagreement nearly impossible.
7. Teaching-moment questions — using Socratic leading to guide someone to your conclusion. Make it a learning moment instead: find out what they see that you don't.

Team language coefficient

• In every El Faro bridge recording, hierarchy predicted word count with 100% accuracy.
• Crewmen said as little as 2–5% of words when the captain was present; conversations opened up only after he left.
• This maps to a Gini coefficient applied to voice share: 0 = perfectly equal, 1 = one person said everything. Lower is more resilient.
• MIT research confirms teams with more even share of voice are more resilient and effective.
• Two causes of uneven distribution: the leader talks too much, or quieter members don't engage.
• Fix it by inviting directly: "John, you've been quiet — what gives you pause here?" Follow up privately if needed.

Asking for disconfirming information

• Structure questions so the easy answer is the one you don't want to hear.
• Ask: "What am I missing?" "How could this be wrong?" "What was unclear?"
• The El Faro captain made ~1,600 statements and ~250 questions in 25 hours — and answered most of his own questions.
• In time-critical decisions, use rapid scale votes (1–5, or fingers held up) to get nuanced input fast without losing speed.