An Elegant Puzzle is Will Larson’s systems-oriented guide to engineering management. Where most management books focus on interpersonal skills (feedback, coaching, motivation), Larson focuses on the structural and systemic challenges: how to organize teams, how to manage competing priorities, how to handle technical debt, how to design processes that scale, and how to create the organizational infrastructure that lets an engineering department grow without breaking.
The team sizing chapters are among the most useful. Larson provides specific guidelines for how many people a team needs to be effective (he argues for six to eight), what happens when teams are too small (they can’t absorb attrition or take on meaningful projects) or too large (coordination costs eat their productivity), and how to rebalance teams without destroying morale.
The technical debt and migration chapters are equally practical. Larson treats technical debt as an organizational problem, not a technical one: it accumulates when teams are under-resourced or when priorities shift before projects are completed. He provides frameworks for deciding when to pay down technical debt versus when to keep building, and for planning large-scale migrations that don’t stall halfway through.
The organizational design chapters cover career ladders, performance reviews, and the mechanics of running an engineering department. Larson includes specific templates and frameworks (including the concept of a “systems model” for engineering management) that can be adapted to different organizations.
For founders scaling an engineering team, the book fills a gap that most management books leave empty. The interpersonal skills covered in books like The Manager’s Path are necessary but not sufficient. You also need to know how to structure teams, allocate resources, and build processes that work at 20 people and still work at 200. That’s what this book covers.
The writing is dense and organized more like a reference manual than a narrative. Larson packs a lot of ideas into relatively few pages, and some sections require multiple reads to fully absorb. The style is analytical and precise, reflecting his engineering background. Some readers will miss the storytelling found in other management books, but the density of actionable ideas per page is unusually high.
