# Why you should ditch your overly detailed incident response plan

DevFeed: [Why you should ditch your overly detailed incident response plan](<https://devfeed.tech/articles/why-you-should-ditch-your-overly-detailed-incident-response-plan-11758.md>)

Original publisher: [Read original article](<https://incident.io/blog/ditch-detailed-plans>)

Author: Danny Martinez

Published: 2022-10-06T00:00:00Z

Content type: article

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [incident management](<https://devfeed.tech/topics/incident-management.md>)

Tags: [best-practices](<https://devfeed.tech/tags/best-practices.md>), [guide](<https://devfeed.tech/tags/guide.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [management](<https://devfeed.tech/tags/management.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>)

## AI overview

The article argues that overly detailed incident response plans and lengthy comprehensive documents are less useful during real incidents because incidents are unique, unfamiliar, and require improvisation under pressure. It recommends documenting a concise, repeatable process that captures the common steps shared across incidents.

## Source excerpt

Best practices for how you should respond to incidents.