BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.devopsdays.org//devopsdays-portland-2026//speaker
 //TMECBU
BEGIN:VTIMEZONE
TZID:US/Pacific
BEGIN:DAYLIGHT
DTSTART:20250909T000000
TZNAME:PDT
TZOFFSETFROM:-0700
TZOFFSETTO:-0700
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251102T020000
RDATE:20261101T020000
TZNAME:PST
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260308T030000
RDATE:20270314T030000
TZNAME:PDT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:When the AI Is the Incident: Preparing Your Team for a New Kind of
  Failure - Kat Gaines
DTSTART;TZID=US/Pacific:20260909T095500
DTEND;TZID=US/Pacific:20260909T102500
DTSTAMP:20260824T025851Z
UID:pretalx-devopsdays-portland-2026-3P9HFW@talks.devopsdays.org
DESCRIPTION:Your on-call process was built for software bugs. A service go
 es down\, an alert fires\, someone pages the right engineer\, and you work
  the problem. But AI systems fail differently: they degrade quietly\, hall
 ucinate confidently\, and resist the clean root cause analysis your runboo
 ks were written around. If 2025 was the year of AI adoption\, 2026 is shap
 ing up to be the year everyone finds out their incident response process w
 asn't built for this.\n\nThis talk examines what's genuinely new about AI 
 incidents: the failure modes\, the metrics that matter\, and why your exis
 ting playbooks miss them entirely. We'll dig into what needs to change acr
 oss process\, roles\, and communication\, and what teams handling this wel
 l are already doing differently\, before the next AI failure exposes the g
 ap.
LOCATION:Ballroom
URL:https://talks.devopsdays.org/devopsdays-portland-2026/talk/3P9HFW/
END:VEVENT
END:VCALENDAR