Skip to content
tezvyn:
Menu

Counterfactual Reasoning in Incident Analysis

MediumHow cards are made

Counterfactual reasoning asks what would have prevented or mitigated an incident: if this alert had existed, if this check had run. Used well it finds systemic gaps, but it is a trap when it implies a single person should have just acted differently in…

Why it exists

Understanding an incident is not only about what happened but about what could have changed the outcome. Counterfactual reasoning exists to systematically probe those alternatives so the team can identify safeguards that were missing and would meaningfully prevent or shrink a recurrence.

The mental model

Think of replaying the incident while changing one variable at a time and asking whether the outcome improves. If an alert had existed on this metric, would detection have been faster. If a rate limit had been in place, would the cascade have been contained. The useful version targets the system and its controls; the harmful version targets a person, asking why didn't you just notice, which is hindsight bias dressed up as analysis.

How it works

During analysis, for each phase of the incident you pose alternatives focused on mechanisms: detection, prevention, and mitigation. Good counterfactuals are grounded in plausible, implementable changes, such as an automated guardrail, a missing test, or a safer default, and they translate directly into remediation items. The discipline is to keep them blameless: phrase them about what the system lacked, not what an individual failed to do, because the responder almost always acted reasonably with the information available in the moment.

When it matters

It matters most in blameless postmortems, where the entire value depends on extracting systemic lessons without scapegoating. Done well, counterfactuals are an engine for generating preventive action items. Done poorly, they corrode psychological safety, discourage honest disclosure, and produce shallow fixes like telling people to be more careful, which never hold.

A concrete example

A harmful counterfactual: if the on-call engineer had checked the dashboard sooner, the outage would have been shorter. A constructive one: if an automated alert had fired on the queue depth that was already climbing, detection would not have depended on someone happening to look, so the action item is to add that alert. The second changes the system; the first just blames a person for not having foresight.

Interview question

Which counterfactual is constructive in a blameless incident analysis?

  • a.If an automated alert had existed on the climbing queue depth, detection would not have depended on someone lookingCorrect
  • b.If the on-call person had been more experienced, it would not have happened
  • c.If the engineer had simply checked the dashboard sooner, it would have been shorter
  • d.If people just cared more about reliability, this would be avoided
Why?

A constructive counterfactual targets a missing system control, like an absent alert, yielding a concrete fix. The others blame individuals using hindsight bias, which produces no durable change and harms psychological safety.

Just read this? Test yourself on what you have been reading.

Put your scrolling time to good use

Learn one idea, try a quiz and save useful cards for revision. Tezvyn makes it easy to learn and stay current in your tech field, a few minutes at a time.

The iPhone app is on the way

We are building it. Until it lands, nothing here is held back from you: every interview card, your saved cards, streaks and the job board all work in Safari, plus hundreds of free practice quizzes of thirty questions each. Sign in and it all carries over to the app the day it arrives.

Want it as an icon? Tap Share at the bottom of Safari, then Add to Home Screen. It opens full screen and the cards you have read stay available offline.

Get it on Google PlayiPhone app coming soon

We are hiring for this. Every open role lists the topics its interview covers, so you can prepare for the real thing rather than guessing.

See open roles