Expected Value

Concept of the skill

What it is: Expected value is a decision method for choosing under quantified uncertainty. It ranks actions by summing probability times value across each possible outcome, then comparing the resulting expected payoff or utility.

Mental model: Build a payoff table. Rows are actions, columns are possible outcomes, and each outcome has a probability and a value in the same unit. Expected value is the weighted total for each row after costs, checked against constraints.

Why it exists: Agents over-weight vivid upside, visible downside, or the option with the best story. Expected value forces each option to state how often each outcome happens, how much it matters, what it costs, and whether the result survives sensitivity checks.

What it is NOT: It is not Bayesian updating, broad backlog prioritization, second-order consequence discovery, formal valuation, or a guarantee that the average outcome will occur once.

Adjacent concepts: Expected utility, expected monetary value, payoff matrices, decision trees, break-even probability, sensitivity analysis, value of information, risk of ruin.

One-line analogy: Expected value is a scale that weighs every future by both its size and its chance, then compares the total weight of each option.

Common misconception: A positive expected value is not automatically a good decision. If the downside can kill the project, violates a constraint, or depends on made-up probabilities, the correct next move may be mitigation or information-gathering.

Expected Value

Domain Context

Expected value is a portable decision framework for ranking actions when outcomes are uncertain but probabilities and values can be stated. It is useful for product bets, experiments, investments, risk tradeoffs, information-gathering choices, and go/no-go decisions where the input probabilities are already accepted or can be estimated honestly.

Use synthetic, aggregate, or public examples only. Do not include personal data, customer data, payment data, order data, private file paths, secrets, or confidential business facts in expected-value examples or evals.

Correct application requires a clear action set, mutually exclusive outcomes, probabilities that sum coherently, values in one shared unit, costs included, sensitivity checked, and hard downside constraints handled before recommending the highest expected value.

Coverage

This skill teaches the operational expected-value loop:

1. Define the decision and action set.
2. Enumerate mutually exclusive, collectively relevant outcomes for each action.
3. Assign probabilities conditional on each action.
4. Assign value or utility in one shared unit.
5. Include costs, opportunity costs, and downside exposure.
6. Compute expected value for each action.
7. Run sensitivity and break-even checks.
8. Apply constraints such as risk of ruin, safety, privacy, legality, or irreversibility.
9. Decide, mitigate, reject, or gather information based on the comparison.

It also covers expected monetary value versus expected utility, fake precision, probability calibration, value of information, variance, tail risk, and boundaries with nearby reasoning and strategy skills.

Philosophy of the skill

Most bad expected-value work fails before the arithmetic. The agent chooses the outcome list that favors the preferred answer, uses probabilities that do not sum to a coherent scenario set, mixes dollars with time or trust, forgets action cost, and then treats the final number as objective.

The discipline is not "turn every decision into math." The discipline is to expose the hidden math that was already happening. If a team says a feature is "worth trying," expected value asks: worth how much, how often, at what cost, and what downside could invalidate the average? Rough ranges are acceptable when they are labeled and stress-tested. Fake exactness is worse than an honest range.

1. Decision Frame

Expected value starts with actions, not outcomes. Compare actions that are actually available.

Do not compute expected value over vague options like "make the product better." Convert the question to concrete actions: "ship experiment A this week," "run a two-day research probe," "do nothing," or "buy the risk down first."

2. Formula

For one action:

EV(action) = sum(probability_i * value_i) - cost(action)

For expected utility, replace monetary value with utility:

EU(action) = sum(probability_i * utility_i) - utility_cost(action)

Use expected utility instead of expected monetary value when money is not linear with preference, downside risk has nonlinear pain, or the choice includes non-financial values such as trust, time, reputation, safety, or strategic position.

3. Probability Rules

Probabilities are not decoration. They determine how much each outcome counts.

If the core uncertainty is what probability to assign after new evidence, use bayesian-reasoning first. Expected value starts after the probability estimate is accepted enough to compare actions.

4. Value Rules

Every outcome value must be in the same unit for the comparison to mean anything.

Expected value is often wrong when it treats all dollars, all hours, or all failures as linear. Losing the last week before launch is not the same as losing a random week in a quiet month. A single privacy breach is not "just one bad outcome" if it crosses a non-negotiable threshold.

5. Sensitivity and Breakpoints

The expected-value number is less important than knowing what would change the decision.

Run these checks before recommending an action:

If a small change in one guessed probability flips the answer, the right recommendation is usually "gather information or run a smaller probe," not "choose the option with a thin expected-value lead."

6. Downside Constraints

Expected value can recommend a positive-average action that is still unacceptable.

Treat these as vetoes or required mitigations:

• risk of ruin,
• privacy exposure,
• illegal or unethical actions,
• unrecoverable trust loss,
• irreversible architecture damage,
• budget or cash-flow constraints,
• safety-critical failure modes.

The rule is: maximize expected value only inside the feasible set. A positive expected value outside hard constraints is not a recommendation; it is a signal to redesign the option, buy down risk, or reject it.

7. Agent Workflow

When applying expected value, produce this compact trace:

Decision:

Options:
- A:
- B:

Outcome model:
- A:
  - outcome / probability / value:
- B:
  - outcome / probability / value:

EV calculation:
- A:
- B:

Sensitivity:
- break-even:
- most fragile assumption:

Constraints:
- ruin/privacy/legal/irreversibility:

Recommendation:
- choose / mitigate / gather information / reject:

Prefer a small table over prose when more than two outcomes are compared.

8. Worked Example

Scenario: choose between shipping a small product experiment or spending the same week on maintenance. Use synthetic values only.

Experiment gross expected value:

(0.20 * 120) + (0.50 * 25) + (0.30 * -20) = 30.5

If the experiment costs 10 units of effort beyond maintenance, net expected value is 20.5, below the maintenance option's 25. If the experiment can be reduced so the extra cost is 4, net expected value becomes 26.5 and wins, assuming no hard constraints are violated.

The decision is not "experiments are good" or "maintenance is safer." The decision is driven by the cost and the probability of reusable learning. That is the assumption to test.

9. Value of Information

Information has expected value when it can change the decision.

Use this shortcut:

VOI = expected improvement from better choice after learning - cost of learning

Gather information when:

• the current expected-value leader has a small margin,
• the decision flips under plausible assumptions,
• the information is cheap relative to the stakes,
• the action is hard to reverse,
• the downside constraint is uncertain.

Do not gather information when the same action wins under every plausible range or when learning costs more than the possible decision improvement.

10. Boundaries With Neighbor Skills

11. Anti-Patterns

Cross-Domain Synergy

• bayesian-reasoning supplies better probabilities when new evidence should change them.
• second-order-thinking expands the outcome list before probabilities and values are assigned.
• prioritization is useful when reach, confidence, effort, strategic fit, and non-quantified constraints matter more than a pure payoff calculation.
• constraint-awareness keeps the feasible set honest before expected-value optimization begins.
• evaluation helps decide whether the comparison has enough evidence to support the recommendation.

Verification

After applying this skill, verify:

• The action set is concrete and comparable.
• Outcomes are mutually exclusive enough to avoid double-counting.
• Probabilities are conditional on the action and sum coherently.
• Probability source quality is labeled.
• Values use one shared unit or are explicitly converted to utility.
• Costs and opportunity costs are included.
• Expected value is calculated for each option, not just the favored option.
• Sensitivity or break-even analysis is shown.
• Hard constraints and ruin risk are checked before recommending the highest expected value.
• The recommendation is one of: choose, mitigate, gather information, or reject.

Do NOT Use When