<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Incident Response on David Cajio | AWS, DevOps &amp; Platform Reliability</title><link>https://davidcajio.com/tags/incident-response/</link><description>Recent content in Incident Response on David Cajio | AWS, DevOps &amp; Platform Reliability</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>© 2026 David Cajio</copyright><lastBuildDate>Thu, 23 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://davidcajio.com/tags/incident-response/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Write a Production Runbook Engineers Will Actually Use</title><link>https://davidcajio.com/posts/production-operations/how-to-write-production-runbook/</link><pubDate>Thu, 23 Jul 2026 00:00:00 +0000</pubDate><guid>https://davidcajio.com/posts/production-operations/how-to-write-production-runbook/</guid><description>A production runbook should help an engineer understand a service, identify the failure, restore it safely, and know when to escalate. This guide shows how to write one that people will actually use.</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://davidcajio.com/posts/production-operations/how-to-write-production-runbook/feature.jpg"/></item></channel></rss>