Bad runbooks waste time. Good runbooks guide you to resolution quickly.
Runbook structure:
Title: Clear problem description
Symptoms: How do you know this runbook applies?
Prerequisites: What access or tools do you need?
Steps: Numbered, specific actions
Verification: How do you confirm the fix worked?
Escalation: Who to contact if steps don't resolve it
Writing tips: Include exact commands, show expected output, add decision trees, and screenshot GUI steps. Test by having someone unfamiliar follow it.