Incidents are new normal
summary
Incidents become routine as canary releases, feature flags and observability expose more production feedback; teams run blameless postmortem reviews that build a chronological timeline from logs and chat, invite cross‑functional voices, and extract causal factors then dig deeper with five whys to surface process gaps. Actions split into short corrective work (add monitors, dashboards, rollback playbooks) and longer preventive projects (capacity tests, architecture changes) with a named owner, acceptance criteria and follow‑up metrics so fixes are tracked and validated.
AI-written summary · about
chapters (11)
- 0:00Incidents are the new normal
- 1:37Why post-incident reviews matter
- 4:27Building a reliable culture
- 7:57Role of incident facilitators
- 13:33Focus on process gaps not people
- 16:25Building incident timelines
- 21:44Learning from what went right
- 22:47Finding root causes with five whys
- 26:16Turning incidents into actions
- 31:59Share learnings to prevent future issues
- 32:40Incidents drive continuous improvement
related talks
37mIncidents are a new normal
37mLearning from Incidents at Scale; Actually Doing Cross-Incident Analysis
10mSimplify your postmortems and focus on scaling
20mData Incidents - When things go wrong
15mIncident Ready: Chaos Engineer Your Incident Response
01h 04mIncident Management - Talk the Talk, Walk the Walk
22mAfter the dust has settled: learning from incidents
13mThe Incident Is The Way: Using Your Incidents to Win...