Treat Pipeline Minutes as a Product Metric
CI duration is not a platform vanity chart — it is a multiplier on every engineer’s weekly capacity.
When a pipeline takes twenty-five minutes, every experiment costs a coffee break. Teams that only celebrate deploy frequency often miss the quieter tax: developers batching changes because feedback is too slow, or skipping tests locally because “CI will catch it.” Both behaviours inflate risk while feeling rational in the moment.
Promote median and p95 pipeline duration to the same dashboard as cycle time. Assign an owner who can change cache keys, shard suites, and retire obsolete jobs without a three-week ticket debate. Small wins compound — shaving three minutes off a hot path can return dozens of engineer-hours each sprint.
Flaky tests deserve a separate queue with a kill-or-fix deadline. A red build that “usually passes on retry” trains people to ignore the signal. Instrument retries, publish flake owners, and celebrate deletions as loudly as new features.