Games Contact us
Select Page
Home>Book Taste>An Elegant Puzzle

Taste Note - Amazon Software Development Best Sellers

An Elegant Puzzle: Systems Thinking for Running an Engineering Organization

A Kurums Book Taste review of An Elegant Puzzle for technology leaders who need their engineering organization to scale without stalling.

TechnologyTaste NoteAmazon bestseller
An Elegant Puzzle book cover

Why this book fits Kurums

Most technology leaders are promoted for building software and then asked to build an organization. Will Larson, who led engineering teams at Stripe and Uber, wrote this book for exactly that moment. It treats team sizing, technical debt, reorganizations, hiring and career ladders as design problems with inputs, constraints and predictable failure modes, not as matters of charisma.

For the Kurums Technology audience, the value is vocabulary and leverage. When the CFO asks why the platform team needs two more engineers, or the CEO asks why delivery slowed after a reorg, this book gives you a model you can explain in five minutes and defend with data. It turns gut feel about headcount and priorities into a system other leaders can inspect.

What the book argues

Larson starts with organizational design. Teams have a workable size: a manager can usually support six to eight engineers, a manager of managers four to six managers, and a group smaller than four is rarely a real team because it cannot absorb vacations, departures or on-call load. Sizing badly creates managers who are either idle or drowning, and both outcomes show up later as attrition and missed dates.

He then describes four states a team can be in: falling behind, treading water, repaying debt and innovating. Each state has a different fix. A team falling behind needs more people, a team treading water needs less work in progress, a team repaying debt needs time, and an innovating team needs slack protected. The central warning is that system fixes are slow and tactical shuffles, such as moving individuals between teams to plug gaps, usually make the whole system worse.

The remaining chapters apply the same thinking to tools and people. Migrations are presented as the main scalable way to retire technical debt, run in three stages: de-risk, enable, then finish. Strategy and vision documents are separated, with strategy grounded in current reality and vision describing the future. Hiring is treated as a funnel to instrument, and career ladders and performance processes as systems that must be designed for fairness, not improvised manager by manager.

Key ideas, translated to your desk

Diagnose the team state first

Before approving headcount or a new project, decide whether the team is falling behind, treading water, repaying debt or innovating. The right investment depends on the state, and the wrong one wastes a quarter.

Finish migrations, do not just start them

Old and new systems running in parallel are often the most expensive state of all. Fund the last 20% of a migration as seriously as the first, and make the platform team own completion.

Write strategy and vision separately

A strategy document names the problem, the constraints and the specific choices for the next year. A vision document describes where you want to be in a few years. Mixing them produces documents nobody can act on.

Use it at work

  • Map every team against the four states and attach one fix to each before the next planning cycle.
  • Check manager spans against the six-to-eight guideline and flag teams of three or fewer for merger or support.
  • List every half-finished migration, name an owner and set a completion date with a measurable end state.
  • Instrument your hiring funnel from sourcing to accepted offer and review conversion rates monthly.

Read it if

  • You manage managers in engineering and keep fighting the same staffing and priority battles each quarter.
  • You are planning a reorg and want a model for team size and ownership before you redraw the chart.
  • You liked The Manager's Path and want the organizational systems view that comes next.

You can skip it if

  • You lead a single small team and need day-to-day people management basics first.
  • You want a narrative book; this is a collection of essays and checklists that rewards rereading more than a cover-to-cover read.
  • Your organization has under twenty engineers, where many of its structural problems have not appeared yet.

This book appears in

Curated Tasting Menus that chain this title into a reading route.

Discover more from Kurums | Business Intelligence

Subscribe now to keep reading and get access to the full archive.

Continue reading