Judging a Decision by Its Process
Judging a Decision by Its Process
A process judgment is a dated note, written before the result exists, of why the choice made sense given what was known at the time. A sloppy choice can still get lucky. A sound choice can still fail. Because of those two cases, the note is the grade. The later result is not the grade.
Core takeaways
- Write a dated note before the result exists, saying why the choice makes sense given what is known then. That note is the grade.
- Judging by the outcome alone makes two errors. It rewards a bad process that got lucky, and it abandons a good process that met bad conditions.
- The more of the result you actually owned, the more the result may grade the process. A well-specified exam is higher-control than a career bet.
- After the result, review the process with six questions and four quick checks. The result is one piece of feedback. It is not the whole verdict.
- Resulting, hindsight certainty, emotional verdict, no feedback loop, and overcorrection are the five ways the review fails.
- The process improves on the next repetition. That is regulation. It is not a verdict on the person.
Why the result is not the grade
This judgment is used after the result is known. Decisions are made with incomplete information. Outcomes are affected by timing, chance, changing conditions, other people, and variables that were never under control. Judging by the outcome alone produces two errors. It rewards a bad process that got lucky. It abandons a good process that met bad conditions.
The better question is this: given what was known at the time, was the process reasonable?
How much of the result was yours
Different situations give different amounts of control. In some, the outcome is mostly the process. In others, the outcome is mostly luck. The more of the result that was actually owned, the more the result may grade the process. A well-specified exam is higher-control than a career bet. That is a direction of difference. It is not a percentage.
The note written before the result
The tool that makes the question answerable is a note written before the outcome exists. It says why the choice made sense at that time. After the result, the quality of the process and the quality of the outcome stay separate. The result is one piece of feedback. It is not the whole verdict. The process improves on the next repetition.
The six review questions
A process review asks six things. What was known at the time? What was uncertain? What downside was protected? What option improved the position? That fourth question is covered on Positional Decisions and Expected Value. What would change my mind? That fifth question continues on Changing Decisions. What did the outcome teach?
Four quick checks
Four short checks sit beside the six questions. They replace a separate toolkit. What assumption would break this if it were false? What is the strongest case against the preferred option? If this fails, what is the most likely reason? Is this option being chosen because it is good, or because it protects comfort, identity, or self-image?
Exam results, the high-control case
Learning outcomes are noisy. Academic assessments are the high-control case. With a sound process, results are more predictive. The luck that is left is small, for example being sick on the day. A poor test score does not by itself mean the method was bad. A good score does not by itself mean the method was strong. Inspect the process. Do not treat a single score as nothing either.
Five questions do that inspection. Was encoding deep enough? Was retrieval spaced and interleaved? Were gaps found early? Was the exam different from what was expected? Was the result caused by knowledge, execution, stress, or timing?
That inspection turns performance into Self-Regulation. It stops performance from being a verdict on the person. Kolbs Experiential Cycle gives the after-action shape: what happened, how it felt and why, what rule that suggests, and what changes next time.
Five ways the review goes wrong
| Failure | What it does |
|---|---|
| Resulting | Grades the decision only by the final result |
| Hindsight certainty | Makes the right answer feel obvious after |
| Emotional verdict | Treats disappointment as evidence |
| No feedback loop | Leaves the process unimproved |
| Overcorrection | Lets one bad outcome flip the whole strategy |
Resulting is the name for the first row: it treats the result as the grade.
In a high-control repeat, the result may amend the dated note. In a low-control bet, the result is one noisy input. In both cases the next move is to improve the process for the next repetition. That is regulation. It is not a verdict on the person.
How to practice this
- Before the result exists, write a dated note saying why the choice makes sense given what you know. Notice what you can list as known and what you must list as uncertain.
- After the result is known, ask what was known, what was uncertain, and what downside was protected. Then ask what option improved the position, what would change your mind, and what the outcome taught. Notice whether the process was reasonable given only what the note says was known.
- Name the assumption that breaks your option, the strongest case against it, and its likeliest cause of failure. Then notice whether you are choosing it because it is good or because it protects comfort, identity, or self-image.
- Decide how much of the result you owned, and how much came from timing, chance, conditions, or other people. In a high-control repeat, let the result amend the note. In a low-control bet, notice that the result is one noisy input.
- After a test score, ask whether encoding was deep enough, retrieval was spaced and interleaved, and gaps were found early. Ask whether the exam differed from what you expected, and whether knowledge, execution, stress, or timing caused the result. Notice that one score, poor or good, is one piece of feedback and does not grade the method alone.
- Read the finished review against the five failures. Notice if you graded only by the result, if the right answer now feels obvious, or if disappointment is counting as evidence. Notice if the process stayed unchanged, or if one bad outcome is flipping the whole strategy.
Related pages
- Decision Making: the hub; the full split between process and outcome is on that page.
- Positional Decisions and Expected Value: the position and expected-value questions in the review.
- Changing Decisions: the change review; the question of what would change my mind continues there.
- Kolbs Experiential Cycle: after-action: what happened, what rule, what changes.
- Self-Regulation: performance as regulation instead of a verdict on the person.
Open questions
Is the pre-outcome note enough, or does a high-consequence choice need a repeated journal?
Sources
- Duke, Thinking in Bets (2018): resulting, grading a decision by how it turned out. Names the two errors (lucky-bad-process, unlucky-good-process).
- Fischhoff 1975: hindsight rewrites what was knowable. Support for writing the reasons before the result exists.
- Howard / decision-analysis: decision quality and outcome quality are separate objects.