App Ops Desk · Issue #45
Release train timing for solo founders
Heroic release sprints feel productive. They also produce the most avoidable mistakes.
One action this week: Pick one release day and one cutoff day. Write them on the team calendar (even if the team is you).
Default cadence
- Release day: Tuesday or Wednesday (not Friday, not Monday)
- Code freeze: 24h before archive
- Archive window: known start/end time
- Review wait: separate from “user ship” (use phased release)
Failure modes
- Friday night “just one more fix” ships
- No written cutoff → scope creep until 4am
- Phased release skipped because you are impatient
Bottom line
Predictable beats fast. Fast becomes predictable only after the process is boring.
Resources hub → Full library and jump-by-symptom links. Join the free list Product updates only. Founding checkout is separate and not live yet.