An Elegant Puzzle: Systems of Engineering Management

Will Larson’s “An Elegant Puzzle: Systems of Engineering Management” isn’t your typical management how-to. It’s a candid, sometimes dry-eyed exploration of the systemic challenges behind leading engineering teams in fast-growing tech companies like Digg, Uber, and Stripe. The book argues that most management headaches aren’t caused by flaky employees or clueless bosses but by the organizational systems themselves. In other words, the problem is often the way the machine is built, not just the people running it.

Larson’s core message is simple but often ignored: engineering management should be treated as a systems problem. That means looking beyond individual behaviors and focusing on structures—team size, workflows, career paths, and technical debt. He’s not selling quick fixes or feel-good leadership mantras. Instead, he offers practical, tested strategies grounded in real-world experience.

One of the standout ideas is the sweet spot for team size. Larson suggests that a manager effectively handles about six to eight engineers. Too few, and you risk micromanagement; too many, and things slip through the cracks. This isn’t a magic number but a guideline to keep communication manageable and maintain a healthy feedback loop. When teams get overwhelmed—say, the backlog balloons and morale tanks—his advice is refreshingly straightforward: add more people. It sounds obvious, but in practice, managers often resist because of budget or process inertia.

Another big theme is the relationship between technical work and feature development. Larson warns against mixing technical migrations or refactoring with feature work. If you try to do both simultaneously, you end up with chaos, delays, and frustrated engineers. Instead, he advocates for decoupling these efforts so that technical debt gets the focused attention it deserves without dragging down feature velocity.

Career ladders get a thoughtful treatment too. Larson pushes for designing paths that let engineers progress without forcing them into management roles. Not everyone wants to be a people manager, and good organizations recognize that. By providing parallel tracks—technical and managerial—you keep talent engaged and reduce the pressure on managers to be the only route to advancement.

The book is packed with examples from high-growth tech environments, which is both its strength and limitation. If you’re managing a scrappy startup or a mature, slow-moving company, some advice might feel out of touch or hard to apply. Larson’s systems-thinking lens is sharp, but it sometimes glosses over the messy human and political realities that don’t fit into neat frameworks. People aren’t just cogs; they bring unpredictability, emotions, and power plays that resist systematization.

Ultimately, "An Elegant Puzzle" is a toolbox for engineering leaders who want to move beyond vague leadership platitudes and understand the levers that actually move the needle. It’s about making engineering management less of a dark art and more of a science—without pretending it’s easy or formulaic. For anyone who’s wrestled with scaling teams, managing technical debt, or figuring out how to grow engineers without burning them out, Larson offers a grounded, no-nonsense perspective that’s rare in this genre.