The Un-Incident: Extracting Value from the Gray Area of...
summary
Claims that 30–60% untracked potential incidents hide learnings and defines four concrete gray‑area patterns: no‑CI (non‑critical), near miss, not‑our‑fault, and premature escalations. Recommends actions: tighten observability tied to SLO burndown, use automated signals (example: Argo CD deploy linked to 51% error and 1,500 users impacted with a rollback recommended), add Jira/Slack triggers, run incident‑process reviews, create an alternative “request for assistance” flow, and involve product managers to fix UX and guardrails.
AI-written summary · about
chapters (9)
- 0:00Un-incident concept
- 1:22Speaker background
- 2:48Un-incident taxonomy: four patterns
- 8:26Handling un-incidents: mindset & culture
- 11:24Fact-based decisions & observability
- 13:13Structured processes for ambiguity
- 16:48Improving incident processes
- 20:42Not our fault incidents & feedback
- 23:09Recap & Q&A
related talks
37mIncidents are a new normal
13mThe Incident Is The Way: Using Your Incidents to Win...
41mAre We Getting Better Yet? Progress Toward Safer Operations
01h 04mIncident Management - Talk the Talk, Walk the Walk
34mIncidents are new normal
37mLearning from Incidents at Scale; Actually Doing Cross-Incident Analysis
29mShrinking the Impact of Production Incidents
30mHow Did Things Go Right? Learning More from Incidents