itsual Checklist and Runbook
Overview
Checklists and runbooks reduce errors and cognitive load. They should be written for the person doing the work, especially under time pressure or stress.
When to Use
- Operational procedures
- Incident response and on-call guides
- Release / deployment steps
- Onboarding and recurring operational tasks
- Safety or compliance-critical processes
Design Principles
- Write for the doer, not the auditor
- Use clear, actionable steps (verb-first)
- Include preconditions, expected results, and failure signals
- Keep the happy path prominent; branch for exceptions
- Make ownership and escalation paths obvious
- Version and date the document
Checklist vs Runbook
- Checklist — Short, ordered verification or action items
- Runbook — More detailed procedure with context, decision points, and recovery steps
Verification
- Someone unfamiliar with the process can follow it
- Critical steps cannot be easily skipped or misread
- Failure and escalation paths are defined