liveBook · Manning

Chapter 10: Kaizen: Continuous improvement

What you will learn in chapter 10 of Build High Value Software Systems

The introduction presents Kaizen as a sustained habit of making small, measured improvements to the development system, rather than occasionally cleaning up code.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The introduction presents Kaizen as a sustained habit of making small, measured improvements to the development system, rather than occasionally cleaning up code.

Key terms: Kaizen, refactoring, development system, observe, measure, change, measure again, Gemba

10.1 What Kaizen actually means

This section defines Kaizen as a scheduled discipline of small, measured process improvements and shows how repeated changes helped one software team reduce delivery friction.

Key terms: Kaizen, continuous improvement, structure and cadence, friction point, standard work, lead time

10.1.1 Small

This subsection explains how Kaizen improves one friction point at a time and why small, measurable changes can compound.

Key terms: Kaizen, friction point, project approach, compounding, sprint-by-sprint improvements

10.1.2 Continuous

Continuous Kaizen means acting on friction as part of everyday work and protecting a recurring time to turn improvement ideas into action.

Key terms: Kaizen, continuous improvement, friction, cadence, retrospective, friction point, timebox

10.1.3 By the people who do the work

This section explains why Kaizen improvements should be identified and tested by the people doing the work, with managers enabling them rather than prescribing fixes.

Key terms: Kaizen, Gemba, constraint, measurement tools

10.1.4 From mindset to method

The section turns continuous improvement from a stated mindset into a measurable cycle that can be practiced in focused events or daily work.

Key terms: Kaizen, mindset, continuous improvement, observe, measure, baseline, measure again, standardize or revert, Gemba, Kaizen event

10.2 Kaizen versus refactoring

The section distinguishes refactoring’s improvement of code from Kaizen’s improvement of the system that produces and delivers code, and explains why teams need both.

Key terms: refactoring, Kaizen, workflow, pre-commit hook, staging deployment, review friction, waste inside the code, waste around the code, process improvement

10.3 Retrospectives as structured Kaizen

The section explains why retrospectives become structured Kaizen only when they look beyond team rituals to where value stalls between request and delivery.

Key terms: retrospective, value stream, Lean Kaizen, lead time, events, Kaizen

10.3.1 Why retrospectives fail

This section shows why retrospective action lists often fail and how a one-improvement-per-sprint Kaizen cycle turns discussion into measured, lasting change.

Key terms: action items, before-and-after measurement, Kaizen, friction point, standard work, Kaizen card, baseline, change, owner, measure

10.4 A3 as a communication API for improvements

This section shows how an A3 makes a Kaizen improvement proposal understandable and actionable for decision makers, including readers who cannot meet with the proposer.

Key terms: A3, communication API, improvement proposals, asynchronously, calendar bottleneck, Expected Impact, Background, results, trust, autonomy

10.5 Developer-led Kaizen

Developer-led Kaizen turns friction within a developer’s control into small, measured improvements that are communicated when they affect others.

Key terms: personal Kaizen, sphere of influence, refactorings, CI, cache dependencies, parallelize independent stages, before/after numbers, personal workflow, shared infrastructure, heads-up

10.5.1 Personal practices

This section shows how developers can turn recurring friction, small process changes, and measured AI use into personal Kaizen habits.

Key terms: personal Kaizen, friction log, Kaizen cycle, daily Kaizen improvement calendar block, process improvement, automation, measure-change-measure, learning loop, AI-suggested review comments, AI-centric workflow

10.5.2 Anchoring your practices

The section explains how to sustain developer-led Kaizen by making improvement habits easy to repeat and finding new opportunities when progress feels stale.

Key terms: trigger, visible progress, Kaizen, Kaizen anchor, improvement sensor, rotate the observer, zoom out, revisit old improvements

10.6 Exercise: Run a personal Kaizen event

This exercise guides readers through a one-week personal Kaizen cycle: observe workflow friction, make one measurable change, compare results, and repeat.

Key terms: friction log, waiting, rework, searching, context switching, manual work, Kaizen card, baseline, change, measure

10.7 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 9: Measuring what matters Chapter 11: Architectures that flow →

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.