Everything by Simon Sinek, but most important for me is "Leaders Eat Last" [0]. I haven't read the last one (The Infinite Game), but I've heard it's pretty good as well. Also Extreme Ownership [1] and Dichotomy of Leadership [2] by Jocko Willink and Leif Babin. All of these books had tremendous impact on me as a leader and I highly recommend them. [0]: https://www.amazon.com/Leaders-Eat-Last-Together-Others/dp/B... […
I can’t handle the level of repetition. You read one chapter and you’ve read the entire book. It could literally just be a bumper sticker - ‘real leaders eat last’ - ok got your thesis
Ask HN: Best book / resources on leadership, especially for tech teams?
161–170 of 220 posts
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#162Earlier quoted context omitted.
> The military demands that soldiers immediately and unquestioningly follow commands given by their superiors (particularly during combat). This doesn't jive with my understanding of US military (or human nature). Out of combat, a top-down command and control hierarchy leads to poor decision making by troops on the ground. A general can't and shouldn't make decisions on day-to-day operations at the platoon-level. In…
See for example Team of Teams by General Chrystal--which is also a good book about organization/business generally.
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#163The US Army has an exceptionally well-crafted field manual on leadership. No fluff, but also no chest-thumping. It's honestly the best resource I've ever seen on what constitutes a good leader, how good leaders are developed, and how good leaders develop their teams. Being a DOD publication, it's in the public domain: https://usacac.army.mil/sites/default/files/misc/doctrine/CD... I can't stress enough how excellent…
* Abusive behaviors—includes behaviors that involve a leader exceeding the boundaries of their authority by being abusive, cruel, or degrading others. These behaviors are contrary to what is required for the moral, ethical, and legal discharge of their duty. Specific examples include, but are not limited to, bullying, berating others for mistakes, creating conflict, ridiculing others because of the authority held, domineering, showing little or no respect to others, insulting or belittling individuals, condescending or talking down to others, or retaliating for perceived slights or disagreements.
* Self-serving behaviors—includes behaviors that result from self-centered motivations on the part of the leader, where they act in ways that seek primarily to accomplish their own goals and needs before those of others. Specific examples include, but are not limited to, displaying arrogance, lacking concern or empathy for others, taking credit for others' work, insisting on having their way, distorting information to favor own ideas, exaggerating accomplishments or abilities, putting own work and accomplishments ahead of others' and the mission, displaying narcissistic tendencies, or exhibiting a sense of entitlement.
* Erratic behaviors—includes behaviors related to poor self-control or volatility that drive the leader to act erratically or unpredictably. Specific examples include, but are not limited to, blaming others, deflecting responsibility, losing temper at the slightest provocation, behaving inconsistently in words and actions, insecurity, or being unapproachable.
* Leadership incompetence—includes ineffective leadership behaviors that result from a lack of experience or willful neglect. Incompetence can include failure to act or acting poorly. While incompetent leadership can arise from reasons unrelated to counterproductive leadership, it is included as a category often associated with arrogant or abusive leaders who are not aware of their shortcomings and do not seek to correct their shortcomings. Conversely, some leaders lacking competence are aware of their shortcomings, which lead them to behave in counterproductive or negative ways to cover up their shortcomings or mistakes. Specific examples include, but are not limited to, unengaged leadership, being passive or reactionary, neglecting leadership responsibilities, displaying poor judgment, poorly motivating others, withholding encouragement, failing to clearly communicate expectations, or refusing to listen to subordinates.
* Corrupt behaviors—includes behaviors that violate explicit Army standards, regulations, or policies. Violations may range from behaviors subject to administrative discipline to criminal actions subject to discharge or incarceration. Specific examples include, but are not limited to, dishonesty, misusing government resources or time, creating a hostile work environment, EEO/SHARP violations, or violating Section 3583 (Requirement of Exemplary Conduct), Title 10, United States Code, AR 600-100, or the Uniform Code of Military Justice.
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#164"Peopleware" is a great one -- https://www.amazon.com/Peopleware-Productive-Projects-Teams-...
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#165Earlier quoted context omitted.
Leaders Eat Last was one of the best books I read this year. Extreme Ownership was also quite good but Simon really explains the “Why” of leadership that most books are missing. High-Output Management is another classic.
I understand the “why” of leadership very well, but as a high-functioning autistic person, I struggle very much with the “how”, especially around communication. Like - for all possible values of X, if X is what I want someone to do, how do I communicate that so people (a) understand that I want X from them and (b) aren’t offended and understand that it is meant kindly/charitably (which it really is, I often just don’…
The "Please stop. I've got this." is an action-oriented message that is conveyed before the action. It says "I would like for you to do X because of Y." It is conveyed in an imperative structure, which is used for a command or a request. "Please stop." Conversely, when you say "I was going to get it," it is a declarative message rather than an imperative message. It does not tell your wife what you would like for her to do. It is merely additional data that does not help her make better decisions, which means it is mostly useless for her. An extreme comparative example is looking at a person who has just burned their hand at the stove and then saying "that stove appears hot."
Humans don't like to receive an array of "reasons" data before they've received the "request." We don't like statements in the form of "because of Y, Z, A, B, C... please do X." Our subconscious can typically detect that we are receiving a stream of "reasons" and we are starting to brace for the "request" (because the request might be unpleasant).
People like to know what others expect of them. Your comment says you would like to know what your wife expects of you. When you follow the order of operations you are giving people what they want (what you expect of them) followed by your reason for wanting that. When you go in the opposite order, you are conveying the converse: "I want something of you but I haven't told you what it is yet."
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#166General Management - High Output Management by Andrew Grove
Visibility and Alignment - Measure What Matters by John Doerr
Understanding People and Teams - Surrounded by Idiots by Thomas Erikson
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#167Earlier quoted context omitted.
I understand the “why” of leadership very well, but as a high-functioning autistic person, I struggle very much with the “how”, especially around communication. Like - for all possible values of X, if X is what I want someone to do, how do I communicate that so people (a) understand that I want X from them and (b) aren’t offended and understand that it is meant kindly/charitably (which it really is, I often just don’…
This is not a book full of "scripts," but will hopefully help inform future actions: The "Please stop. I've got this." is an action-oriented message that is conveyed before the action. It says "I would like for you to do X because of Y." It is conveyed in an imperative structure, which is used for a command or a request. "Please stop." Conversely, when you say "I was going to get it," it is a declarative message rath…
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#168The US Army has an exceptionally well-crafted field manual on leadership. No fluff, but also no chest-thumping. It's honestly the best resource I've ever seen on what constitutes a good leader, how good leaders are developed, and how good leaders develop their teams. Being a DOD publication, it's in the public domain: https://usacac.army.mil/sites/default/files/misc/doctrine/CD... I can't stress enough how excellent…
You listen to Jocko podcast by any chance?
Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#169Re: Ask HN: Best book / resources on leadership, especially for tech teams?
#170The US Army has an exceptionally well-crafted field manual on leadership. No fluff, but also no chest-thumping. It's honestly the best resource I've ever seen on what constitutes a good leader, how good leaders are developed, and how good leaders develop their teams. Being a DOD publication, it's in the public domain: https://usacac.army.mil/sites/default/files/misc/doctrine/CD... I can't stress enough how excellent…
I'm reading through it and absolutely loving it so far. They're able to succinctly capture concepts I have had trouble defining. Are there any specific parts you'll recommend? Or anything I should skip?
Regarding skipping, I can't recall anything that's counterproductive to read, but it's possible I skipped those parts, and, so, can't remember them. I wouldn't hesitate to jump into sections that seem especially relevant to your situation, and then jump back out.
In terms of parts to recommend, I thought Chapter 6 had especially practical/applicable content for me as a manager. Within that chapter, I felt that the "Counseling, Coaching, and Mentoring" section (beginning at section 6-52, through Table 6-3) is especially pertinent, as it laid out those particular roles and responsibilities far better than any of the internal resources I was given. The lines between those roles at startups are often muddy, if they're even laid out at all, and there's a lot of great work that senior engineers / tech leads can do to develop junior engineers they work with, outside the normal manager / IC dynamic.