liveBook · Manning

Kaizen event

As explained in Build High Value Software Systems

A focused, time-boxed effort in which a team works intensively to improve a specific process problem.

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

How Build High Value Software Systems covers it

How deep it goes
Prescribes choosing friction, baselining, scoping, changing, remeasuring, and standardizing or reverting, while leaving the specific change open.
Examples
Uses slow PR reviews, flaky CI, manual deploys, onboarding, and review-SLA or reviewer-assignment changes.
What it assumes
Choose a recurring process friction and measure its baseline before the event.
What you can do after
Apply a measured improvement cycle to change one team process, compare results after one or two sprints, and standardize or revert.
How it connects
Connects Lean manufacturing, continuous improvement, process measurement, and standard work.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Build High Value Software Systems. The section links point to the parts of the book it draws on.