Skip to content
How to ThinkIn the Age of AI

When error budget is exhausted, analyze the pattern…

When error budget exhaustion occurs in a tracked system, conduct root cause analysis of the pattern rather than investigating individual deviations, because budget exhaustion signals structural problems while individual errors within budget represent normal variance.

When This Fires

Common Failure Mode

Investigating each deviation individually: "Monday I missed because of a meeting. Wednesday because I overslept. Friday because I was tired." Three individual explanations that miss the structural pattern: your schedule has changed in a way that systematically conflicts with your system. Individual explanations feel complete but produce individual fixes (reschedule Monday's meeting, set an extra alarm, go to bed earlier) that don't address the structural cause.

The Protocol

(1) When error budget is exhausted (deviation threshold exceeded within the time window — Define your error budget in writing), stop investigating individual incidents. (2) Instead, analyze the pattern: list all deviations in the budget period. What do they have in common? When did they cluster? What contextual factors recur? (3) Identify the structural cause: what changed in the system, environment, or context that shifted the error rate above budget? (4) Design a structural fix (Recurring errors with the same root cause need structural…) that addresses the pattern-level cause, not the individual symptoms. (5) After implementing the fix, reset the error budget and monitor. If the error rate returns to within budget → the structural fix worked. If budget is exhausted again → the root cause analysis was incomplete. Dig deeper.