Improvement Across Cycles: how small gains compound.
Chapter 13 · “Improvement Across Cycles” · by Vinay Pasricha
Why does continuous improvement take many cycles to pay off?
Chapter 13 argues that execution rarely reveals its truth in a single cycle. The first run teaches basic lessons: whether the sequence works, roughly what it produces, where the major barriers are. The system’s real limits show up only across several cycles, which is why the Capacity Expansion Engine is cyclical. The executor who expects improvement from one cycle is often disappointed; the one who expects it to compound over five, ten or twenty understands the doctrine.
The chapter describes how constraints evolve. Early ones tend to be obvious: a missing process step, a missing tool, unclear communication. Next come subtler ones, such as a flaw in the design of the sequence or an inefficient handoff. By the fifth or tenth cycle they can be sophisticated: decision-making before execution begins, how fast the team learns, or an environment changing faster than the team can adapt. New constraints appearing is a sign the doctrine is working; the same constraint returning every cycle means the Act stage did not address it.
Returns diminish, since early cycles often bring dramatic gains and later ones smaller, but small gains compound. The book’s example is a team improving delivery speed by 5%, then another 5%, then 3% over successive cycles. The chapter adds that not every constraint is worth addressing, that depth in a few critical processes generally beats modest improvement everywhere, and that past gains must be watched for backsliding.
The year-by-year version of this compounding is set out in Chapter 4, The Capacity Expansion Engine.
But even small improvements across many cycles compound into substantial gains.
— Chapter 13, “Improvement Across Cycles”
Chapter 13 in full.
The complete text of “Improvement Across Cycles”, 664 words, as published in the manuscript on this site.
When the constraint is a leadership seat.
Vinay Pasricha leads searches for leadership and top-management roles in India: CXOs, the founder’s bench and functional heads. Tell him about the organisation and the role. The enquiry is recorded and sent to him directly.
