21 March 2026 · Aria Hsu

Runbooks operators will actually open at 02:00

A migration runbook that reads like a strategy memo will be ignored. Write for the person holding the keyboard.

Code editor on a desk during late work hours

Operators under fatigue need step order, credential locations, and rollback triggers — not background narrative. We draft runbooks as numbered sequences with named owners and a single source of truth for status updates.

Tabletop rehearsals expose the soft spots: a step that assumes VPN access someone lacks, or a rollback that depends on a snapshot never taken. Fix those before the window, not during it.

Keep the strategy story in the migration charter. Keep the night-of document ruthlessly operational.

Back to field notes