[mattbrewsbytes]

I also like that book. There are some obviously major motivational things that are different from corporate life (from what I've read, I have no first hand military exp): a camaraderie of protecting your peers with a common mission of literally staying alive, a chain of command with dire consequences, and other humans trying to kill you.

None of those things exist in software engineering so there will be people that aren't motivated by the allure of moving up, aren't passionate about the product and maybe just want to do their job and go home. There is nothing wrong with that as long as they are doing their work.

As a leader, you may have peers that will like you to take extreme ownership because they can play politics and blame you for things. I don't think there is room for that sort of BS on a battlefield but I don't have first-hand experience.

There are also a lot of teams that don't have 'mission' like goals that are clearly evident (e.g. root out terrorists in Ramadi) but have a continuous flow of work to be done.

Like any books/videos/courses on leadership or self-help, take what you can from it an see what sticks in your world, don't take it as a prescription or steps on how to do something.

[ambicapter]

> As a leader, you may have peers that will like you to take extreme ownership because they can play politics and blame you for things. I don't think there is room for that sort of BS on a battlefield but I don't have first-hand experience.

This question is addressed, if not in the book, at least in his podcast. Let me see if I can find it.