Ship Every Friday: Anatomy of a Weekly Release Heartbeat
startupplaybooks
Inside the weekly ship cadence that Origami used from week one — why Friday, what counts as shipping, and how to keep the heartbeat when the team scales.
Shipping every Friday sounds like a productivity slogan. In Origami's playbook it's an operating primitive — a heartbeat, not a goal. Here's the anatomy.
Why Friday specifically
A Friday ship forces the week to converge. Monday–Thursday is scoped backward from what can actually be in production by end of day Friday. Weekend bugs cost less than mid-week ones because your team is fresh on Monday to triage.
What counts as 'shipping'
Code in production, in front of real users. Not a merged PR. Not a staging deploy. Not a feature flag turned on for internal accounts. If a paying user can't touch it Friday, it didn't ship.
The heartbeat vs the milestone
A milestone is 'v2 is out.' A heartbeat is 'something is out every seven days, forever.' Milestones slip and take morale with them. Heartbeats don't slip — the scope does.
What to cut when the week is tight
- Nice-to-have polish.
- Refactors with no user-facing effect.
- Anything blocked on another team.
How the heartbeat survives scale
One release train, one release manager on rotation, one changelog. Teams pile work onto the train, not around it. The moment you have two release trains, you have zero heartbeats.
The compounding effect
Fifty Friday ships a year is fifty forcing functions to finish things. That's the real edge — not velocity, but a repeated public deadline that keeps work small.
See how we apply similar cadence discipline inside the Silverberry AI Platform.