Back to blog

CompanyMay 12, 2026 · 7 min read

Shipping weekly without burning out a 40-person team

Weekly releases are easy at four people and brutal at forty — unless you change what a release is. The operating habits that kept our cadence humane.

Overhead view of a team working at a table covered in charts and laptops

We have shipped every week since 2019. What changed between then and now is not the cadence — it is everything around it. A weekly release at forty people cannot work the way it did at four.

The failure mode is predictable: release day becomes an event, events need heroes, and heroes burn out. Our whole system is designed to make Thursday boring.

The release is not the deadline

Nothing is ever "rushed in" for the release. Work merges when it is ready; the train leaves with whatever is aboard. Missing a week costs nothing because another train leaves in seven days.

This one rule removed 90% of release pressure. The remaining 10% we removed by rotating the release captain role weekly — it is a checklist, not a skill, and treating it as a checklist keeps it that way.

Sustainable pace is not a perk. It is the reason the pace is sustainable.

What we measure instead

We do not track velocity. We track how often a release required someone to work outside normal hours. The answer for the last two quarters: zero. That number is on the wall next to uptime.

Forty people, weekly releases, no heroes. It turns out the boring version is the one that scales.

Related insights

Keep reading