Base120 · Recursion
Recursive Improvement (Kaizen)
Continuously refine process through small, frequent enhancements
When to use
"Use when big-bang improvements are risky or infeasible. Make small, frequent enhancements that compound over time. The cumulative effect of many small improvements often exceeds the effect of rare large ones."
Example
"A team adopts a practice of one small improvement per week — better error messages, faster tests, clearer docs. After a year, 52 improvements have compounded into a noticeably better codebase, with no single change being risky."
Common misuse
"Making small improvements that are not aligned with a direction. Random small improvements do not compound; they accumulate as noise. Kaizen requires a target state to steer toward."