Turn the Ship Around! A True Story of Turning Followers into Leaders
Source: https://www.penguinrandomhouse.com/books/311686/turn-the-ship-around-by-l-david-marquet/ ↗
Marquet took command of a nuclear submarine with the lowest performance ratings in the US Navy and turned it into one of the highest, largely by inverting the relationship between command and initiative — moving from "I will, sir" to "I intend to" as the default communication mode.
The book is the specific operational account of how he did it, with unusually concrete examples of the moments where the shift happens or fails.
For product direction the transfer is direct: distributed authority is the challenge most product organisations face, and Marquet's account is more specific about how to produce it than the usual leadership literature.
Short and memoir-style; deceptively deep.
Central argument
Marquet argues that conventional leader-follower hierarchies are structurally incompetent because they concentrate decision-making at the top while concentrating relevant knowledge at the bottom. His central claim is that this inversion can be corrected not through culture change or motivation programs but through a specific linguistic and procedural shift: replacing 'I will, sir' — waiting for orders — with 'I intend to' — stating planned action and inviting challenge. The result, demonstrated aboard the USS Santa Fe, is that authority migrates to wherever competence and information actually reside, producing both better decisions and more capable people.
Critique
The nuclear submarine context, while vivid, creates a quiet selection problem: Marquet inherited a crew that was already trained, credentialed, and operating under life-or-death accountability norms that impose a discipline on 'I intend to' statements that most organisations cannot replicate. In product teams, where competence is uneven, stakes are diffuse, and psychological safety is genuinely asymmetric, the mechanism may produce performative intent rather than genuine distributed authority — people announcing intentions they have not thought through because the protocol rewards signalling over substance. Marquet addresses this through 'technical competence' as a prerequisite, but underestimates how difficult that prerequisite is to establish.
Why it matters for product
The 'I intend to' frame maps directly onto one of the most persistent dysfunctions in product organisations: senior leaders who complain about lack of ownership while unconsciously rewarding teams that seek approval rather than act. Marquet's account gives product directors a concrete diagnostic — if your team defaults to status updates and option-presenting rather than intent-stating, the problem is structural, not attitudinal, and needs to be addressed at the level of how decisions are formally communicated and sanctioned. His distinction between leader-leader and leader-follower design also reframes org design questions: whether squads, tribes, or pods actually produce autonomy depends on whether the communication defaults inside them have changed, not just the reporting lines.