Incident Management - Talk the Talk, Walk the Walk
summary
Claims a proactive daily routine plus specific hygiene cuts downtime and mean time to resolution: maintain runbooks, tweak alerts, create tasks, automate self-heal, and write fast postmortem notes. Uses on-call handoffs and alert tools like PagerDuty, Opsgenie, VictorOps; follows five pillars identify, notify, investigate, resolve, close. Incident manager role assigns work, mutes noise, forces escalation when stuck, and expects one-line ownership rather than ad hoc heroics.
AI-written summary · about
chapters (17)
- 0:00Introduction to incident management
- 1:23Speaker introduction and background
- 2:30Agenda and key talk objectives
- 3:54Why incident management matters
- 5:21Expecting failure and proactive mindset
- 7:06Structured incident management process
- 10:40Notification and escalation best practices
- 11:46Investigation and diagnosis focus
- 14:33Resolution and recovery steps
- 16:39Incident closure and follow-up
- 19:47Postmortem and learning process
- 20:54Incident manager role and conduct
- 24:03Key traits of an incident manager
- 33:14Proactive measures after incidents
- 37:09Daily proactive incident preparedness
- 42:04Summary and call to action
- 42:50Q&A session
related talks
01h 04mIncident Management - Talk the Talk, Walk the Walk
32mIncident Management - Talk the Talk, Walk the Walk
45mIncident Management - Talk the Talk, Walk the Walk
39mNavigating the Chaos: A Holistic Approach to Incident Management
05mDevOps and incident management: A recipe for success
12mBetter Incident Management to Reduce MTTR
49mThe Role of Incident Management in Business Stability
23mIncident Response, Management & Alerts - where they fit in CloudOps?