Incident Command, Escalation, and Resolution
Ops Bot | Operations | Max 30 Points
| Level | Criteria |
|---|---|
| 1 | Chaotic response; no IC role; hero culture; no learning |
| 2 | Basic severity levels; some escalation paths; informal IC |
| 3 | Defined IC role; runbooks used; postmortems written |
| 4 | Trained ICs; MTTD/MTTR tracked; blameless culture |
| 5 | Incident learning system; automated mitigation; chaos drills |
| # | Question | Max |
|---|---|---|
| 1 | How well-defined is your IC role? | 6 |
| 2 | How do you track MTTD/MTTR? | 6 |
| 3 | How do you conduct postmortems? | 6 |
| 4 | How effective are escalation paths? | 6 |
| 5 | How do you train incident responders? | 6 |
| Domain | Relationship |
|---|---|
| On-Call | On-call handles initial response |
| Alerting | Alerts trigger incident flow |
| Culture | Blameless culture enables learning |
Incidents Are Learning Events
Every outage makes us stronger.