Incident response teams are evolving, thanks to DevOps, agile, and today’s demand for always-on services. But, what’s the best way to respond when you’re faced with a complex mix of systems, software, and teams? Is there a way to respond faster, collaborate better, and continuously improve your incident management process?
Join Simon Kubica, Product Manager for Opsgenie, as he uncovers best practices that’ll streamline every stage of your response effort. See how Atlassian, Amazon and Google enable collaboration between support, operations and development, and learn how to leverage automation and conduct effective postmortems. Plus, Simon will show live demos on how you can implement these tips in Opsgenie, Statuspage, and Jira Service Desk.
3. it’s not working!! ARGHH
I can’t get my work done
what’s going on?
Is this down for anyone else?
What’s the ETA?
CUSTOMERS DEMAND ALWAYS-ON SERVICES
7. Communicate early and often
4
3
2
1
RESPOND
DETECT
RESOLVE
LEARN
FOUR KEYS TO TRANSFORMING YOUR INCIDENT RESPONSE
Break down team silos
Set, share, run and review your game plan
Blameless and collaborative postmortems
8. Mean time to recovery (MTTR)
FOUR PHASES OF INCIDENT RESPONSE
DETECT RESPOND RESOLVE LEARN
22. COMMUNICATE EARLY & OFTEN
• Have a templated first comms ready
• Don’t rely on your usual infrastructure
• Centralize and embed your status
• Consider your internal stakeholder updates
• See it as an opportunity to build trust
RESOLVEDETECT RESPOND LEARN
23.
24.
25. SET, SHARE, RUN &
REVIEW YOUR
GAME PLAN
3
RESOLVEDETECT RESPOND LEARN
26. • Assessment and severity criteria
• Escalation rules
• Roles and individual authority
• Communication cadence
SET IT UP:
RESOLVEDETECT RESPOND LEARN
SET, SHARE, RUN & REVIEW YOUR GAME PLAN
27.
28. • Have responders read it
• Ask for feedback
• Put it in Confluence
• Make it easily accessible
SET, SHARE, RUN AND REVIEW YOUR GAME PLAN
SHARE IT:
RESOLVEDETECT RESPOND LEARN
29. • Test your new process with a simulation
• Get as close to the real thing as possible
• Set a cadence - quarterly works well
• Involve less experienced teammates
SET, SHARE, RUN AND REVIEW YOUR GAME PLAN
RUN IT:
RESOLVEDETECT RESPOND LEARN
30. • Set monthly / quarterly reminders and assign
an owner
• Have we learned anything that can make this
process better?
• Are we following this process in practice?
SET, SHARE, RUN AND REVIEW YOUR GAME PLAN
REVIEW IT:
RESOLVEDETECT RESPOND LEARN
43. Communicate early and often
4
3
2
1
RESPOND
DETECT
RESOLVE
LEARN
FOUR KEYS TO TRANSFORMING YOUR INCIDENT RESPONSE
Break down team silos
Set, share, run and review your game plan
Blameless and collaborative postmortems