The Ratio

Our weekly newsletter on reliability economics.

I run a benchmark that nobody asked for. 121 enterprise teams have taken it anyway. Every Tuesday I send you the one number that surprised me and the seven links that explain why it matters to me.

The newsletter is how I think out loud about what the data says.

No sponsors. No AI slop. Hit reply any time — I read everything.
Prefer RSS? reliabilityeconomics.com/blog/feed/the-ratio.xml

Issue №26November 11, 2026

The Ratio

A weekly newsletter on reliability economics


The Number

2 of 107

Only 2 of 107 organizations have SLOs that are central to release and investment decisions — the rest either have no SLOs or treat them as reporting artifacts.

107 organizations reported SLO maturity. 29 have none. 59 have SLOs that don't influence decisions. 14 influence some decisions. Only 2 have SLOs central to release and investment choices.

The Ratio

A decade of conference talks, blog posts, and SLO evangelism. The benchmark says almost none of it landed. 2 out of 107. That's the conversion rate on an entire industry movement.

SLOs without decisions attached to them are compliance artifacts. Paperwork. Like a building inspector who files reports but never stops construction, the assessment exists, the consequence doesn't. 88 organizations either skipped SLOs entirely or built ones that change nothing about how software ships or where money goes.

The first group, the 29 with no SLOs, at least isn't pretending. The second group, the 59 with SLOs that influence nothing, has the overhead without the outcome. That's worse.

88 of 107 organizations have SLOs that either don't exist or don't influence a single decision.



The Crowd Favorite

  1. One (Remastered) — Metallica ↗ — A runbook without a rollback path leaves on-call with no exit. That's a design failure, not an operational one.
  2. Even Flow — Pearl Jam ↗ — The unrepeatable studio fix is your hero-action: decisive, undocumented, invisible to the next engineer paged at 3 a.m.
  3. Synchronicity II — The Police ↗ — "Unrelated" services fail simultaneously at peak load because they share a hidden dependency, not because the incidents coincidentally overlap.
  4. Radio Ga Ga — Queen ↗ — When every threshold fires, the revenue-impacting signal drowns in noise. Alert fatigue is a pipeline architecture problem, not an ops discipline problem.
  5. Times Like These — Foo Fighters ↗ — A DR plan that lives in one engineer's head doesn't survive attrition. Test the rebuild, not just the backup.
Prevention

No rollback, no runbook, no handoff.


The Challenger — Industry Shift

Platform engineering absorbed SRE's toil-reduction mandate. The 2024 DORA report shows high-performing organizations centralizing reliability tooling in internal developer platforms, not in SRE teams.

The analogy is hospital sterile processing: nurses once managed their own instrument supply, consuming clinical hours. Centralized departments restored that capacity for patient care. The reliability parallel is direct. When platform teams own the paved road, SRE capacity shifts from infrastructure babysitting to availability architecture.

Reliability is centralizing. Teams that miss this will fund the wrong headcount for the next three years.

The Ratio

Reliability is centralizing. Fund the right team.


The Ratio is a weekly newsletter by Florian Hoeppner.

Take the assessment → reliabilityeconomics.com/benchmark
Reply to this email with your take.

The Ratio

Our weekly newsletter on reliability economics.

I run a benchmark that nobody asked for. 121 enterprise teams have taken it anyway. Every Tuesday I send you the one number that surprised me and the seven links that explain why it matters to me.

No sponsors. No AI slop. Hit reply any time — I read everything.
Prefer RSS? reliabilityeconomics.com/blog/feed/the-ratio.xml