#54GOVERNANCEGOVERNElite
Severity Definition
Pre-defined incident levels
Easy
Overview
Clear definitions of incident severity with expected response times and escalation procedures.
Why It Matters
No debate during incidents. SEV1/2/3/4 defined in advance.
The Risk
Without clear severity definitions, incident response is chaotic. Minor issues trigger full escalations. Major incidents get slow response. Teams burn out from alert fatigue.
Implementation Components
A complete implementation of this capability includes:
- Clear severity level definitions (SEV1-4 or P1-4)
- Impact criteria for each level
- Expected response times per severity
- Escalation procedures per severity
- Examples of past incidents at each level
- Decision tree for severity assignment
Implementation Pattern
- 1Define severity levels
- 2Specify impact criteria
- 3Define response times
- 4Document escalation
Pipeline Coverage
This continuous capability monitors and applies to the following pipeline phases:
RELEASE
Tool Examples
These are examples, not endorsements. Choose what fits your context.
Dependencies
Enables (unlocks)
Same Layer
Other capabilities in this continuous layer
- •#55 Incident Timeline
- •#56 Status Communication
- •#57 Post-Incident Review
- •#58 Change Ledger
- •#59 Recovery Runbooks
+6 more