Good Strategy/Bad Strategy

Systems of Engineering Management (Larson) - Best practical advice for dealing with software engineering teams Leading at the Speed of Growth (Catlin & Matthews) - Despite the title making me want to vomit, it has a bunch of practical advice about problems you'll encounter at various "stages" of a company, and how to identify what stage you're in. The First 90 Days (Watkins) - Useful if you ever take on a leadership role where the current state of the organization could be described as a "shitshow". Good Strategy / Bad Strategy (Rumelt) - Learn the difference between goals and strategy and plans.

- The Mom Test - 4 Steps to the Epiphany - The Personal MBA (Josh Kaufman) - Lean Analytics - Good Strategy Bad Strategy

Engineer turned engineering leader here. "Good Strategy / Bad Strategy" by Richard Rumelt - An awesome book on strategy, which explains very plainly how to construct a reasonable strategy, and see signs of bad strategy. It (among other things) dissects NVIDIA's rise in the late 2000's, and predicts (more or less) the next ten years of where the company went. "The Effective Manager" by Mark Horstman - All the things that no one says or tells about management and communication. "Team Topologies" by Skelton and Pais - A really good view of organizational design patterns and anti-patterns for software teams rooted in the premise of Conway's Law.