Separate what was knowable during an incident from what became obvious only after the outcome.
Open situation →Reasoning Practice · Intermediate
One outage creates a permanent rule
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.
Your decision
What should happen before the control becomes policy?
Show the best first move
A. Define the evidence and recurrence threshold that would justify the control across systems.
Why this move helps
The vivid outage can dominate risk judgment. Predefined criteria make the policy depend on recurrence, exposure and control effectiveness rather than memory alone.
Evidence still missing
- Base rate of the failure mode.
- Systems with the same exposure.
- Expected risk reduction and operating cost of the control.
Evidence note
Availability is a plausible risk because one severe event dominates the proposal. A rare event can still justify a broad control when expected harm is high.
Next action
Set a measurable adoption rule and test it against the system portfolio.
Best first lens
Availability Heuristic
Use the lens to ask a better question. It does not prove that a person or team has a cognitive bias.
Other defensible lenses
The situation may have more than one explanation.
Continue the path
Situation → skill → technique → action.
You can review your reasoning process without confusing confidence, outcome and hindsight with decision quality.
Build this skill →Decide in advance what evidence should cause a forecast or decision to change.
Run the technique →
