Study smarter with Fiveable
Get study guides, practice questions, and cheatsheets for all your subjects. Join 500,000+ students with a 96% pass rate.
Expected value is the mathematical backbone of every business decision made under uncertainty—and that's essentially every business decision. When you're calculating whether to launch a product, hire a contractor, or invest in a project, you're implicitly asking: "What's the average outcome if I played this scenario thousands of times?" This concept connects directly to probability distributions, decision analysis, risk assessment, and financial modeling—all core testable areas in your course.
Here's what the exam is really testing: Can you move beyond plugging numbers into formulas to actually interpret what expected values tell decision-makers? You'll need to recognize when to use discrete vs. continuous approaches, understand how linear transformations work, and evaluate whether gathering more information is worth the cost. Don't just memorize formulas—know what business problem each calculation solves and when to apply it.
Before applying expected value to business problems, you need to master the fundamental calculations. The type of random variable determines which mathematical approach you'll use.
Compare: Discrete vs. Continuous random variables—both use the same conceptual framework (outcome × probability), but discrete uses summation while continuous requires integration. Exam tip: If values are countable (customers, units, defects), use discrete; if measurable on a continuous scale (time, weight, dollars), think continuous.
The linearity property is your best friend for efficient calculations. Understanding these shortcuts prevents errors and saves time on exams.
Compare: Unconditional vs. Conditional expected value—unconditional uses all possible outcomes, while conditional restricts to a subset based on known information. FRQ angle: "Given that sales exceeded projections in Q1, what is the expected annual revenue?" requires conditional thinking.
This is where expected value becomes a decision-making tool. Business strategy often requires comparing expected outcomes across multiple options.
Compare: Decision trees vs. simple EMV calculations—both find expected values, but decision trees handle sequential decisions with multiple stages. If an exam problem involves "then" or "after observing," you likely need a decision tree structure.
These concepts address how uncertainty affects decisions and what we'd pay to reduce it. Information has quantifiable value when it improves decision-making.
Compare: EVPI vs. EVSI—EVPI assumes you'll know the outcome with certainty (theoretical maximum), while EVSI reflects realistic, imperfect information sources. Exam tip: If asked "should the company pay $50,000 for this market research," calculate EVSI and compare to the cost.
| Concept | Best Examples |
|---|---|
| Basic formula application | Discrete outcomes, simple probability distributions |
| Continuous variables | Time-based problems, revenue modeling, quality measurements |
| Linear transformations | Salary + commission, currency conversion, scaled variables |
| Decision trees | Multi-stage investment decisions, product launch timing |
| EMV calculations | Comparing business strategies, bid decisions, project selection |
| Risk preferences | Insurance pricing, investment choices, certainty equivalents |
| Information value (EVPI/EVSI) | Market research decisions, pilot study justification |
| Conditional expected value | Updated forecasts, segment-specific predictions |
A company can either launch Product A (60% chance of $500K profit, 40% chance of $100K loss) or Product B (certain $150K profit). Calculate the EMV of Product A and identify which option a risk-neutral manager would choose.
Compare and contrast EVPI and EVSI: Under what circumstances would they be equal, and why is EVSI typically lower?
If and you need to find , which property do you apply, and what's the result?
A decision tree has two chance nodes following an initial choice. Explain the "fold back" method and why you start calculations at the endpoints rather than the beginning.
Why might a risk-averse investor reject a project with positive EMV? Which concept—expected value or expected utility—better captures their decision-making process?