The Principles of Product Development Flow: Second Generation Lean Product Development
Source: https://www.amazon.com/Principles-Product-Development-Flow-Generation/dp/1935401009 ↗
Reinertsen writes the book most "lean" advocates should have written and didn't: a rigorous, economics-based account of why batches, queues and variability govern the speed of product development.
The argument is quantitative — cost of delay, WIP limits, capacity utilisation curves — and often counterintuitive.
Running teams at 100% utilisation destroys throughput; holding inventory has a measurable cost; smaller batches are almost always cheaper end-to-end than large ones.
It is the deepest book on the page about why shipping faster is not about working harder.
For a product director it clarifies the physics of the system you manage, not the psychology; dense, essential, worth re-reading every year.
Central argument
Reinertsen argues that product development speed is governed by economic and queueing-theory principles — specifically that queues, batch sizes, variability, and capacity utilisation are the true determinants of throughput, not effort or motivation. His central finding is that running teams at or near 100% utilisation is catastrophically expensive because it causes queues to grow non-linearly, destroying flow; the fix is not to work harder but to reduce WIP, shrink batch sizes, and manage the cost of delay explicitly. The book reframes 'lean' away from its manufacturing interpretations and toward a quantitative, economics-first discipline where every process decision has a measurable financial consequence.
Critique
The framework is built primarily on hardware and embedded-systems product development contexts, and its quantitative rigour — cost-of-delay calculations, capacity utilisation curves — assumes a degree of measurement infrastructure and process visibility that most software product organisations simply do not have. A thoughtful reader might argue that the prescriptions are easier to apply in domains with relatively stable, estimable work than in early-stage discovery-heavy products where demand, scope, and value are all deeply uncertain. There is also an implicit assumption that the bottleneck is throughput rather than direction — that you are building the right things — which the book largely brackets as out of scope.
Why it matters for product
For a product director, the most actionable implication is organisational: team utilisation targets and portfolio loading decisions are not HR or resourcing questions but physics questions with compounding throughput consequences — running squads at near-full capacity to appear efficient is a direct tax on delivery speed. The cost-of-delay framing also gives product leaders a principled vocabulary for prioritisation conversations with finance and executives, replacing gut-feel sequencing with a calculation that weighs the economic cost of waiting against the cost of doing. And the batch-size argument directly challenges common planning habits — large quarterly roadmap commitments and infrequent release cycles — by showing that the hidden carrying cost of large batches routinely exceeds the apparent coordination savings.