BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//pretalx//talks.devopsdays.org//dodroxrox26//speaker//DNJETH
BEGIN:VTIMEZONE
TZID:US/Mountain
BEGIN:DAYLIGHT
DTSTART:20250922T000000
TZNAME:MDT
TZOFFSETFROM:-0600
TZOFFSETTO:-0600
END:DAYLIGHT
BEGIN:STANDARD
DTSTART:20251102T020000
RDATE:20261101T020000
TZNAME:MST
TZOFFSETFROM:-0600
TZOFFSETTO:-0700
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:20260308T030000
RDATE:20270314T030000
TZNAME:MDT
TZOFFSETFROM:-0700
TZOFFSETTO:-0600
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
SUMMARY:Why Most SLOs Fail - Amin Astaneh
DTSTART;TZID=US/Mountain:20260922T110000
DTEND;TZID=US/Mountain:20260922T113000
DTSTAMP:20260729T024619Z
UID:pretalx-dodroxrox26-FDTEUK@talks.devopsdays.org
DESCRIPTION:Most teams will tell you they have SLOs. **Most of them are do
 omed to fail.** Not because their metrics are bad or their tooling is wron
 g\, but because reliability has no seat at the table. **SLOs are useless u
 nless they inform your roadmap.** If error budget exhaustion doesn't chang
 e what gets built next sprint\, you don't have an SLO program. You have an
  expensive monitoring system.\n\nThis talk draws on firsthand experience l
 eading SRE initiatives and tech consulting to name the organizational patt
 erns that make SLO programs fail\, regardless of how much effort teams put
  in. You'll leave with a five-question diagnostic you can run at your next
  retro to find out exactly where your organization stands\, and a clear pi
 cture of what it actually takes to give reliability the authority to chang
 e behavior.
LOCATION:Main Stage
URL:https://talks.devopsdays.org/dodroxrox26/talk/FDTEUK/
END:VEVENT
END:VCALENDAR