5 Management Books That Built My Engineering Leadership Library

Management reading lists are easy to compile and hard to act on. The problem isnt finding good books - its knowing which one to read first and what to actually take away.

These five are the ones I read in the first quarter of 2021. They cover the spectrum from team culture to individual coaching to process theory. Ive grouped them into a loose learning path so you know where to start depending on where you are in your leadership journey.

---

Start Here: Understanding Your System

The Phoenix Project - Gene Kim

A novel about IT, DevOps, and why your delivery pipeline is probably your biggest constraint. Its the least "management" book on this list and the most accessible. The format (business novel) means you absorb the ideas through story rather than framework descriptions - which is exactly why it works for teams that resist process books.

The one idea that stuck: Bottlenecks propagate. If your deployment pipeline has one slow step, everything queues behind it. Fixing that step changes the entire system - you dont need to optimise everything at once.

The Unicorn Project - Gene Kim

The companion novel, told from the developer perspective rather than IT operations. Where The Phoenix Project is "why DevOps matters," this one is "what it feels like to work in a system that doesnt let you ship."

The one idea that stuck: Autonomy without alignment is chaos. The book frames developer productivity as a function of the surrounding system, not individual effort - a useful lens when your team is struggling despite working hard.

---

Then: The Process Layer

Essential Scrum - Kenneth Rubin

The most textbook-like entry on this list. Essential Scrum is a thorough reference covering roles, ceremonies, artifacts, and the principles behind them. Its not a quick read - its a reference you return to when a specific practice isnt working and you need to understand why.

The one idea that stuck: The distinction between Scrum's mechanical practices (sprint length, ceremony format) and its principles (inspection, adaptation, transparency). Teams often fail at Scrum not because theyre doing it wrong mechanically, but because they have lost sight of what each ceremony is meant to achieve.

Honest note: Only read this cover-to-cover if you are a Scrum Master or coach. For team members, the official Scrum Guide is more than enough.

---

Finally: Leading People

The Managers Path - Camille Fournier

The single most practical engineering management book Ive read. It covers the full arc from tech lead to CTO, with specific advice for each transition. Where most management books give you principles, this one gives you what to actually say in a 1:1, how to handle a promo conversation, and when to escalate.

The one idea that stuck: Every management level has a different primary responsibility. Tech lead is about technical scope and mentoring. Engineering manager is about people and delivery. Director is about strategy and organisational health. The mistake is carrying the previous level's priorities into the new role.

Radical Candor - Kim Scott

The most focused book on this list: one framework, applied to the specific problem of giving feedback. Radical Candors 2x2 matrix (Care Personally vs Challenge Directly) is simple enough to remember and hard enough to actually practice.

The one idea that stuck: Most managers avoid one quadrant - Ruinous Empathy (caring personally without challenging directly). They know something is wrong but dont say it because they dont want to hurt feelings. The framework makes that avoidance visible and gives you language to name it.

Honest note: The concept is excellent. The book could have been a long article. The case studies add context but also padding. If youre short on time, read the original Radical Candor article instead.

---

Honest Take

This list has a gap: none of these books address managing managers or leading at a director+ level. Essential Scrum and The Phoenix Project assume youre close to the work. The Managers Path touches on director-level concerns but doesnt go deep. If youre beyond first-line management, youll need additional resources on organisational design, strategy, and executive communication.

The other honest note: reading five management books in three months is too many. These ideas need time to settle, to try, to fail at. A book a month is a more realistic cadence if you actually want to apply what you learn rather than collect frameworks.

What to Read First

All links in this post are to Amazon for reference. The books are widely available through libraries and other retailers as well.