R.I.V.E.R. Maturity Ladder / Working Draft
Maturity Ladder / Working Draft / April 2026

A framework and a practice.

Teams don't adopt these metrics overnight; they ascend through them.

DORA's single most powerful rhetorical device was its maturity tiering. Elite / high / medium / low gave teams a self-locating language and an aspirational ladder. R.I.V.E.R. needs the same — five levels, each defined by what the team has achieved, not by what it lacks. The ladder is also a calibration target for the qualitative research: interviews will teach us what these levels actually look like in the wild, and where the transitions are hardest.

The ascent — five levels of practice ↑ Higher impact per release
1
Deploy
2
Control
3
Declare
4
Prove
5
Learn
Compounds
Delivery
Hygiene
Deploy ≠
Release
Intent
Declared
Outcomes
Proven
Learning
Loop
1
Deploy Delivery hygiene

The team ships reliably on a DORA foundation. Delivery hygiene is in place — deployment frequency, lead time for changes, change failure rate, and time to restore are tracked and trending in the right direction. This is the foundation of a good release practice.

2
Control Deploy ≠ release

Deploy and release are separate events. The team rolls out progressively, targets specific cohorts, and can reverse a release in seconds without a redeploy. Release-layer metrics exist but aren't consistent across teams or releases.

3
Declare Intent, ahead of ship

Before a release ships, the team states what it expects to happen — hypothesis, success signal, target cohort, time horizon. Some releases get measured against what was declared. The discipline is emerging, not yet uniform.

4
Prove Systematic attribution

Outcome attribution is systematic. Most releases carry a declared success signal and are evaluated against it after the fact. Not every hypothesis will hold — and that's the point. The team builds a durable record of which intents realized and which didn't, and can report Outcome Realization Rate in skip-levels and planning reviews with the evidence to back it.

5
Learn The compounding loop

Evidence from realized and unrealized intents feeds the next cycle. The team's predictions sharpen over time, not just its measurements. This is the compounding loop — the "Evolution" in R.I.V.E.R.

Still a work in progress

The level names and descriptions are draft v2 — revised from an earlier set that leaned on framework-internal vocabulary. The verbs (Deploy, Control, Declare, Prove, Learn) are meant to be self-locating even for readers who haven't seen the rest of R.I.V.E.R. The level descriptions will be calibrated against real practice through the Phase 1 qualitative interviews.

VALUE CHAIN framework-wide
Idea
Commit
Deploy
Release
Adoption
Impact