Express error budgets as numbers with time windows — '2 missed sessions per week' not 'try to be consistent'

Why This Is a Rule

"Be consistent with my writing habit" is not an error budget. "Two missed sessions per week maximum" is. The difference is that the second version is falsifiable — at the end of any week, you can determine whether the budget was respected or exhausted. The first version allows infinite rationalization: any performance level can be framed as "mostly consistent."

Time-bounded numeric thresholds convert tolerance from a feeling into a measurement. The number specifies how much deviation is acceptable. The time window specifies the period over which deviations are counted. Together, they create a binary assessment at the end of each period: within budget or over budget. This binary is what makes error budgets operational — you can track, trend, and trigger investigation (When error budget is exhausted, analyze the pattern not individual incidents — budget exhaustion signals structural problems) based on objective data rather than subjective impressions.

Tracking budget consumption as a first-class metric means treating it with the same seriousness as output metrics. "How many of my 2 weekly misses have I used?" should be as visible as "how many sessions did I complete?" The consumption rate provides early warning: if you've used both allowed misses by Wednesday, the remaining days carry zero margin, which changes your priority calculation.

When This Fires

• When defining error budgets for any system (Define your error budget in writing: ideal behavior, minimum acceptable, deviation threshold, and investigation trigger window) — express them in this format
• When existing standards are vague ("be good about...") and need conversion to trackable budgets
• When reviewing budget design for actionability — vague budgets don't trigger investigation
• When tracking budget consumption as part of regular system monitoring

Common Failure Mode

Budgets without time windows: "I allow myself to miss 5 sessions." Over what period? Five misses in a week is catastrophic; five misses in a year is exemplary. Without the time window, the budget is ambiguous and the exhaustion threshold is undefined. Always pair the number with the period.

The Protocol

(1) For each error budget, express as: "[Number] [unit of deviation] per [time period]." Examples: "2 missed writing sessions per week." "3 late deliveries per quarter." "1 skipped review per month." (2) Track consumption actively: at any point in the period, you should know how many of your allowed deviations you've used. (3) When approaching budget limit (e.g., 1 deviation remaining with 3 days left in the period), increase attention — your margin is gone. (4) At period end: was the budget respected? If yes → the system is performing within tolerance. If no → investigate the pattern (When error budget is exhausted, analyze the pattern not individual incidents — budget exhaustion signals structural problems). (5) Review the budget itself quarterly: is it appropriately calibrated? Too generous (you never approach the limit) → tighten. Too strict (you exhaust it constantly) → either the system needs structural improvement or the budget needs loosening.