Severity Classification & Escalation Matrix

Stack: THE CHAOS STACK →Senior (L5-L6)protocol

⚡THE SHORT ANSWER

By establishing objective criteria based on customer and financial impact—defining exactly who gets paged, who leads triage, who handles executive communications, and how fast the team must respond.

Engineering Handbook & Failure Dynamics

6-Dimensional Architecture Breakdown

⚙️1. Underlying Mechanism

Execution

▸
Severity tiering categorizes incidents into actionable levels: Sev-1 (Critical outage, core revenue down, all-hands incident command)
▸
Sev-2 (Major degradation, significant user impairment, primary squad paged)
▸
Sev-3 (Minor issue with viable workaround, handled during business hours)
▸
Sev-4 (Cosmetic or low-impact bug, standard backlog ticket). The Escalation Matrix specifies automated paging timers (e.g., if Sev-1 is unacknowledged in 5 minutes, escalate to Engineering Director)

🎯2. Appropriate Use Context

Scope

Mandatory foundation for all on-call rotations, customer support handoffs, and executive reporting pipelines.

⚠️3. Production Failure Modes

P0 Risk

A junior engineer declares a Sev-1 for a broken internal analytics chart, waking 15 senior engineers at 2 AM and draining the incident response budget for real outages.

📡4. Diagnostic Signals & Telemetry

Telemetry

✓
Constant arguments between Support and Engineering over bug priorities
✓
critical outages being ignored because they were mislabeled as Sev-3
✓
lack of written escalation paths

🛡️5. Prevention & Safeguards

Safeguards

✓
Publish unambiguous, objective definitions for each Sev level based on financial loss per minute or percentage of impacted active sessions
✓
grant on-call engineers authority to downgrade false Sev-1s

⚖️6. Architectural Trade-offs

Trade-off

Requires organizational training and strict adherence to protocol in exchange for zero panic and predictable triage workflows.

📋

Case Study (TinyCTO In-Field Example)

REAL-WORLD TELEMETRY

TinyCTO Episode 20: The support team paged the entire backend squad on Saturday for a single VIP user login issue. The CTO established a Sev-2 rule requiring >5% affected users to trigger off-hours paging.

Interactive Concept Drills

3 Cards

What defines a Sev-1 incident?

A critical customer-facing outage or data loss event that halts core business operations with no viable workaround.

What is an Incident Escalation Matrix?

A rule-based protocol defining when and to whom an incident notification escalates if unacknowledged or unresolved within set time limits.

Why should Sev-3 and Sev-4 bugs never wake an engineer at night?

Because they do not halt core business operations, and waking engineers degrades cognitive performance for genuine Sev-1 emergencies.