Scenario planning and expected value at a glance
The expected value framework gives every possible result of an option a probability and a money value, then sums the products into one average. Its clearest worked use on the site comes in the guide on valuing leads by pipeline stage: multiply a deal's margin by the share of comparable leads that end up closing. The framework page is candid about where it falls short. Weak probabilities give a weak answer, a single average conceals the full spread of results the business might actually see, and the method fits a long run of small, similar bets far better than a single big one.
The scenario planning framework readies a plan for futures that cannot be forecast with any confidence. It selects the handful of outside forces that are truly uncertain and would reshape the plan the most, weaves them into a few named futures, translates each into the assumptions and budget case the plan uses, and settles beforehand the signpost that shows a future is arriving, the trigger at which the team acts and the response it will make. The page is explicit that scenarios are judgements rather than forecasts, and that what they buy is the chance to decide calmly before the season instead of in a hurry once it has started.
So the difference is not between a precise method and a rough one. Both rest on judgement. Expected value puts the judgement into probabilities and collapses the futures into one figure; scenario planning puts it into the choice of uncertainties and keeps the futures apart. The question that separates them is whether the decision is one the business will make many times, so that the average is what it will actually experience, or one it will live through only once.
Compare table
Scenario planning vs Expected value
| Row label | Scenario planning | Expected value |
|---|---|---|
| Question answered | What will we do if the world turns out this way, or that way? | Averaged across the ways it could turn out, what is each option worth? |
| What varies | The outside conditions that produce the numbers: demand, competition, costs, regulation | The outcomes of one choice: a lead closes or does not, a test wins or finds nothing |
| Role of probabilities | Kept deliberately rough; weighting the scenarios is a named mistake | Central: weak probabilities produce a weak answer |
| Inputs | Driving forces from the environmental scan, a few critical uncertainties, assumptions and a budget case for each future | Outcomes, a probability for each from the business's own history or a stated judgement, and a value in margin |
| Decisions it suits | One plan, one season or one large commitment facing a few big unknowns | Many similar, repeated choices: lead types, offers, bids, tests |
| Output | A few named futures, each with a signpost, a trigger and an agreed response | One value per option in money, with a range where the probabilities are uncertain |
| When the work is done | Before the plan is approved, then at each planning review | Whenever the choice is made, refreshed as outcomes arrive |
| What it prepares | The action to take when a signal appears | The ranking or the ceiling to apply now |
| How it misleads | The futures drawn can anchor the team, so a change outside all of them is noticed late | A judged figure set down as a percentage looks exact, and an average hides a worst case the business cannot absorb |
| Typical misuse | Scenarios with no trigger or response, or weighted scenarios with the plan built for the favourite | Valuing a single irreversible commitment by its average |
Most cases turn on two rows: the decisions each suits and the role of probabilities. If the same kind of choice comes round many times and the business has its own record of how often each outcome happens, the average is what it will actually get, and expected value is the cleaner tool. If the plan will meet one future and the probability of each future is a guess, scenario planning is the more honest tool, because it does not pretend to know the odds.
When to choose scenario planning
Choose scenario planning when a plan rests on a few outside conditions that would change it most and that nobody can forecast: whether demand holds, whether a rival opens or discounts, whether media costs jump, whether an announced regulation lands on time. The framework page draws these forces from the environmental scan, and the PESTEL framework supplies the wider list. Known patterns such as SeasonalityPredictable, repeating changes in demand tied to the calendar, such as months, holidays, weekdays or hours. are predetermined elements that every scenario shares, not uncertainties to plan around.
It is also the right tool when one outcome could do damage the business cannot absorb. The expected value page itself notes that one large commitment never gets the chance to average out, so its worst result needs weighing as carefully as its expected one. The one-way and two-way doors framework sorts choices by how hard they are to reverse: the less reversible the commitment, the more the worst future matters beside the average.
The value of scenario planning lies in the decisions made before the season, not in the document. Translate each future into the plan's assumptions and a budget case. The tutorial on building a marketing budget sets a lower and a higher case in columns beside the base and keeps a visible contingencyA reserve for the unplanned, held as its own visible budget line with written rules for releasing it, rather than padding spread across other lines., while the guide to marginal returns and forecasting helps judge how much extra spend a higher case can absorb before Diminishing ReturnsEach extra unit of spend or effort buys less extra result than the one before it. set in and each further unit of spend no longer pays its way. Then agree the signpost, the trigger and the response with whoever controls the money, so that the switch happens in days rather than after a fresh ReforecastA rebuild of the full-year view of the budget from actual spend and what marketing now knows, done at the points finance sets; not a fresh budget. weeks later.
Scenario planning is the weaker choice for decisions the business makes again and again. Building futures for every bid, offer or lead type is slow, and it throws away what the business's own history says about how often each outcome happens.
When to choose expected value
Expected value fits priced bets with a track record: what an enquiry is worth, the most a lead from each source may cost, which offer or test goes next. The odds usually come from a stage-to-close rate or a Win RateShare of closed sales opportunities that were won., and the value from Contribution MarginRevenue left after every cost that varies with each sale., not revenue, as the lead valuation guide explains; the CPA calculator converts the two into a cost-per-lead ceiling to test a target against.
It suits repeated decisions because, over enough leads or tests, the results settle near the average. The guide to prioritising tests includes it among the ways to score a backlog, rating it the truest way to frame what a test could be worth but noting that few teams have well-calibrated odds. The troubleshooting guide for a missed marketing forecast shows the other everyday use: a forecast built as spend times response times conversion rates times value per sale is a chain of expected values, so a miss can be traced back to the probability or the value that proved wrong.
Expected value is the weaker choice when the probabilities would have to be invented to make the arithmetic work, or when the business will live through a single result, not the average of many. A probability-weighted forecast of next season describes the average of several seasons, and that is not the one the business will have.
Decision table
| Situation | Choose | Why |
|---|---|---|
| Setting a cost ceiling for each lead source or enquiry type | Expected value | Close rates from the business's own history and margin per sale price each source |
| Ranking a test backlog or a set of offers | Expected value | Many repeated bets, whose results tend towards the average |
| Next year's plan depends on whether demand holds and whether a rival enters | Scenario planning | A few outside uncertainties with no honest probabilities |
| One large commitment whose worst outcome the business could not absorb | Scenario planning, with the worst case weighed | The business will live through one outcome, not the average |
| A budget request needs a lower and a higher case | Scenario planning | Each case is tied to the conditions that would trigger it |
| No history, and a choice that will be made many times | Expected value, with probabilities stated as ranges | The range shows whether the uncertainty changes the decision |
| A plan with both large unknowns and many routine bets | Both: scenarios for the plan, expected values inside each scenario | Each method answers the question it suits |
Pricing the repeated bets inside each scenario
Most plans need both methods. The season as a whole faces a few large unknowns; inside it, the team makes a great many small, repeated choices about bids, leads and offers. The clean arrangement is to build the scenarios for the plan and keep the expected values working inside each one. A scenario changes the inputs: in a weak-demand future the close rate or the order value may fall, so the value of an enquiry falls with it and the cost ceiling should follow. Write each scenario's assumptions as the inputs the expected values use, and the ceilings move when the trigger fires rather than when someone notices the cost per sale has drifted.
The arrangement fails in one direction: averaging the scenarios. Give each future a probability, multiply and add, and the plan is built for a blended season that matches none of the futures and prepares no response to any of them. The scenario planning page names over-weighting a favourite future as the way the single-forecast problem returns, and the average is the same problem in another form.
Two neighbouring choices are easy to mistake for this one. If the real question is the size of the budget rather than how to prepare for its uncertainty, see how top-down and bottom-up budgeting compare. Where options differ on qualities nobody can put a price on, such as fit, ease of use or support, the expected value and weighted scoring matrix comparison shows when scoring criteria works better. A business case for one investment can draw on both methods at once: the marketing business case tutorial asks for low, middle and high estimates built with the scenario discipline, and the marketing budget calculator checks that spend and expected outcome come from one plan.
A bicycle retailer values its bookings and prepares a season it cannot forecast
Snecklow Cycles, an invented bicycle retailer with two shops and an online store, reads its last 12 months of bookings. Of 400 bike-fit bookings, 120 led to a bike sale (30%), each leaving a contribution margin of £240, so a bike-fit booking is worth 0.30 × £240 = £72. Of 1,500 service bookings, 60 led to a bike sale (4%), worth 0.04 × £240 = £9.60, plus £18 of margin on the service itself, so £27.60. It keeps half of each value and sets cost-per-booking ceilings of £36 for fits and £13.80 for services in its search campaigns.
For the season ahead, the owner first does what the shop has always done: three sales forecasts of £520,000 if electric bike demand rises, £440,000 if it holds and £340,000 if a discount chain opens on the ring road, weighted 30%, 50% and 20%. The weighted figure is £444,000, and the media plan is set at 6% of it, £26,640. The plan fits none of the three: too much spend at full price if the chain opens, too little stock and staff if demand rises.
So the shop builds the three as scenarios instead. The signposts are electric bike pre-orders by mid-March compared with the same period a year earlier, and the council's decision on the chain's planning application. The responses are agreed with the owner's accountant in January. If pre-orders fall more than 15% or the application is approved, £4,000 moves from local print into search for fitting and servicing, a free first service comes with every bike, and the fit conversion rate is assumed to drop to 25%, which lowers the fit ceiling to £30. If pre-orders rise more than 15% and stock cover stays above 6 weeks, £5,000 of contingency is released into paid social. Otherwise the base plan runs.
In mid-March pre-orders are 22% below last year and the application is approved in April. The print money moves within a week, the free first service goes live, and the search campaigns run on the new ceiling of £30 per fit booking rather than the old £36.
Common mistakes
- Averaging the futures. A probability-weighted season prepares no response to any of the futures it blends.
- Probabilities with no source. Mark each as measured or judged, and give the judged ones a range.
- An average for a one-off commitment. A large choice that cannot be undone needs its worst result weighed beside its mean.
- Scenarios without triggers or responses. A story with no agreed action changes nothing when the signal arrives.
- Scenarios for routine choices. Bids, offers and lead types are priced from history, not from imagined futures.
- Fixed inputs inside changing futures. When a scenario changes close rates or order values, the expected values and ceilings built on them change with it.
- A best and worst case on one number. Shifting one revenue figure up and down tests sensitivity; it does not build scenarios.
The comparison library lists the other pairs that are easy to confuse.
