App Ops Desk · Issue #47
Rollout / rollback decision tree
Most bad releases get worse because the founder delays the rollback decision. A tree removes the emotion.
One action this week: Print or bookmark this tree and run it against the next release where crash-free dips below 99.5%.
Decision tree
Crash-free ≥ 99.5% and no support spike? → Monitor. No action. Crash-free 98–99.5% or support spike? → Phased release pause + investigate today. Crash-free < 98% or purchase path broken? → Emergency hotfix train. Target <24h. Hotfix rejected / cannot fix today? → Roll back to previous build.
Before you need it
- Previous build still available and signed
- Rollback announcement drafted
- Support reply macro ready
Bottom line
Decide in advance. Decisions in the moment always favor hope over data.
Resources hub → Full library and jump-by-symptom links. Join the free list Product updates only. Founding checkout is separate and not live yet.