Never be on call again
summary
Claims that on-call duty disappears if recovery steps are written so anyone can follow them, with a concrete rule: start with a list rather than a 90‑page manual, whiteboard the flow, and make a one-page procedure that lets a partner restore a server. Tools suggested: a whiteboard and use AI to help convert notes into runnable steps. Practices: gamify writing, assign ownership, enforce project not done until documented; a two‑year‑old can follow the result.
AI-written summary · about
related talks
44mYou build it, you run it
31mHow to Build a Healthy On-call Culture
05mOn-Call in a World Full of Toil
28mBuilding a healthy on-call culture
01h 04mIncident Management - Talk the Talk, Walk the Walk
19mIts Time We Rethink On-Call Culture
06mIgnite: Key Factors for Successful 24×7 On-Call Duty
45mIncident Management - Talk the Talk, Walk the Walk