liveBook · Manning

Chapter 9: Measuring what matters

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

The chapter introduction frames metrics as a way to expose hidden system problems and judge whether measured improvement is real.

After this chapter you will be able to

What it builds on

Section by section

Introduction

The chapter introduction frames metrics as a way to expose hidden system problems and judge whether measured improvement is real.

Key terms: metrics, value stalls, queues, wrong metrics, busywork, game dashboards, improving outcomes

9.1 Why measure? Making problems visible

This section shows why measuring end-to-end delivery time, rather than local activity, makes hidden delays in software delivery visible.

Key terms: system instead of the station, lead time, activity time, activity ratio, TIMWOODS-centric waste

9.1.1 Measurement for learning versus ranking

This section explains why team metrics should reveal system problems for improvement rather than rank individuals, which can hide problems and encourage gaming.

Key terms: variation, cycle time, system pattern, driving out fear, andon cord, information flow, management by results, management by means, measure the system, not the person

9.1.2 The optimization trap

This section shows how targeting a metric can undermine the system it measures, and how to use metrics to investigate and improve the process instead.

Key terms: Goodhart's Law, diagnostic signal, gamification, change failure rate, gemba, numerical target, process, production boards, local optimization, bottleneck

9.2 Lean metrics for developers

This section reframes four flow metrics as ways to observe how everyday developer work moves or stalls.

Key terms: flow metrics, lead time, cycle time, activity time, activity ratio

9.2.1 Lead time

Defines lead time as the full request-to-delivery journey and shows how to measure and interpret it to find workflow delays without turning the metric into a target.

Key terms: lead time, request to delivery, system friction, engineering intelligence platforms, observability tools, issue tracker events, commit timestamps, deploy logs, median, p50

9.2.2 Cycle time

This section defines cycle time and shows how to use it to locate delays, evaluate improvements, and learn without ranking developers.

Key terms: cycle time, lead time, Definition of Ready (DoR), Definition of Done (DoD), batch size, queue time, WIP limits, control chart, control limits, decomposition

9.2.3 Activity time

This section uses activity time and activity ratio to reveal hidden waiting, diagnose where flow slows, and test improvements without treating the measures as productivity targets.

Key terms: activity time, elapsed time, value stream map, queue time, activity ratio, review windows, value stream, queue, activity type, diagnostic lens

9.2.4 Beyond the fundamentals

Extends flow measurement into production and shows how to use operational metrics to locate problems without turning them into scorecards.

Key terms: MTTR, Mean Time to Restore, critical incidents, deployment frequency, batch size, continuous delivery, smooth flow, bottlenecked, chaotic, stalled

9.3 Avoiding vanity metrics and metric gamification

The section shows how activity-based metrics can reward behavior that worsens delivery, and how paired system metrics and gradual replacement make measurement more useful.

Key terms: vanity metric, value delivery, local measurements, system measurements, metric gamification, cycle time, coherent change, system improvement, paired metrics, guardrail

9.4 Visual dashboards for continuous improvement

This section reframes a Kanban board as a live visual tool for diagnosing flow, not merely tracking ticket status.

Key terms: kanban, visual management system, inventory tracking, flow diagnosis, pull-based system, column depths, queues, WIP limits, ageing items, blocked indicators

9.4.1 From flow signals to flow dashboards

This section shows how to turn flow metrics into a useful team dashboard that reveals trends without becoming stale, overwhelming, or a tool for ranking people.

Key terms: Kanban board, flow dashboard, visual management, activity ratio, MTTR trend, deployment frequency, change failure rate, lead time trend, median, cycle time distribution

9.4.2 Making it work in practice

This section explains how to make flow dashboards useful for continuous improvement by showing patterns, revealing stalled work, and making the effects of changes visible.

Key terms: trends, snapshots, time series data, baseline, distributions, averages, bimodal distribution, classification, improvement experiment, activity ratio

9.5 Exercise: Calculate your current lead time

This exercise uses a representative sample of completed work to calculate delivery times, locate delays, and test one measurable improvement.

Key terms: completed changes, representative sample, active working time, lead time, cycle time, wait time, activity ratio, review queue, CI, rework

9.6 Summary

Where this is used later

Concepts explained in this chapter

← Chapter 8: Root cause thinking for developers Chapter 10: Kaizen: Continuous improvement →

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.