Turn the Ship Around!
by L. David Marquet
The clearest argument I've read for pushing decisions down to the people doing the work.
- Status
- Read · May 2022
- Bought
- May 13, 2022
- For
- Engineering leads and managers · ICs about to step into team leadership · Anyone running a high-stakes, low-error operation
Where it earned its place
The one-paragraph verdict
Marquet ran a nuclear submarine by refusing to give orders — instead he pushed authority down to wherever the information already lived, and made his crew state intent rather than ask permission. That single move, “I intend to surface the ship,” is worth the price of the book; it’s concrete, repeatable, and it scales straight onto an engineering team. The recurring praise is right: it’s a real story with real stakes, not a consultant’s hypothetical. The recurring criticism is also right — it’s padded, the anecdotes loop, and the back half coasts on the goodwill the front half earned. You can extract the whole framework in the first hundred pages. [Turn the Ship Around! on Goodreads]
Who should read it
Read it if you’re an engineer stepping into leadership and you suspect being the smartest person in the room is the bottleneck — because it is. It’s also useful for senior leads who keep getting pulled into decisions they shouldn’t own. Skip it if you want academic rigor or a citation trail; this is one captain’s lived experience generalized into a method, not a study.
Where it earned its place
The “intent” idea shows up directly in how I run teams. No news is good news is Marquet’s control-pushed-down principle applied to status reporting: if the team owns the decision, silence is signal, not absence. And protecting teams by saying no is the flip side — pushing authority down only works if you also absorb the pressure coming from above.
Skip it if…
You already practice delegation and just want the model. The framework fits in a blog post; the book stretches it to 250 pages. Borrow it, lift the “I intend to” pattern, move on.