liveBook · Manning

Measure-change-measure cycle

As explained in Build High Value Software Systems

A recurring process of observing work, measuring it, making a change, and measuring again.

The measure-change-measure cycle improves the workflows, feedback loops, standards, and tools around code—not just the code itself. It turns recurring friction into small changes whose effects can be checked. section 10.0

Run the cycle on a specific friction point:

  • Observe the actual workflow rather than relying on guesses or memory. section 10.1.4
  • Measure the problem with a baseline metric that fits the friction point. section 10.1.4
  • Make one small, specific change so its effect can be isolated. section 10.1.4
  • After one or two sprints, repeat the measurement using the same metric and method. section 10.1.4
  • Keep and document the change if it helps without degrading something else; otherwise revert it and test another approach. section 10.1.4

Baseline a release process

Instead of calling releases painful, record the 11 manual steps, average two-hour duration, and three failed releases in six months. That baseline gives a later comparison a specific measure. section 10.1.4

Table 10.1 Mindset versus method
Characteristic
Mindset team
Method team
Frequency
Improves when something breaks
Improves every sprint
Scope
Reacts to the loudest pain
Selects based on measurement
Tracking
“We fixed some stuff.”
Before/after data for each change
Sustainability
Bursts of effort, then drift
Steady compounding
Knowledge
Improvements live in one person's head
Changes documented in standard work

Compare a measured, documented improvement method with an improvement mindset that lacks consistent tracking. section 10.1.4

How Build High Value Software Systems covers it

How deep it goes
Defines the steps, gives measurement and change examples, and adds a standardize-or-revert decision after comparing the same metric.
Examples
Uses PR timing, pipeline duration, context switches, release steps, review SLAs, PR-size limits, and automatic reviewer assignment.
What it assumes
Starts from direct workflow observation and a matching baseline metric rather than assuming memory or impressions are reliable.
What you can do after
Apply a repeatable workflow for testing a small change against a baseline, then standardize or revert it.
How it connects
Connects Kaizen with Gemba observation, refactoring, workflow metrics, and documented standard work.

Also explained in

Compare how 2 books explain measure-change-measure cycle →

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.