Decision OS / Review

Review decisions to improve judgment, not to prosecute your past self.

Separate process quality from outcome quality and extract one improvement for future decisions.

Educational only. Not legal, medical, mental health, financial, investment, tax, employment, immigration, emergency, or professional advice. Use qualified support for high-stakes domains and urgent safety concerns.

Case notes

Decision Review makes the decision process visible before the outcome arrives.

A decision review is not self-punishment. It is how judgment compounds. The review asks what was known then, what changed, what signal was missed, and what process should improve next time.

Good outcomes can come from weak process. Bad outcomes can come from strong process. Decision OS reviews the process without pretending outcomes do not matter.

01

Separate process and outcome.

A lucky result should not validate a sloppy process.

02

Use what was known then.

Do not judge the past self with future evidence it could not access.

03

Extract one process improvement.

Review should change the next decision, not just tell a story.

Common problems and experiments

Make the next process move small enough to test this week.

I beat myself up after bad outcomes.

Experiment

Score process quality separately from outcome quality.

What to watch

A bad outcome is not automatic proof of a bad decision.

I ignore good-luck warnings.

Experiment

Ask what would have happened if the luck had broken the other way.

What to watch

Good outcomes can hide fragile process.

I never review.

Experiment

Schedule a monthly 20-minute review of one decision card.

What to watch

Judgment improves when review is small enough to repeat.

Prompt to try

Keep one decision sentence visible.

What should my future decision process do differently because of this review?

7-day protocol

The decision review loop

  1. 01 Choose one past decision card.
  2. 02 Write the outcome without drama.
  3. 03 Score process quality from 1 to 5.
  4. 04 Score outcome quality from 1 to 5.
  5. 05 Name what was knowable then.
  6. 06 Name one signal missed or one lucky break.
  7. 07 Write one process rule for next time.

Decision checklist

Mark the process, not the outcome.

Source notes

Outcome and judgment

Judgment can be distorted by heuristics and retrospective storytelling.

Open source

Premortem

Premortems and reviews work together: one improves the plan before action, one improves future process after results.

Open source

Education-only scope

Decision review is educational reflection, not professional advice or crisis guidance.

Back to Decision Inventory Run Decision Lab Open Life Dashboard