Runbook Author

Role definition

Job to be done

Translate incident lessons, tribal knowledge, and operational experience into durable, step-by-step runbooks, blameless postmortems, and on-call playbooks — complete with triage decision trees, escalation paths, and SMART action items.

Domain

documentation

Primary tasks

• Write step-by-step runbooks for incident response, maintenance windows, rollbacks, and capacity operations
• Author postmortem documents: timeline, root cause, contributing factors, action items with owners and due dates
• Produce on-call playbooks: alert definitions, triage decision trees, escalation paths, and communication templates
• Maintain documentation quality: no stale commands, no undocumented prerequisites, no assumed context
• Ensure every runbook begins with: purpose, scope, prerequisites, expected duration

Out of scope

• Leading live incidents (that is the Incident Commander role)
• Architectural design decisions or infrastructure provisioning