What is Change Failure Rate?

Change failure rate is the share of deployments that cause a failure in production and is a DORA measure of release stability. It balances the push for speed against the need for reliability. An inconsistent definition of 'failure' makes it hard to trust or compare. For context, elite teams sit at 0-15%; a rate climbing well above that suggests testing or release practices need strengthening. Treat an external benchmark as a reference point rather than a universal target: company stage, sector, customer mix, pricing model and measurement definitions can materially change what “good” looks like. Read Change Failure Rate alongside Deployment Frequency and MTTR; together these measures provide a more balanced view and reduce the risk of optimizing one number at the expense of the wider outcome.

Make sure the numerator and denominator cover compatible populations and periods, and avoid dividing by a partial or unusually small base. Use stable production boundaries and timestamp definitions, and distinguish planned work from incidents, rollbacks and failed deployments. Measure at service or team level and keep the start event, end event and production boundary stable; portfolio averages can hide a fragile component. A dashboard should show the current value, prior-period comparison and a trend rather than presenting one isolated reading.

Treat the metric as a prompt for system improvement: reduce batch size, automate safe delivery, strengthen observability, rehearse recovery and use blameless reviews to eliminate recurring failure modes. Common pitfalls: inconsistent definition of failure. Record the definition beside the dashboard, review it when systems or processes change, and annotate unusual events so future readers can distinguish a genuine performance shift from a data or timing effect.