A kaizen event is a focused, time-boxed team effort to improve one specific process problem. In software, that might mean slow PR reviews, flaky CI, manual deploy steps, or long developer onboarding. It is not a hackathon or refactoring sprint: choose a measurable process problem and aim for a result. section 15.8 section 10.1.4
Plan the improvement around a before-and-after comparison:
- Choose a recurring process friction point and record its current state with a metric. section 15.8
- Define one improvement and a measurable target; narrow the scope if it is too large for the available time. section 15.8
- Schedule a two-to-four-hour session with the people who do the work. Make one small, specific change. section 15.8 section 10.1.4
- After one or two sprints, measure the same thing in the same way. If it improved without degrading something else, document the new standard; otherwise, revert and try another approach. section 15.8 section 10.1.4
Reducing PR review time
If reviews take a median of 2.3 days, set a one-day target. The team might change its review SLA or automate reviewer assignment, then compare review times after one or two sprints. section 15.8 section 10.1.4
Events concentrate attention on larger problems; small frictions can be measured and improved as part of everyday work. Both scales matter: an event is one focused cycle, not a replacement for continuous improvement. section 10.1.4
