Interactive graph

Change Window

Created Jul 24, 2026, 10:27 AM · Updated Jul 24, 2026, 10:27 AM

Table of Contents

Risky changes ship when someone awake can roll back, not Friday night when everyone is offline.

Key Concept

Rollback Principle fails when the people who can revert are asleep or at a wedding.
Level 1: Like when you fix the roof on a sunny Tuesday - not Friday night when nobody can help if it leaks worse.
Level 2: Rollback fails when the people who can revert are asleep or at a wedding - match risky updates to when someone awake can undo them.
Level 3: A change window is boring calendar hygiene - deploy Tuesday morning, freeze before holidays, keep the old build one click away.
Level 4: Stop Friday-night client deploys - Tuesday standup owns rollback if the release goes loud.
Level 5: Not fear of shipping - PKM parallel: Maintenance Window is scheduled garden prune; change window is scheduled production risk when Rollback Principle needs awake hands.
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.
I ship risky changes when someone awake can roll back, not Friday night when everyone's offline.

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.

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