Turn yesterday's incident thread into a runbook draft

Incidents teach. Then the thread ages out and the next incident starts from zero. Write the runbook while it's fresh.

This hack: twenty-five minutes, yesterday's incident to runbook draft.

When to use it

• An incident just resolved.
• The thread or timeline exists.
• Someone else might hit this again.

When not to

• Blameless review hasn't happened and facts are contested. Wait for agreed timeline.
• Security/legal holds apply. Follow that lane.
• You're writing to assign blame. Stop.

Do this (timer on)

1. 1. Paste timeline + fixes.
2. 2. Draft runbook: detect, diagnose, mitigate, communicate, follow-ups.
3. 3. Mark unverified steps. Assign an owner to test the runbook.

Prompt (copy)

Turn this incident thread into a runbook draft.

Sections:
- Symptoms / how we detect
- Immediate mitigation
- Diagnosis steps
- Communication template (short)
- Follow-ups / owners
- What we still don't know

Do not invent root cause if not confirmed.

INCIDENT MATERIAL:
[paste]

After you send

If incidents never become runbooks, knowledge handoff fails under pressure. Operations Efficiency when tribal memory is the only DR plan.

Start free assessment (Operations Efficiency) at https://faisalrizvi.com/ - See where we're wasting hours. 3 minutes. Score + prioritized roadmap. Shareable report. No login.

Book a free 30-min call only if you want a walkthrough after the roadmap.