Part 13 · 1 chapters · ~8 min
An Elegant Puzzle
Will Larson's systems of engineering management, read from a staff engineer's seat: team sizing, the four team states and their fixes, migrations as the scalable fix for debt run as de-risk, enable and finish, stocks-and-flows models of organisations, and metrics with baselines and counter-metrics.
15
An Elegant Puzzle
A management book that staff engineers read because the problems they solve sit in the same systems managers run: team shape, migrations, metrics and how organisations change.
| migration phase | what the staff engineer does | example: moving money flows to explicit state machines |
|---|---|---|
| de-risk | design doc; migrate the hardest, most representative flow first | convert the loan agreement flow with guarantors first, since it has the most states |
| enable | tooling, docs and examples so other teams migrate themselves | a shared machine helper, a lint rule against ad-hoc status booleans, a guide with the first flow as the example |
| finish | track every remaining case; do the last ones; delete the old path | a dashboard of unmigrated flows; take the last two; remove the old helpers |
why finishing matters
Half-finished migrations leave two ways of doing everything, which is worse than either. Owning the last 20% is a classic staff signal, because nobody else is incentivised to do it.
AN ELEGANT PUZZLE
Will Larson, 2019: systems of engineering management, useful to staff engineers who work beside managers
swipe the figure sideways, or tap expand for full screen
1/6
Sizing teams
Sizing: Larson suggests managers support six to eight engineers, and that teams of fewer than four struggle to sustain on-call, absorb leave and hold knowledge. When a team grows past eight, split it into two with a clear boundary rather than growing management layers early.