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

An empty error budget is the moment of truth for the SLO programme. Without a defined consequence, the SLO is observation, not guidance.

• Observation vs guidance. SLO without consequence is a number on a dashboard; engineering keeps shipping.
• Self-resetting budget. Without a freeze, the budget refills next month; the SLO never bites.
• Load-bearing planning. Real consequences make the SLO drive sprint planning, not just retrospectives.
• Trust signal. The team learns whether the SLO matters from how leadership responds when it empties.

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, and signed at the right level; inventing them mid-incident produces the wrong response.

• Pre-negotiate. Define consequences at programme launch, not when the first budget empties.
• Document. Written agreement; signed by VPs of engineering and product; lives next to the SLO definition.
• Defendable. Easier to enforce a documented agreement than to argue in the heat of a budget exhaustion.
• Annual review. Consequences updated yearly as the programme matures; the rules grow with the team.

When to invoke each

Consequences scale with severity. Match the response to the harm; over-reacting trains teams to dispute the SLO, under-reacting undermines it.

• Slight breach. Nudge: sprint conversation, capacity adjustment, no formal freeze.
• Severe breach. Feature freeze on the affected service until the budget recovers.
• Repeated breach. SLO renegotiation; the target may be wrong, or investment may be insufficient.
• Catastrophic. Product-wide freeze plus root-cause sprint; reserved for incidents that crater customer trust.

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.