Era 01
Whenever
2021
14 days median gap
Practice
Release work that teams can plan around.
Shared cadence, clear playbooks, and multi-team coordination - built from years of running the process, not from a slide deck about it.
- Cadence
- Turn ad hoc ships into a predictable rhythm
- Playbooks
- Standardize how releases get planned and cut
- Teams
- Coordinate across products without perpetual sync meetings
- Proof
- Track the metrics that show the system is working
Brief
Five years, 1,358 releases.
Every release below was coordinated across product teams and pulled from a release-tracking system, then laid out chronologically. The throughline: releases stopped being an event and became a rhythm - from whenever one was ready, to monthly, to weekly, to daily and on-demand.
Oxford Comma offers this as a service: assess where your cadence is stuck, standardize the playbooks, and scale the process so more teams can ship without chaos.
The shift
Four eras of cadence.
Median gap between releases, compressed over five years.
Era 02
Monthly to weekly
2022
4-7 days median gap
Era 03
Weekly to daily
2023
1-2 days median gap
Era 04
Daily / on-demand
2024-2026
1 day median gap · often same-day
At a glance
The numbers.
1,358
releases coordinated, May 2021 - Aug 2026
14× faster
median gap between releases: 14 days to 1 day
2 to 8
product teams brought under a shared release process
+36%
2026 releases to date (279) vs. same period 2025 (205)
3,717
tickets / work items shipped through those releases
<6%
of releases landed on a Friday - deploy safety held as pace rose
Growth
Release volume, year over year.
From 23 releases in the first partial year to a run-rate of roughly 420+ for 2026. The 2024-2025 plateau was not stalling - volume held while the release process itself was standardized.
Releases per year
2026 = year-to-date, through Aug 14
Monthly volume, full history.
Every month since the first tracked release. The October 2024 spike (59 releases) was a coordinated multi-team push; the general trend since has held in the 30-48 per month range - roughly 1.5 releases a business day.
Releases per month
May 2021 - Aug 2026
Cadence
Compression: days between releases.
The clearest evidence of the shift is not volume - it is the gap between releases. Mean days between any release, by half-year:
Mean days between releases
by half-year
"Whenever" became "on-demand" - and the org did not just ship faster, it shipped on a rhythm predictable enough that eight teams could plan around it.
Process maturity
Playbooks and release days.
Release template standardization
by year
Ad hoc
Playbook A
Playbook B
Release day of week
2025 - present
Coordination complexity.
Share of releases requiring simultaneous coordination across two or more teams - the hardest releases to manage. This rose as more teams joined the shared cadence, then eased as release trains matured enough for teams to ship independently.
Multi-team releases
% of all releases, by year
Source: release tracker export · 1,358 releases · May 2021-Aug 2026 · compiled from personal release management records
Next
Want this kind of rhythm?
If releases still feel like events - or like chaos - we can help assess the cadence, standardize playbooks, and coordinate across teams.