Cognitive Biases · Growth Library
Review a Decision Using What Was Known at the Time
Separate the quality of the process from the luck of the outcome.
Try this
Write the decision and its date, list the information and constraints that were available then, separate later discoveries into a different section, note which realistic alternatives were considered or missed, identify one process weakness or strength, and define one change to use for a similar future decision.
Check-in: What was genuinely knowable at the decision point, what did I learn only afterward, and what should change in the process next time?
Evidence: Practical guidance; no evidence-like claim is detected in the current source record.
Review note: The inherited article mixed unsupported decision-quality effects with invented timing and memory thresholds, fabricated first-party results, arbitrary scores, and emotional-regulation instructions. The effective public record is narrowed to reconstructing what was actually known at the decision point, separating later information, inspecting concrete process strengths and omissions, and carrying one process improvement into the next similar decision.
A result can make an earlier choice look obviously good or obviously bad. A useful retrospective separates the outcome from the information that existed when the choice was made. That creates a fairer process record and, more importantly, a concrete improvement for the next similar decision.
1. Reconstruct the decision point
Write what was being decided, who owned the decision, the date or stage, and the constraints that were active. Then collect the artifacts that existed at that point. Do not start by explaining the later outcome.
2. Separate then-known facts from later information
Create two lists: information available before the decision and information learned afterward. If an item is based only on memory, mark that uncertainty. This prevents later knowledge from quietly changing what the original decision environment looked like.
3. Inspect the process, not just the result
Ask whether important constraints were visible, alternatives were considered, dissent or uncertainty was recorded, ownership was clear, and a fallback existed where one was needed. Name specific omissions instead of assigning a vague good-or-bad score.
4. Carry one improvement forward
Choose one process change that would improve a similar future decision: capture a missing input, require a named owner, document an assumption, add a rollback trigger, or request a second view. Put that change where the next decision will actually encounter it.
Questions to consider
Does a good process make a bad outcome acceptable?
No. Outcomes still matter. The process review asks a different question: whether the decision used the information, constraints, alternatives, and responsibilities available at the time, and what should be improved before a similar choice recurs.
What if I cannot remember what was known then?
Prefer contemporaneous artifacts such as tickets, notes, messages, dashboards, approvals, or decision records. Mark uncertain memories as uncertain rather than turning hindsight into a reconstructed fact.
Maintenance record
Review history
Current status: Reviewed. An editorial or evidence review is recorded and no later event changes that conclusion.
2026-09-10 · reviewed · Brali editorial agent (AI-assisted) Source: protocol-content-overrides-search-review-wave-6.json
Replace unsupported debiasing effects, invented timing and memory thresholds, fabricated first-party process results, arbitrary scoring systems, and therapy-adjacent framing with a bounded retrospective decision review.
Browse the review ledger · Challenge or update this hack
Implementation observations can trigger a review, but they cannot change an evidence conclusion by themselves. Commercial relationships do not control review status or outcomes.
Continue from here
Choose the next useful path.
Article versions
Brali keeps substantive article history visible. Later reviews may refresh wording, sources, examples, or boundaries without silently replacing the record.
- Version 2025-10-06: first recorded publication in the migrated Brali corpus.
- Evidence review 2026-09-10: reviewed by Brali editorial agent (AI-assisted); evidence state is
practical.
Canonical source record · Evidence state: practical.