Chapter 10: Kaizen: Continuous improvement
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
- Kaizen Beyond Code Cleanup. Distinguish Kaizen from refactoring or a one-off fix by describing how it improves the workflows, feedback loops, standards, and tools that produce code.
- Measured Improvement Habit. Describe Kaizen's observe-measure-change-measure-again cycle and explain why repeating it matters more than gaining a one-time insight.
- Kaizen as a disciplined practice. Explain what Kaizen means in this section and why improvement requires a regular practice rather than good intentions.
- Beta’s repeated improvement cycle. Trace how Team Beta selected, tested, and retained process changes, and explain how repeated small changes produced results that Team Alpha did not achieve.
- Single friction point improvements. Distinguish a small Kaizen change from a larger improvement project, using the CI pipeline example.
- Compounding small gains. Explain why successive small Kaizen changes can produce substantial improvement over time.
- Improvement alongside daily work. Explain why continuous improvement is a default habit of noticing and acting on friction during ordinary work, rather than an occasional initiative or a task deferred until later.
- Protected improvement cadence. Justify a recurring, protected slot for improvement and describe how choosing one friction point for a short timebox can turn good intentions into action.
- Frontline knowledge of friction. Explain why the people doing the work should identify process improvements, and how a top-down change can miss the actual constraint.
- Repeatable improvement cycle. Trace the Kaizen cycle from observing real work and establishing a baseline through a specific change, comparable remeasurement, and a decision to standardize or revert.
- Different targets of improvement. Distinguish refactoring from Kaizen by what each aims to improve: internal code structure versus the workflow, tooling, and standards that move value from idea to production.
- Complementary improvement practices. Justify why a team needs both refactoring and Kaizen, including why process improvements can have broad effects across future work.
- Retrospective and value stream scope. Distinguish improving a team's iteration rituals from improving the end-to-end flow of value, and explain why a team can run effective ceremonies while delivery remains slow.
- Retrospective action item failures. Explain why retrospectives that produce lists of action items often lead to the same complaints next sprint: too many items dilute focus, vague items do not specify an actionable change, and unmeasured items cannot be judged.
- One-friction-point Kaizen cycle. Trace the retrospective cycle: review the previous improvement and its results, choose one high-impact friction point addressable next sprint, define and implement a change, then measure it at the next retrospective and update standard work if it succeeds.
- Measurable Kaizen card. Describe how a Kaizen card makes a proposed improvement testable by recording the problem, baseline, specific change, owner, measure, and target, as in the PR review-time example.
- A3 as improvement proposal. Explain why proposing a fix alone can fail and how an A3 gives a decision maker the problem, proposed action, investment, impact, and way to judge success.
- Audience-specific impact language. Explain how to tailor an A3's language to its reader while keeping its structure, and why measured results matter afterward.
- Developer improvement scope. Explain why many useful improvements do not require approval, and distinguish these changes to process, tooling, or standards from refactoring.
- Shared change communication. Distinguish the communication needed for a personal workflow change from that needed for shared infrastructure, and describe what a useful heads-up contains.
- Act measure share pattern. Trace the developer-led Kaizen pattern from noticing friction through measuring and sharing the outcome, and explain why sharing matters.
- Friction log and priorities. Describe how to record interruptions and unnecessary work, then review the log weekly to choose an improvement.
- Evolving AI standard work. Explain how to use observations about AI output and effort to adjust personal AI practices.
- Four threats to improvement habits. Explain why improvement habits fade when they lack a trigger or visible progress, demand too much time, or remain isolated.
- Kaizen anchors in existing routines. Describe how to attach a small Kaizen check to a routine already being performed, adding one anchor at a time.
- Friction logging and prioritization. Describe how to log a day of workflow friction, group the entries, and choose a target for improvement.
- Change evaluation and repetition. Trace what to do after choosing a change: implement it, keep logging its effects and new friction, compare results with the baseline, and repeat the cycle.
What it builds on
- Gemba and Kaizen in software development (chapter 2) · The introduction of Gemba and Kaizen as Lean practices.
- Why measure? Making problems visible (chapter 9) · Measurement as a way to make problems visible.
- Lean metrics for developers (chapter 9) · Selecting metrics to describe a friction point.
- Understanding flow, from idea to production (chapter 6) · The idea of flow from idea to production.
- A3 reports: Structured, blameless problem solving (chapter 8) · A3 reports as a structured problem-solving format.
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.
- Kaizen Beyond Code Cleanup: Distinguish Kaizen from refactoring or a one-off fix by describing how it improves the workflows, feedback loops, standards, and tools that produce code.
Why it matters: It shifts attention from repeatedly fixing symptoms to improving the conditions that create them. - Measured Improvement Habit: Describe Kaizen's observe-measure-change-measure-again cycle and explain why repeating it matters more than gaining a one-time insight.
Why it matters: Checking and repeating small changes helps improvements survive beyond a single observation or cleanup effort.
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.
- Kaizen as a disciplined practice: Explain what Kaizen means in this section and why improvement requires a regular practice rather than good intentions.
Why it matters: It turns a desire to improve into work the team actually makes time to do. - Beta’s repeated improvement cycle: Trace how Team Beta selected, tested, and retained process changes, and explain how repeated small changes produced results that Team Alpha did not achieve.
Why it matters: Beta’s example shows how a repeatable improvement cycle can change delivery results without a heroic overhaul.
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.
- Single friction point improvements: Distinguish a small Kaizen change from a larger improvement project, using the CI pipeline example.
Why it matters: A small, targeted fix can improve a workflow without waiting for a larger project to be approved and completed. - Compounding small gains: Explain why successive small Kaizen changes can produce substantial improvement over time.
Why it matters: A modest fix can be worthwhile not only for its immediate benefit but also for the improvements it makes possible next.
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.
- Improvement alongside daily work: Explain why continuous improvement is a default habit of noticing and acting on friction during ordinary work, rather than an occasional initiative or a task deferred until later.
Why it matters: Small sources of friction are more likely to get fixed when improvement is part of the work. - Protected improvement cadence: Justify a recurring, protected slot for improvement and describe how choosing one friction point for a short timebox can turn good intentions into action.
Why it matters: A recurring slot gives improvement work a chance to happen despite competing feature deadlines.
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.
- Frontline knowledge of friction: Explain why the people doing the work should identify process improvements, and how a top-down change can miss the actual constraint.
Why it matters: Asking the people who encounter a delay helps a team improve the real constraint instead of an assumed one. - Managerial support for Kaizen: Describe the manager's role in enabling worker-led Kaizen.
Why it matters: People need room and tools to turn firsthand observations into tested improvements.
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.
- Evidence of practiced Kaizen: Distinguish a team that practices Kaizen from one that only claims a continuous-improvement mindset by asking for a recent process change, before-and-after measurement, and the decision made about the change.
Why it matters: Concrete answers show whether improvement is an actual practice rather than a vague aspiration. - Repeatable improvement cycle: Trace the Kaizen cycle from observing real work and establishing a baseline through a specific change, comparable remeasurement, and a decision to standardize or revert.
Why it matters: The cycle turns a complaint about friction into an improvement whose effect can be checked. - Event and daily Kaizen: Distinguish a focused Kaizen event from a daily improvement habit and explain why the section says both scales matter.
Why it matters: Improvement need not wait for a scheduled event, but some problems benefit from concentrated team effort.
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.
- Different targets of improvement: Distinguish refactoring from Kaizen by what each aims to improve: internal code structure versus the workflow, tooling, and standards that move value from idea to production.
Why it matters: A cleaner codebase does not, by itself, fix a broken delivery process. - Purpose of code changes: Apply the section’s target-based distinction to code-related changes, such as a formatting pre-commit hook or staging deployment automation.
Why it matters: The kind of file changed does not tell you whether an improvement is refactoring or Kaizen. - Complementary improvement practices: Justify why a team needs both refactoring and Kaizen, including why process improvements can have broad effects across future work.
Why it matters: A team can have excellent code yet still lose days to manual deployments and slow reviews.
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.
- Retrospective and value stream scope: Distinguish improving a team's iteration rituals from improving the end-to-end flow of value, and explain why a team can run effective ceremonies while delivery remains slow.
Why it matters: A better meeting does not necessarily mean work reaches customers sooner. - From discussion to improvement: Explain why shifting a retrospective's lens from individual events to the value stream is the first step toward Kaizen rather than merely discussing work.
Why it matters: Changing the question helps a team notice delivery problems that meeting-focused discussion misses.
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.
- Retrospective action item failures: Explain why retrospectives that produce lists of action items often lead to the same complaints next sprint: too many items dilute focus, vague items do not specify an actionable change, and unmeasured items cannot be judged.
Why it matters: Naming the failure modes helps a team avoid repeating a retrospective without changing its work. - One-friction-point Kaizen cycle: Trace the retrospective cycle: review the previous improvement and its results, choose one high-impact friction point addressable next sprint, define and implement a change, then measure it at the next retrospective and update standard work if it succeeds.
Why it matters: A small change that is implemented and checked can compound across sprints. - Measurable Kaizen card: Describe how a Kaizen card makes a proposed improvement testable by recording the problem, baseline, specific change, owner, measure, and target, as in the PR review-time example.
Why it matters: The card gives the team a concrete way to decide whether its proposed fix worked. - Kaizen log and visibility: Explain why every Kaizen card, including unsuccessful ones, goes into a log and how a dedicated Kanban board makes proposed, active, measuring, standardized, and reverted improvements visible.
Why it matters: A visible history lets the team learn from experiments that succeeded and those it reverted.
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.
- A3 as improvement proposal: Explain why proposing a fix alone can fail and how an A3 gives a decision maker the problem, proposed action, investment, impact, and way to judge success.
Why it matters: A complete proposal helps an improvement compete with other priorities rather than being dismissed as work on something that is not broken. - Self-contained asynchronous case: Describe how an A3 can support approval and discussion without requiring a meeting.
Why it matters: Improvements need not wait for everyone to find time for the same meeting. - Audience-specific impact language: Explain how to tailor an A3's language to its reader while keeping its structure, and why measured results matter afterward.
Why it matters: An improvement is more likely to gain support when its impact is expressed in the decision maker's terms and its results are visible.
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.
- Developer improvement scope: Explain why many useful improvements do not require approval, and distinguish these changes to process, tooling, or standards from refactoring.
Why it matters: You can improve everyday development work without waiting for a larger initiative. - Measured CI improvement: Describe how the developer in the CI example found and changed sources of delay, then checked the result.
Why it matters: The example shows how a modest workflow change can produce a visible, measurable gain. - Shared change communication: Distinguish the communication needed for a personal workflow change from that needed for shared infrastructure, and describe what a useful heads-up contains.
Why it matters: Acting without approval should not leave teammates surprised by changes to shared workflows. - Act measure share pattern: Trace the developer-led Kaizen pattern from noticing friction through measuring and sharing the outcome, and explain why sharing matters.
Why it matters: Sharing measured results helps make small improvements a normal team habit.
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.
- Friction log and priorities: Describe how to record interruptions and unnecessary work, then review the log weekly to choose an improvement.
Why it matters: A record of friction helps you improve a recurring problem rather than react only to the latest annoyance. - Daily process improvement habit: Explain the purpose of a short daily Kaizen block and why repeated manual tasks are candidates for automation.
Why it matters: A modest improvement habit can save effort that would otherwise be spent repeatedly working around the same problem. - Measured skill development loop: Trace the measure-change-measure approach in the AI-assisted code review example.
Why it matters: Measuring before and after a focused change helps distinguish an effective learning adjustment from a plausible-sounding one. - Evolving AI standard work: Explain how to use observations about AI output and effort to adjust personal AI practices.
Why it matters: Observing both useful output and rework helps you use AI where it improves your workflow.
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.
- Four threats to improvement habits: Explain why improvement habits fade when they lack a trigger or visible progress, demand too much time, or remain isolated.
Why it matters: Recognizing these failure patterns helps you design an improvement habit that lasts. - Kaizen anchors in existing routines: Describe how to attach a small Kaizen check to a routine already being performed, adding one anchor at a time.
Why it matters: Anchoring makes improvement easier to notice and repeat during work you already do. - Renewing a stale Kaizen practice: Explain why improvement may feel stale after early wins and describe the three suggested ways to find fresh opportunities.
Why it matters: A plateau need not end improvement; changing perspective can reveal problems that have become harder to see.
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.
- Friction logging and prioritization: Describe how to log a day of workflow friction, group the entries, and choose a target for improvement.
Why it matters: A friction log makes the choice of what to improve come from your actual work rather than a guess. - Measurable Kaizen change card: Explain how to turn one selected friction item into a Kaizen card with a baseline, a specific change, and a way to measure the result.
Why it matters: Writing down the baseline and measure gives you something concrete to compare after the change. - Change evaluation and repetition: Trace what to do after choosing a change: implement it, keep logging its effects and new friction, compare results with the baseline, and repeat the cycle.
Why it matters: Checking both the benefits and costs of a change keeps Kaizen from becoming a series of untested fixes.
Key terms: friction log, waiting, rework, searching, context switching, manual work, Kaizen card, baseline, change, measure
10.7 Summary
Where this is used later
- Decisions that cannot wait (chapter 11) · Uses the idea of kaizen to improve an existing standard.
- A system that flows (chapter 11) · Kaizen provides the idea of continuous improvement.
- Standard work for operations and incident response (chapter 12) · Improvements are made by the people who do the work.
- Scaling improvements across teams (chapter 15) · The principle that the people doing the work participate in designing improvements.
- Exercise: Plan your first team Kaizen event (chapter 15) · The principle that improvements come from the people who do the work.
- Production Kaizen (chapter 12) · Supplies an improvement cycle that can be applied to production work.
- Sustaining and scaling the problem-solving habit (chapter 13) · Assumes retrospectives as a recurring improvement practice.
- Building a culture of continuous learning (chapter 15) · Retrospectives as a structured improvement practice.
Concepts explained in this chapter
- continuous improvementA feedback loop is a process in which information about outcomes is returned to influence subsequent decisions or actions.
- friction logA record of workflow friction, such as waits, context switches, manual steps, and moments of confusion.
- kaizen cardA record of a proposed process improvement that specifies its baseline, change, owner, and target outcome.
- retrospectiveA team meeting for reflecting on recent work and identifying improvements.
- measure-change-measure cycleA recurring process of observing work, measuring it, making a change, and measuring again.
- A3 reportA structured Lean problem-solving approach that documents an issue, its analysis, and proposed countermeasures in a concise report.
- value streamA value stream is the complete sequence of activities and handoffs through which work produces an outcome for a customer or user.
- refactoringRefactoring is the restructuring of existing software without changing its externally observable behavior.
- GembaThe actual place where work occurs and value is created, viewed in Lean management as the location for direct observation.
- baselineAn initial measurement of a process or system that provides a reference for comparison with later measurements.
- kaizen eventA focused, time-boxed effort in which a team works intensively to improve a specific process problem.
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.
