
“One of the 12 best business books of all time…. Timeless principles of empowering leadership.” – USA Today "The best how-to manual anywhere for managers on delegating, training, and driving flawless execution.” —FORTUNE Since Turn the Ship Around! was published in 2013, hundreds of thousands of readers have been inspired by former Navy captain David Marquet’s true story. Many have applied his insights to their own organizations, creating workplaces where everyone takes responsibility for his or her actions, where followers grow to become leaders, and where happier teams drive dramatically better results. Marquet was a Naval Academy graduate and an experienced officer when selected for submarine command. Trained to give orders in the traditional model of “know all–tell all” leadership, he faced a new wrinkle when he was shifted to the Santa Fe, a nuclear-powered submarine. Facing the high-stress environment of a sub where there’s little margin for error, he was determined to reverse the trends he found on the Santa Fe: poor morale, poor performance, and the worst retention rate in the fleet. Almost immediately, Marquet ran into trouble when he unknowingly gave an impossible order, and his crew tried to follow it anyway. When he asked why, the answer was: “Because you told me to.” Marquet realized that while he had been trained for a different submarine, his crew had been trained to do what they were told—a deadly combination.
I think this paragraph is right on the money, but the ‘leader’ has more influence on their ‘underlings’ than you give them credit for. In this vein, I highly recommend “Turn the Ship Around!” by Marquet, which is the only good book on leadership I’ve managed to find.
I haven’t read the article, so maybe it’s been covered, but here’s a simple way I usually “ask for no.” I send a message on Slack:
“Hey (name), I’m planning to (do a thing) on Wednesday. Let me know if you have concerns.”
It doesn’t come across as usurping authority, or sneaky, or any of the other very italicized things you’re worried about. It comes across as polite and confident.
I’m a VP and this is how I expect my managers to interact with me on major decisions that are within their purview (I don’t need to hear about minor decisions) and it’s also the culture I’m trying to create at the team contributor level as well. Ownership and autonomy, within well-defined guardrails.
See also Turn the Ship Around and its “I intend to” structure.
Your role is to improve your staff to be better in their jobs. Ignoring the Manager/Engineer caste system, there is a lot general leadership in both roles.
You want your staff to be able to integrate and find information that allows them to make decisions, you don't lose accountability or responsibilty.
There is a big difference between
- "I've looked at the details, and I think we should do X, what do you think?"
and
- "What should we do about this?"
In the former, you can add extra context, and help your report understand details that may have been hidden or unknown to them. In the latter you are allowing your report to shift all the burden to you.
If you are looking into more of the "people" side of things, I would HIGHLY recommend Never Split the Difference by Chris Voss [0]. A big part of being a team lead and/or working at a larger firm is understanding where people are coming from and then convincing them that your solution is "win/win". The book is great at highlighting multiple different tactics to do that.
Turn the Ship Around [1] is also great at giving examples of how to "change organizations in place". If you end up at larger firms, there will be a LOT of legacy infra and processes that you may want to improve. Marquet gives excellent examples of how to change things WHILE ALSO getting buy in from the team.