Separate what was knowable during an incident from what became obvious only after the outcome.
Open →Decision technique
Red-team review
Give a strong alternative case enough space to challenge the preferred option.
When to use
A specific reasoning move for a specific problem.
Before approvals, vendor selection, roadmap commitments and consequential group decisions.
Procedure
Run the technique.
- State the current preferred option and its strongest argument.
- Assign a reviewer to build the best case against it.
- Require concrete failure modes and missing evidence, not generic criticism.
- Resolve or explicitly accept the strongest remaining uncertainty before approval.
Limit
What this technique cannot guarantee.
A ritual adversarial review can become theatre. The red team needs access to evidence and permission to change the decision.
Situations
Where this may be useful.
Compare tools using precommitted criteria rather than demos, authority or the first price shown.
Open →Check whether a score is still a useful proxy for the real goal and whether the comparison is being interpreted consistently.
Open →Evidence-linked concepts
Why this check may matter.
Read the evidence and limits before treating this technique as relevant.
Open →Practice this technique
See when the move becomes useful.
A team prefers a new platform and highlights its strong benchmark score. It dismisses workload, data quality and operating constraints that are not measured by the benchmark.
Skill: Evidence evaluationOpen scenario →