Incident Impact Quantification

Honest numbers.

Overview

Incident impact quantification produces honest numbers about what an incident cost: customers affected, revenue at risk, engineering hours consumed, reputation effects. Postmortems that contain only adjectives ("major customer impact") cannot drive prioritization; postmortems with numbers (12,000 customers affected, $48k revenue at risk, 80 engineer-hours consumed) anchor the investment conversation in evidence rather than anecdote.

• Customer impact. How many customers affected, in what way; concrete reach is the input to comms decisions and SLA-credit calculations.
• Revenue impact. Direct losses, SLA credits, churn risk; dollar numbers move investment conversations that adjective numbers cannot.
• Engineering hours. On-call response time, postmortem time, action-item work; opportunity-cost number that anchors prioritization.
• Reputation impact plus honest methodology. Public visibility and customer-trust effects acknowledged; conservative estimates with documented methodology preserve credibility.

The approach

The practical approach is to use real data wherever possible (billing system, support ticket counts, customer engagement metrics), make conservative estimates when data is missing (low estimates beat optimistic ones for credibility), document methodology so the numbers are auditable, use the same methodology across postmortems for cross-postmortem comparability, and feed the numbers into leadership review so reliability investment lands with business context.

• Use real data. Billing system, support tickets, customer engagement; the data avoids guessing and survives scrutiny.
• Conservative estimates. When data is missing, estimate low; preserves credibility for the next postmortem’s numbers.
• Document methodology. Per-number calculation method; supports auditability and survives leadership questions.
• Cross-postmortem comparability plus leadership review. Same methodology produces comparable numbers across postmortems; numbers support investment conversations with business case.

Why this compounds

Impact quantification compounds across postmortems. Each numbered postmortem produces data the next investment conversation can reference; cross-postmortem trends reveal which incident classes are most expensive; the team’s prioritization becomes evidence-driven rather than anecdote-driven.

• Prioritization. Concrete numbers drive engineering investment; the team invests where the data points.
• Leadership conversations. Dollar numbers get executive attention; the reliability investment lands with business case.
• Trend visibility. Comparable numbers reveal trajectory; the team can answer "are we improving" with data.
• Operational culture. Quantification signals that incidents matter at the executive level; the team treats reliability as engineering work, not janitorial.

Incident impact quantification is an operational discipline that pays off across years. Nova AI Ops integrates with billing and customer telemetry, surfaces incident-cost patterns, and supports the team’s reliability investment discipline.