Command Palette

Search for a command to run...

Blog

Scenario Planning Without Crystal Balls

The point of scenarios is not to predict the future. It is to prepare decisions that work across several futures.

Forecasts fail often. Scenario planning accepts this and asks a different question: which decisions hold up across a range of plausible futures?

How to build useful scenarios

Pick the two biggest uncertainties. For an exporter, perhaps the exchange rate and global demand. For a lender, interest rates and borrower defaults.

Build three or four coherent stories. Not "optimistic, base, pessimistic" on one variable, but combinations that hang together: strong demand with a strong rupee, weak demand with a weak rupee, and so on.

Test decisions, not numbers. For each scenario, ask whether the plan still works and what would need to change.

What it reveals

  • Decisions that are robust: good in every scenario.
  • Decisions that are bets: good in one, bad in others.
  • Early signals that tell you which scenario is unfolding.

Why it is underused

Scenarios feel less precise than forecasts. In fact they are more honest about what anyone can know. A board that has discussed four futures reacts faster when one arrives.

An example: a mid-sized exporter

Suppose an engineering exporter faces two big uncertainties: global demand in its main markets and the rupee–dollar rate. Combining them gives four scenarios. In strong demand with a weak rupee, it expands capacity confidently. In strong demand with a strong rupee, it grows but must protect margins through pricing and hedging. In weak demand with a weak rupee, it holds capacity and pushes into new markets where its prices are now competitive. In weak demand with a strong rupee, it cuts discretionary spending and protects cash.

Looking across all four, some decisions are robust: improving productivity and building a hedging policy help in every scenario. Others, such as a large capacity expansion, only pay off in one or two. The company can do the robust things now and prepare the bets, committing only when early signals point to the right scenario.

Choosing early signals

For each scenario, define two or three indicators that would show it is unfolding: order backlogs, currency forward rates, customer inventory levels. Review them monthly. The value of scenarios comes alive when a signal moves and the team already knows what it means.

Keep it light

Scenario work does not need a large team or months of effort. A half-day workshop and a two-page summary, revisited quarterly, is enough for most organisations.

A common mistake

The most common mistake is treating the middle scenario as the plan and the others as decoration. If the organisation does nothing differently because of the alternative scenarios, the exercise was a forecast in disguise. The test of good scenario work is that it changes at least one decision today, usually by making the plan more flexible.

The best plans are not the ones that predicted correctly. They are the ones that did not need to.

Command Palette

Search for a command to run...