expected-value
Calculates probability-weighted averages of all possible outcomes to enable rational decisions under uncertainty. Covers scenario identification, probability estimation, payoff quantification, and risk-adjusted interpretation. Use when comparing risky options (investments, product bets, strategic choices), prioritizing projects by expected return, assessing whether to take a gamble, or when user mentions expected value, EV calculation, risk-adjusted return, probability-weighted outcomes, or decision tree.
What this skill does
# Expected Value ## Table of Contents - [Workflow](#workflow) - [Common Patterns](#common-patterns) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) ## Core Formula **EV** = Σ (Probability of outcome x Value of outcome) ``` EV = (p₁ × v₁) + (p₂ × v₂) + ... + (pₙ × vₙ) where probabilities must sum to 1.0 ``` **Example**: Launch feature with 60% chance of $100k revenue, 40% chance of -$20k sunk cost. EV = (0.6 x $100k) + (0.4 x -$20k) = $60k - $8k = **$52k** (positive EV, rational to launch if risk tolerance allows) ## Workflow Copy this checklist and track your progress: ``` Expected Value Analysis Progress: - [ ] Step 1: Define decision and alternatives - [ ] Step 2: Identify possible outcomes - [ ] Step 3: Estimate probabilities - [ ] Step 4: Estimate payoffs (values) - [ ] Step 5: Calculate expected values - [ ] Step 6: Interpret and adjust for risk preferences ``` **Step 1: Define decision and alternatives** What decision are you making? What are the mutually exclusive options? See [resources/template.md](resources/template.md#decision-framing-template). **Step 2: Identify possible outcomes** For each alternative, what could happen? List scenarios from best case to worst case. See [resources/template.md](resources/template.md#outcome-identification-template). **Step 3: Estimate probabilities** What's the probability of each outcome? Use base rates, reference classes, expert judgment, data. See [resources/methodology.md](resources/methodology.md#1-probability-estimation-techniques). **Step 4: Estimate payoffs (values)** What's the value (gain or loss) of each outcome? Quantify in dollars, time, utility. See [resources/methodology.md](resources/methodology.md#2-payoff-quantification). **Step 5: Calculate expected values** Multiply probabilities by payoffs, sum across outcomes for each alternative. See [resources/template.md](resources/template.md#ev-calculation-template). **Step 6: Interpret and adjust for risk preferences** Choose option with highest EV? Or adjust for risk aversion, non-monetary factors, strategic value. See [resources/methodology.md](resources/methodology.md#4-risk-preferences-and-utility). Validate using [resources/evaluators/rubric_expected_value.json](resources/evaluators/rubric_expected_value.json). **Minimum standard**: Average score ≥ 3.5. ## Common Patterns **Pattern 1: Investment Decision (Discrete Outcomes)** - **Structure**: Go/no-go choice with 3-5 discrete scenarios (best, base, worst case) - **Use case**: Product launch, hire vs. not hire, accept investment offer, buy vs. lease - **Pros**: Simple, intuitive, easy to communicate (decision tree visualization) - **Cons**: Oversimplifies continuous distributions, binary framing may miss nuance - **Example**: Launch product feature (60% success $100k, 40% fail -$20k) → EV = $52k **Pattern 2: Portfolio Allocation (Multiple Options)** - **Structure**: Allocate budget across N projects, each with own EV and risk profile - **Use case**: Venture portfolio, R&D budget, marketing spend allocation, team capacity - **Pros**: Diversification reduces variance, can optimize for risk/return tradeoff - **Cons**: Requires estimates for many variables, correlations matter (not independent) - **Example**: Invest in 3 startups ($50k each), EVs = [$20k, $15k, -$10k]. Total EV = $25k. Diversified portfolio reduces risk vs. single $150k bet. **Pattern 3: Sequential Decision (Decision Tree)** - **Structure**: Series of decisions over time, outcomes of early decisions affect later options - **Use case**: Clinical trials (Phase I → II → III), staged investment, explore then exploit - **Pros**: Captures optionality (can stop if early results bad), fold-back induction finds optimal strategy - **Cons**: Tree grows exponentially, need probabilities for all branches - **Example**: Phase I drug trial (70% pass, $1M cost) → if pass, Phase II (50% pass, $5M) → if pass, Phase III (40% approve, $50M revenue). Calculate EV working backwards. **Pattern 4: Continuous Distribution (Monte Carlo)** - **Structure**: Outcomes are continuous (revenue could be $0-$1M), use probability distributions - **Use case**: Financial modeling, project timelines, resource planning, sensitivity analysis - **Pros**: Captures full uncertainty, avoids discrete scenario bias, provides confidence intervals - **Cons**: Requires distributional assumptions, computationally intensive, harder to communicate - **Example**: Revenue ~ Normal($500k, $100k std dev). Run 10,000 simulations → mean = $510k, 90% CI = [$350k, $670k]. **Pattern 5: Competitive Game (Payoff Matrix)** - **Structure**: Your outcome depends on competitor's choice, create payoff matrix - **Use case**: Pricing strategy, product launch timing, negotiation, auction bidding - **Pros**: Incorporates strategic interaction, finds Nash equilibrium - **Cons**: Requires estimating competitor's probabilities and payoffs, game-theoretic complexity - **Example**: Price high vs. low, competitor prices high vs. low → 2×2 matrix. Calculate EV for each strategy given beliefs about competitor. ## Guardrails 1. **Probabilities should sum to 1.0**: Listed outcomes need to be exhaustive (cover all possibilities) and mutually exclusive (no overlap). Verify: p1 + p2 + ... + pn = 1.0. 2. **Adjust for risk on one-shot, high-stakes decisions**: EV is a long-run average. For rare, irreversible decisions, factor in risk aversion. A 1% chance of $1B (EV = $10M) does not mean betting the house is rational. 3. **Quantify uncertainty, don't hide it**: Probabilities and payoffs are estimates. Use ranges, sensitivity analysis, or distributions rather than pretending false precision. 4. **Consider non-monetary value**: Some outcomes have utility not captured by money (reputation, learning, optionality, morale). Convert to a common scale or use multi-attribute utility. 5. **Ground probabilities in data**: Use base rates, reference classes, data, and expert forecasts rather than gut feel. Check calibration: are "70% confident" predictions right 70% of the time? 6. **Account for correlated outcomes**: If outcomes are not independent (e.g., economic downturn affects all portfolio companies), correlation reduces diversification benefit. 7. **Time value of money**: Discount future cash flows to present value. EV should use NPV, not nominal values. 8. **Consider option value**: In sequential decisions, fold-back induction finds optimal strategy. Factor in the option to stop early, pivot, or wait for more information. **Common pitfalls:** - ❌ **Ignoring risk aversion**: EV($100k, 50/50) = EV($50k, certain) but most prefer certain $50k. Use utility functions for risk-averse agents. - ❌ **Anchor on single scenario**: "Best case is $1M!" → but probability is 5%. Focus on EV, not cherry-picked scenarios. - ❌ **False precision**: "Probability = 67.3%" when you're guessing. Use ranges, express uncertainty. - ❌ **Sunk cost fallacy**: Past costs are sunk, don't include in forward-looking EV. Only future costs/benefits matter. - ❌ **Ignoring tail risk**: Low-probability, high-impact events (0.1% chance of -$10M) can dominate EV. Don't round to zero. - ❌ **Static analysis**: Assume you can't update beliefs or change course. Real decisions allow learning and pivoting. ## Quick Reference **Key formulas:** **Expected Value**: EV = Σ (pᵢ × vᵢ) where p = probability, v = value **Expected Utility** (for risk aversion): EU = Σ (pᵢ × U(vᵢ)) where U = utility function - Risk-neutral: U(x) = x (EV = EU) - Risk-averse: U(x) = √x or U(x) = log(x) (concave) - Risk-seeking: U(x) = x² (convex) **Net Present Value**: NPV = Σ (CF_t / (1+r)^t) where CF = cash flow, r = discount rate, t = time period **Variance** (risk measure): Var = Σ (pᵢ × (vᵢ - EV)²) **Standard Deviation**: σ = √Var **Coefficient of Variation** (risk/return ratio): CV = σ / EV (lower = better risk-adjusted return) **Breakeven probability**: p* where EV = 0. Solve: p* × v_success + (1-p*) × v_failure = 0.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.