SLO Consequences: What Happens When the Budget Empties

Empty budget is a moment of truth for the SLO program. The defined consequence decides whether the SLO has weight.

Why consequences matter

Without consequences, the SLO is observation, not guidance. Engineering keeps shipping; the budget refills next month.

Real consequences make the SLO load-bearing in planning.

Five common consequences

• 1. Feature freeze on the affected service.
• 2. Reliability sprint dedicated.
• 3. Revert recent risky changes.
• 4. Increase test coverage.
• 5. Adjust SLO target if it was wrong.

Negotiating real consequences

Consequences land politically. Pre-negotiated; documented; signed by VPs.

Easier to defend a documented agreement than to invent one mid-incident.

When to invoke each

Slight breach: nudge (sprint conversation).

Severe breach: feature freeze.

Repeated breach: SLO renegotiation.

The escalation matches the harm.

Antipatterns

• No consequence. SLO is decoration.
• Same consequence for every breach. Disproportionate.
• Consequence enforced ad-hoc. Trust erodes.

What to do this week

Three moves. (1) Apply the pattern to your most-impactful service. (2) Measure adherence for 30 days. (3) Rewrite the policy or the SLO if the gap is durable.