Interactive graph
Change Window
Table of Contents
Schedule risky changes when rollback help is awake - not Friday night when everyone's offline.
Key Concept
Rollback Principle fails when the people who can revert are asleep or at a wedding.
A change window is boring calendar hygiene: deploy Tuesday morning, freeze before holidays, keep the old build one click away. Not fear of shipping - matching risk to coverage. PKM parallel: Maintenance Window is scheduled garden prune; change window is scheduled production risk.
Examples
- We stopped Friday-night client deploys after the bad release - Tuesday standup owns rollback if it goes loud.
- Wedding weekend freeze: marketing edits queue, no Hugo version bumps until Monday.
Note Relationships
| Relationship | Wikilink | Reason |
|---|---|---|
| alternative | Maintenance Window | PKM prune schedule vs production deploy schedule |
| contradicts | Ship It | when milestone pride ships Friday at 5:01 |
| extends | Preparedness | Window assumes rehearsed undo path and someone on call |
| extends | Risk Management | Time-box exposure to staffed hours |
| extends | Rollback Principle | Risky push only when revert crew is reachable |
| extends | Standard Operating Procedures | Written deploy windows belong in the runbook |
