Question 1

Why does Reinertsen argue that running teams at 100% utilization actually slows down product development?

Accepted Answer

Reinertsen uses queueing theory and economic analysis to show that maxing out capacity utilization creates queues and increases cycle time. When teams have no slack, even small delays cascade, and the cost of that delay compounds across the system. It's a counterintuitive insight grounded in mathematics, not motivation—the physics of bottlenecks, not team effort.

Question 2

How does this book connect to lean methodology, and where does it diverge?

Accepted Answer

Reinertsen provides the rigorous economic foundation that many lean advocates assume but never prove. While lean focuses on waste elimination and flow, this book quantifies *why* flow matters through cost-of-delay analysis, WIP limits, and batch economics—making it the theoretically grounded argument that typical lean books lack.

Question 3

What makes this relevant for product directors specifically?

Accepted Answer

Rather than prescribe team dynamics or processes, Reinertsen reveals the underlying physics of the system you manage: how batches, queues, and variability govern shipping speed. This helps directors make data-driven trade-offs between capacity, batch size, and cycle time—understanding the *why* behind faster shipping, not just the *how*.