Interactive graph
Staged Rollout
Table of Contents
Ship the change to a small slice first - rollback stays cheap if the new state bleeds.
Key Concept
Full-blast deploy turns every user into a test subject.
Staged rollout - preview branch, one table section, scrimmage Tuesday - keeps Reversibility real. Safety by Design at release time: harm hits fewer people before you commit the whole lane.
Examples
- Cloudflare preview branch caught the broken layout before main - rollback was not touching production.
- New inbound play ran in scrimmage Tuesday before Friday's game - point guard reverted to last week's call at halftime without reinventing.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Preparedness | Rehearse on a slice vs rehearse the undo drill on paper |
| contradicts | Ship It | when blasting to everyone beats waiting for the small-slice signal |
| extends | Reversibility | Small blast radius makes undo cheap |
| extends | Risk Management | Limit exposure before you bet the whole lane |
| extends | Rollback Principle | Staged slice is where you practice undo before everyone's affected |
| extends | Safety by Design | Fewer people hit before the hazard is proven safe |
| implements | Free Tier Hosting Stack | PR preview deploy before Pages merges to main |
