Don't Be A Bystander, Be An Incident Commander – Rachael Byrne

Don't Be A Bystander, Be An Incident Commander – Rachael Byrne

Many organizations have some kind of incident response process to coordinate during a major service outage. Some operationally mature companies incorporate a formal Incident Commander role in their process for a faster, more effective response. The Incident Commander serves as the final decision-maker during a major incident, delegating tasks and listening to input from subject matter experts in order to bring the incident to resolution. Whether or not a company has a formal process that includes an Incident Commander, most companies believe that your most senior engineer is best suited to lead an incident response. I challenge this assumption.

I have learned first hand that you do not need to be highly technical, let alone senior, to effectively lead a coordinated response to a major incident. Comfort with a structured process and soft skills such as communication are actually more important than technical knowledge for an effective Incident Commander.

All organizations need to maximize the number of people able to lead a major incident response to avoid burn-out of their most senior technical leaders and increase overall availability of their service. Audience members will learn from this talk how to develop an inclusive incident response process that welcomes more Incident Commanders without compromising response effectiveness that they can immediately apply at their own organizations.

027edc76bf9f9c030820807f87c5dbdc?s=128

DevOpsDays Zurich

May 03, 2018
Tweet

Transcript

  1. Don’t be a bystander, be an Incident Commander Rachael Byrne

  2. Something is broken! @b3rachael

  3. @b3rachael

  4. Major Incident Incident Response Incident Commander @b3rachael

  5. Who can lead? @b3rachael

  6. None
  7. 1. Skills 2. Training @b3rachael

  8. (spoiler, none are technical) @b3rachael

  9. @b3rachael

  10. 1. Process @b3rachael

  11. 2. Communication @b3rachael

  12. 3. Time management @b3rachael

  13. 4. Listening @b3rachael

  14. Incident Commander Skills 1. Process 2. Communication 3. Time management

    4. Listening @b3rachael
  15. Inclusive Incident Response Training @b3rachael

  16. Coordinate and delegate @b3rachael

  17. Office Hours @b3rachael

  18. Shadow @b3rachael

  19. Scribe @b3rachael

  20. Failure Friday @b3rachael

  21. Reverse Shadow @b3rachael

  22. Celebrate @b3rachael

  23. Inclusive IC Training 1. Define the role 2. Office hours

    3. Shadow 4. Scribe 5. Failure Friday 6. Reverse shadow @b3rachael
  24. #DevOps @b3rachael

  25. Thank you @b3rachael response.pagerduty.com