Document an operational process so anyone on-call can follow it under pressure.
Why it works: The 2am framing forces explicit commands and numbered steps; asking for destructive-step flags is cheap insurance.
This is a message template. Fill in the blanks below, then paste it into the chat.
Write a runbook for the following operational process.
Process name: [name of the process or incident type]
What triggers this: [what condition or alert causes someone to run this runbook]
System context: [what services, infrastructure, or components are involved]
Steps I take to handle it:
[describe what you do, even roughly; the runbook will make it precise]
What success looks like: [how you know it’s resolved]
Common failure modes: [things that go wrong during this process, if any]
Write it so someone who has never done this before can follow it at 2am. Use numbered steps. Call out any commands explicitly. Flag any steps that are destructive or irreversible.