Process-Over-Outcome Decision Review
Judge decisions by how they were made, not by one noisy result
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 4
- Confidence
- 96%
The process-over-outcome model evaluates a decision using the information, assumptions, and reasoning available when it was made. A favorable result does not automatically validate a poor decision, while an unfavorable result does not necessarily invalidate a sound one. After each consequential choice, separate controllable inputs from luck, assess whether the process correctly handled uncertainty, and update only the parts that proved weak. This creates learning that transfers to future decisions instead of emotional reactions to isolated wins or losses. The model comes from poker, where correct probabilistic play can still lose in a single hand, and applies equally to launches, hiring, negotiation, and strategic bets.
Origin
Blake Eastman learned the model through professional poker, where luck can obscure the quality of an underlying decision.
Core principles
- 01Good decisions can produce bad short-term outcomes
- 02Luck and process must be evaluated separately
- 03A repeatable decision process matters more than one result
- 04Desire for a particular outcome can distort judgment
How to run it
- 1
Capture the pre-decision state
Write down the facts, constraints, probabilities, and options known before acting.
Pro tip Do this before the result arrives so hindsight cannot rewrite your reasoning.
Watch out Do not include information that became available only afterward.
- 2
Document the decision process
Explain how the available inputs produced the chosen action and what trade-offs were accepted.
Pro tip State which assumption would most likely invalidate the choice.
Watch out A conclusion without reasoning cannot be meaningfully reviewed.
- 3
Separate skill from luck
After the outcome, identify which elements were controllable and which were random or external.
Pro tip Ask whether you would make the same choice again with the original information.
Watch out Do not treat a win as proof that every part of the process was good.
- 4
Update the reusable process
Change decision rules only when the review reveals a genuine flaw or better evidence.
Pro tip Keep what worked even when the immediate outcome was disappointing.
Watch out Overcorrecting after one unlucky result creates unstable strategy.
In the wild
A founder validates demand, prices responsibly, and executes a strong launch, but a sudden market event suppresses purchases. The team reviews the original assumptions and execution separately from the external disruption rather than discarding the offer.
→ The company preserves a sound launch process while adjusting future timing safeguards.
A player makes a low-probability call without sufficient information and happens to win. Instead of treating the profit as validation, the player reviews the reasoning and recognizes that repeating the same choice would lose over time.
→ The player avoids reinforcing a poor decision because of one lucky result.
Common mistakes
Outcome bias
Treating every win as a good decision and every loss as a bad decision prevents accurate learning.
Hindsight reconstruction
Adding information learned later makes the original process appear more informed than it really was.
Overcorrecting after variance
Changing a sound method after one unlucky result replaces discipline with reactivity.
Is it for you?
Best for
Entrepreneurs, investors, negotiators, and teams making repeated decisions under uncertainty.
Not ideal for
Routine deterministic tasks where following the procedure reliably produces the same result.
From the transcript
“More than anything, it taught me the value of process. So in poker, you're always looking for you're not focusing on outcome. You're focusing on…”
“So it's not about whether or not the decision was necessarily right or wrong. It was about the process that you've arrived to create that…”
“whoever wants it more loses in a negotiation table.”
From the episode
Nonverbal Communication Secrets That Drive Sales and Build Trust with Blake Eastman
Blake Eastman