---
title: Incident Response
description: Interviews, articles, podcasts, and talks featuring Jesse Robbins, tagged Incident Response.
doc_version: "1.0"
last_updated: 2026-05-31
---

# Incident Response

Interviews, articles, podcasts, and talks featuring Jesse Robbins, tagged Incident Response.

## [Generative AI in DevOps and Incident Response: What the Experts Actually Think](https://jesserobbins.com/mentions/2023-10-12-generative-ai-devops-incident-response-heavybit.md)

*2023-10-12*

I interviewed Nora Jones, Jeremy Edberg, Mandi Walls, and Brent Chapman on what generative AI actually does in incident response, and where humans have to stay in the loop.

## [What to Know About the Modern Incident Response Lifecycle](https://jesserobbins.com/mentions/incident-response-best-practices-heavybit.md)

*2022-11-11*

Heavybit's incident management guide quotes me on why teams only get good at incident response when they treat the whole lifecycle as one discipline.

## [Fireside Chat with Jesse Robbins and Kolton Andrus • Failover Conf 2021](https://jesserobbins.com/mentions/fireside-chat-jesse-robbins-kolton-andrus-failover-conf.md)

*2021-04-29*

At Gremlin's Failover Conf 2021, Kolton Andrus and I covered GameDay origins at Amazon, the evolution of chaos engineering, and where reliability practices were headed.

## [Incident Management for Operations (foreword by Jesse Robbins)](https://jesserobbins.com/mentions/incident-management-for-operations-schnepp-vidal-hawley-oreilly.md)

*2017-07-01*

I wrote the foreword to Schnepp, Vidal, and Hawley's O'Reilly book bringing fire-service incident command into IT operations. The lineage runs from my work at Amazon as Master of Disaster through the first Web Ops/Fire Ops summit I convened in 2012.

## [Resilience Engineering: Learning to Embrace Failure](https://jesserobbins.com/mentions/resilience-engineering-learning-embrace-failure-acm-queue.md)

*2012-09-12*

Jesse Robbins (Amazon), Kripa Krishnan (Google), and John Allspaw (Etsy) discuss how they built organizations that deliberately trigger failure to get stronger: powering off data centers, running 96-hour disaster simulations, and transforming blame cultures into learning cultures.

## [GameDay: Creating Resiliency Through Destruction](https://jesserobbins.com/mentions/gameday-creating-resiliency-through-destruction-usenix.md)

*2011-12-20*

My USENIX LISA'11 talk on GameDay: deliberately inject failures into production to build organizational resilience before real outages happen. I had been running these exercises at Amazon since 2003.

## [Understanding Operations Culture (Part 1)](https://jesserobbins.com/mentions/understanding-web-operations-culture-part-1-oreilly-radar.md)

*2008-06-14*

I wrote this in 2008 to define web operations culture using what I had learned from the fire service: the habits that separate teams who handle incidents well from teams who don't.

## Sitemap

See [sitemap.md](https://jesserobbins.com/sitemap.md) for the full list of pages on this site.
