Throughput Is Not a Vanity Chart

Throughput becomes useful when it is tied to a defined change type, a stable observation window, and an honest account of what never reaches production. Raw deploy counts reward tiny toggles and punish carefully batched releases that still moved customer value.

We ask teams to name the unit of change they care about—customer-facing stories, API contracts, or infrastructure patches—then measure how often those units land safely. The baseline includes failed changes, not only green deploys.

Seasonality matters in Central-based product orgs with quarterly freezes and festival freezes. A two-week spike after a freeze is not a new delivery culture; it is a backlog clearing.

When leadership asks for a single number, we still report the caveats beside it. A number without its window and exclusions is decoration.