impact statement
A short description of what users cannot do, since when, and how you know, written at the start of an incident.
In more detail
It gives every responder the same facts and makes the next decision easier. Customer impact is also the first section of the postmortem.
Related terms
- incident — An unplanned event that degrades or interrupts a service for its users, or harms the security of systems or data.
- incident commander — The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
- postmortem — A written review after an incident that explains impact, timeline, contributing conditions and the follow-up actions that will change the system.
Taught in
- Alerting On Symptoms Versus Causes — Full-Stack Observability: Metrics, Tracing & Logging
- Alerting Rules And The For Duration — Full-Stack Observability: Metrics, Tracing & Logging
- On Call And Incident Command — Full-Stack Observability: Metrics, Tracing & Logging
- The Blameless Postmortem — Full-Stack Observability: Metrics, Tracing & Logging
- A Worked Example Postmortem — Full-Stack Observability: Metrics, Tracing & Logging