Use this concept as a question to test the decision, not as a label for a person.
Open →Decision situation
Production incident review
Separate what was knowable during an incident from what became obvious only after the outcome.
Signals to notice
Reasons to slow down and check.
- The cause now feels obvious.
- A single recent incident is driving a broad process change.
- People are judging the decision mainly by the outcome.
Questions before action
Make the missing evidence visible.
- What was actually known at each decision point?
- Which alternative explanations were plausible then?
- What process change is supported by repeated evidence rather than one vivid event?
Relevant lenses
Concepts that may help you test the reasoning.
Practical moves
Do something different, not only notice a label.
Preserve what was known, expected and uncertain before the outcome changes memory.
Open →Give a strong alternative case enough space to challenge the preferred option.
Open →Decide in advance what evidence should cause a forecast or decision to change.
Open →Skill to develop
Metacognition
You can review your reasoning process without confusing confidence, outcome and hindsight with decision quality.
Practice this situation
Choose a useful first move.
After an outage, the failed component is easy to identify. Reviewers say the on-call engineer should have known immediately, although several alerts looked equally plausible during the incident.
Skill: MetacognitionOpen scenario →A rare database failure causes a severe outage. The team proposes an expensive control for every system without checking how often the failure occurs or whether the control addresses other risks.
Skill: MetacognitionOpen scenario →