Start with the distinction
Core relationship: Multiply each outcome value by its probability and add the contributions. Then inspect whether the decision is repeated, whether losses are affordable, and whether values represent what actually matters.
For expected value for everyday decisions, begin with list mutually exclusive outcomes and finish with read the distribution. The sequence keeps the starting facts, intermediate result, and final limit visible instead of relying on memory.
Work through the reasoning
List mutually exclusive outcomes
Avoid counting the same result in more than one branch. Capture the result before moving to use a common value unit. A written output shows whether the next deduction follows from the evidence or quietly adds a new assumption.
Use a common value unit
Time, money, or scored utility must be consistent before addition. Compare this output with the warning about predicting one outcome. If that failure still fits, revise the representation before using the result in another deduction.
Check probability coverage
Branches should total 100% for a complete model. Use check probability coverage as a checkpoint. Name the input, the change made, and the conclusion that becomes available so another reader can reproduce the move.
Read the distribution
Record the best case, worst case, and reversibility beside the average. Finish by stating what this step establishes and what it leaves undecided. That boundary prevents a valid local conclusion from being stretched beyond the question.
Concrete example
List mutually exclusive outcomes in the case
A trial has a 60% chance to save ten hours and a 40% chance to cost four hours. Its expected time value is 4.4 hours saved, but a deadline may make the four-hour downside unacceptable this week.
Why read the distribution matters
The case starts with list mutually exclusive outcomes, then uses use a common value unit to control the next inference. The conclusion is acceptable only after read the distribution. Changing any fact that supports those moves can change the answer, while an unrelated detail should not.
Where the method breaks
Predicting one outcome
Expected value is not the most likely result. Return to list mutually exclusive outcomes and rebuild only from information the problem actually provides.
Ignoring nonlinear impact
Losing the last essential resource can matter more than its numeric amount. Compare the disputed move with check probability coverage; the two should use the same definitions and direction.
Hiding missing branches
A neat total can conceal outcomes that were never modeled. Run the practice task while deliberately watching for hiding missing branches. Record the first point where the reasoning begins to drift.
Check against predicting one outcome
Questions for use a common value unit
- Can another reader reproduce list mutually exclusive outcomes from the stated information?
- Did you complete use a common value unit without reversing or enlarging the claim?
- Does the result survive the failure mode predicting one outcome?
- Which part remains uncertain after read the distribution?
This check is specific to the method above. A clear answer should expose the evidence chain and the point where a different fact would produce a different conclusion.
A short practice task
Use the expected value calculator for a small reversible choice. Then write one reason the higher average might not be the better immediate action.
Continue after read the distribution
Use the probability reasoning guide for the broader method, then apply the idea in the probability calculator. Keep the written reasoning so the next attempt can improve a specific step rather than simply repeat the exercise.
Compare this method with Base-Rate Neglect in Real Decisions, then continue to Permutations vs Combinations: Does Order Matter? for a different reasoning task.