The problem with judging by results
After a loss, most people reach for one of two explanations: “I was unlucky” or “I played terribly.” Each is sometimes true, and each is often a reflex. In games with chance, the result of one session is a poor measure of decision quality. A good decision can lose, and a bad one can win. If you judge only by outcome, you learn the wrong things: you repeat poor choices that happened to work and abandon sound ones that happened to fail.
A proper review aims to separate the quality of the decision from the quality of the result. That separation is the whole purpose. The method below is simple enough to use after any game, from a board game evening to a long online session.
Step 1: write it down while it is fresh
Memory distorts quickly. We remember dramatic moments and forget the dull ones where the real mistakes often sit. Record the game soon afterwards: key decisions, what you knew at the time, and what happened. Even a few short lines per game are better than nothing. If the game allows recordings or move histories, use them.
Keep the notes factual. Write “I held back my strongest card on turn four,” not “I played badly.”
Step 2: pick the real decision points
Most games contain only a handful of moments where your choice really mattered. Pick three to five. Common candidates are:
- a point where you committed a large share of your resources
- a moment where you changed or abandoned a plan
- a decision made quickly that deserved more thought
- a choice you felt uneasy about at the time
Ignore the rest for now. Reviewing everything leads to shallow notes.
Step 3: judge the decision with what you knew then
For each decision point, ask three questions:
- What information did I have at that moment?
- What were my realistic options?
- Given only that information, was my choice reasonable?
This is the key discipline. You are not allowed to use knowledge from later in the game. Hindsight makes almost every error look obvious, but you could not see it then. The honest question is whether your reasoning was sound given what was visible.
Step 4: estimate the role of chance
Next, ask how much luck was involved in the outcome of that decision. A simple illustration can make this concrete.
Suppose you took an action that would succeed 3 times out of 4, and the alternative was a safe option that gave a small but certain benefit. You chose the risky action and it failed. One failure at 3 in 4 odds is not unusual: the chance of failing is 1 in 4, or 25 percent, so you would expect to see it about once in every four tries. Whether the choice was wise depends on the sizes of the gain and loss, which is the question of expected value, not on the one result. If the reward for success was large and the cost of failure small, the choice may have been good despite the loss.
Compare that with a case where you took the action knowing the payoff did not justify the risk. There the loss was a bad decision that happened to fail, and it deserves to be flagged as one.
A rough sorting helps:
| Decision | Result | Likely lesson |
|---|---|---|
| Sound | Good | Fine, but do not over-credit yourself |
| Sound | Bad | Probably variance; keep the process |
| Flawed | Good | Dangerous: you got away with it |
| Flawed | Bad | Real lesson; fix the process |
The third row is the most important and the least noticed. Lucky wins hide mistakes.
Step 5: look for patterns across games
A single game says little. The valuable information appears when the same issue recurs across many games. Do you often rush when you are behind? Do you avoid close calls? Do you play worse late in a long session? Patterns are far more reliable than any one story. Keep in mind that a small number of games will not reveal much, so be careful about concluding anything from a handful of results. Patience with the sample is part of honest review.
Step 6: choose one thing to change
End the review with a single, specific adjustment, such as “pause and count my options before committing resources,” not a list of ten resolutions. One change you will actually practice beats many you will forget. At the next session, check whether you did it.
Biases that spoil reviews
- Self-serving bias: crediting wins to skill and losses to luck.
- Harsh self-blame: treating every loss as a personal failure, which can make you stop reviewing altogether.
- Hindsight bias: believing the outcome was predictable.
- Sunk cost thinking: defending a plan only because you invested in it.
- Tilt: reviewing in the middle of frustration, when the analysis is least reliable. A short break helps.
When money is involved
If you play games where you stake money, a review should include your spending as well as your decisions. Did you stick to the spending limits you set before playing? Did you play on after a loss to try to get it back? Chasing losses is a well-known trap, and it is a flaw of process, not an unlucky stretch. If you find you cannot stay within limits, that is a sign to stop and contact a local support service. A review is meant to improve your understanding and enjoyment, never to justify playing more.