Principle

Let reliability data slow feature velocity when the budget is spent

Reliability work needs permission to outrank new features before the next outage makes the choice for you.

See the ideaAn illustrative example

Let reliability change the next work choice.

Read the idea

The example's allowed error budget is spent, yet new feature work keeps all the attention while a reliability fix waits.

The objective must reflect real user value and risk. The illustration contains no measured service-level data or universal threshold.

Keep this pictureLet reliability change the next work choice. The reliability fix receives capacity and new changes are deferred under the agreed policy. Resuming feature work depends on the actual service returning to its agreed range.Save the memory card
VedokrokSee the idea. Try it.

Before you use it

Use when
  • A team keeps shipping changes while user-facing reliability is already below the agreed target.

Keep this limit in mind

  • An arbitrary SLO creates arbitrary behavior; error budgets only help when the objective reflects real user value and risk.

Why it matters

Define a user-facing service objective and an allowed error budget for a period. When reliability is healthy, change can proceed normally. When the budget is exhausted or SLO misses persist, shift capacity from new changes toward reliability until the service returns to the agreed range. Treat the policy as prioritization, not punishment.

An example

Pause nonessential agent-feature rollouts when repeated tool failures consume the monthly success-rate budget and focus on reliability fixes.

Check your result

Reliability deterioration changes work priority through an agreed rule rather than ad hoc escalation.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading
Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingLet reliability data slow feature velocity when the budget is spent

Evidence and sources
Supports

Google's example error-budget policy uses SLO performance to decide when teams should continue releases versus focus effort on reliability.

Error-budget policy is an organizational control model and requires an SLO that reflects user value.

Example Error Budget Policy · Goals and SLO miss policy

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details