liveBook · Manning

Continuous improvement

As explained in Build High Value Software Systems

A feedback loop is a process in which information about outcomes is returned to influence subsequent decisions or actions.

A slow build, a review queue, or a deployment that depends on a manual checklist can become so familiar that nobody expects it to change. Continuous improvement, or Kaizen, treats that friction as information about the delivery system. The aim is not flawless work or more code output; it is to make small, measured changes to the workflows, tools, standards, and feedback loops that move an idea into production. section 1.1.1 section 10.0

Start at the Gemba: where work actually happens. Look at pull requests, CI runs, reviews, and deployments rather than relying only on a process diagram or a complaint. People doing the work can spot recurring waits and workarounds. Ask what conditions make a problem predictable, not who to blame for it. section 2.5 section 10.1.3

Use one friction point to run a repeatable cycle:

  • Observe the actual workflow and measure a baseline that matches the problem: review delay, pipeline time, rework, or manual steps. section 10.1.4
  • Make one small change whose effect you can isolate. Prefer a fix you can test soon over a broad redesign. section 10.1.1 section 10.1.4
  • After a short trial, measure the same thing in the same way. Keep and document the change if it helps without unacceptable side effects; otherwise revert or revise it. section 10.1.4

Catch lint failures before CI

A developer logs two lint-related CI failures in a week, each followed by a long rerun. They add a pre-commit linter, then keep logging what it catches and any new delay it causes. The following week has no lint-related CI failures; the hook takes eight seconds on a large commit. They keep the change, document setup, and share the before-and-after result. The point is not that every team needs this hook: the observed failure, baseline, trial, side effects, and decision form the improvement loop. section 10.6

Kaizen differs from refactoring by its target. Refactoring improves code structure without changing external behavior; Kaizen improves how work gets delivered, even when the fix requires code or configuration. A CI cache that shortens builds is Kaizen. Code review can also supply feedback: repeated justified exceptions may mean a standard needs updating, not stricter enforcement. section 10.2 section 4.4.3

Keep the loop alive alongside feature work. Pick one friction point at a recurring interval, or attach a quick check to an existing routine such as submitting a PR. Record what changed and whether it worked. If local friction has eased, look at handoffs and queues across the value stream: a smooth sprint can still end in a slow delivery. section 10.1.2 section 10.5.2 section 10.3

How Build High Value Software Systems covers it

How deep it goes
Details an observe-measure-change-remeasure cycle, including baselines, short trials, side effects, and decisions to standardize or revert.
Examples
Works through CI caching, review delays, deployment automation, and a pre-commit lint-hook experiment.
What it assumes
Assumes familiarity with pull requests, CI, reviews, and deployments while defining Kaizen and its distinction from refactoring.
What you can do after
Practice/perform a measured improvement cycle on personal or team workflows, then keep, revise, or revert the change.
How it connects
Connects Gemba, value streams, code review, standard work, refactoring, and delivery metrics.

Also explained in

Compare how 43 books explain continuous improvement →

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.