Skip to content

Instantly share code, notes, and snippets.

@jacobian
Created May 5, 2016 18:30
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save jacobian/d9bfb1412e953eb7bd380600b46f09d9 to your computer and use it in GitHub Desktop.
Save jacobian/d9bfb1412e953eb7bd380600b46f09d9 to your computer and use it in GitHub Desktop.
  1. Initiate
    • Where should a (potential) incident be reported?
    • How will incidents be tracked?
    • What are the roles and responsibilities during an incident?
  2. Communicate
    • Where will comms happen? Who will be involved?
    • Who will send situation updates? To whom? How often?
  3. Assess
    • Where do we collect information? Who follows up?
    • How do we determine severity?
  4. Remediate
    • Given that severity, what is our response SLA?
    • How do we prioritize remediation (short vs long-term)?
    • How do we communicate and track remediation?
    • When and how do we notify customers?
  5. Retrospective
    • How do we explore causes? Five Whys? Infinite Hows?
    • How will we piece together a timeline for the retro?
    • What metrics do we need to collect?
    • How will we track long-term follow-up?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment