~/talk

Everything I know about incident response

Talkat devopsdays Portland 2019 · 2019-09-10..09-12· [devops-and-delivery]
slides:none on file

Claim: incidents are inevitable so focus on response, not prevention. Use EMS practices: breath, do a scene size‑up, gather O‑PQRST (Onset, Provocation, Quality, Radiation, Severity, Time) to orient responders, and map needed roles and hidden dashboards. Trust pattern‑matching — treat the patient not the monitor — but avoid litigating severity during the call. Use closed-loop communication and narrate actions before intervening. Practice responses, onboard on‑call people, know who has access and longer latencies, and build sustainable post‑incident recovery so responders don’t burn out.

AI-written summary · about

  1. 0:00Start
  2. 0:09Everything I Know About Incident Response I Learned on an Ambulance
  3. 0:44Hours of boredom punctuated by moments of sheer terror
  4. 2:14The goal is not to "make sure this never happens again"
  5. 5:40Practice Your Response
  6. 16:58Treat your patient, not the monitor
  7. 19:32Don't talk to patients about severity
  8. 22:51Communication matters
  9. 25:48Don't become part of the emergency
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.