Stop Building One Forecast. Start Building Three.

There's a quiet act of false confidence at the heart of most financial planning. A team spends weeks building a single forecast—a precise set of numbers for revenue, margin, and cash over the coming year—and presents it as the plan. Everyone nods. And then reality, which never consulted the spreadsheet, does something else entirely, and the plan becomes a document people stop referencing by March.

The problem isn't that the forecast was wrong. All forecasts are wrong. The problem is building only one of them, which forces you to pretend you know which future is coming when you don't.

A single number hides the thing that matters

When you present one forecast, you've collapsed a range of possibilities into a point estimate, and in doing so you've hidden the most decision-relevant information: how much the outcome could vary and what drives the variation. A forecast that says "revenue will be $48M" tells leadership nothing about whether the realistic range is $46–50M or $38–58M. Those are wildly different businesses to manage, and the single number conceals which one you're in.

Worse, the single forecast invites a false debate. Stakeholders argue about whether the number is "right"—too aggressive, too conservative—when the honest answer is that no single number is right. The argument is unwinnable because it's the wrong argument.

Three scenarios reframe the conversation

Building three forecasts—a base case, a downside, and an upside—changes what the planning conversation is about. Instead of "is this number right," the question becomes "what would have to be true for each of these, and what would we do in each?" That's a far more useful discussion, and it produces a plan that survives contact with reality.

The base case is your honest best estimate—what you actually expect if things go roughly as planned. The downside isn't a worst-case catastrophe; it's a credible bad outcome—the large customer softens, the cost input spikes, the new product slips. The upside is a credible good outcome. The discipline is making each one plausible and specific, tied to identifiable drivers, not just the base case multiplied by 0.9 and 1.1.

The real payoff: pre-deciding your responses

The strategic value isn't in the numbers themselves. It's in what you do before you know which scenario is unfolding. For each scenario, you decide in advance what you'd do: in the downside, which costs get cut, which capex gets deferred, which covenant comes under pressure and what you'd do about it; in the upside, where you'd invest the surplus. You've turned the forecast from a prediction into a set of pre-loaded decisions.

This matters enormously when the moment arrives, because decisions made calmly in advance are far better than decisions made under pressure in real time. The team that scenario-planned the downside doesn't panic when revenue softens—they execute the plan they already built. The team with one forecast scrambles.

Build it on shared drivers so it stays maintainable

The mechanical trap with multi-scenario planning is that you end up maintaining three separate models that drift apart. The fix is building one model on explicit drivers, where the scenarios are just different driver assumptions feeding the same engine. Change the customer-volume assumption, the cost-input assumption, the timing assumption—and all three scenarios recompute from the same logic.

This is also what makes the model answer questions in real time. When the board asks "what if our biggest customer cuts volume 20%," you don't build a fourth model—you flex the driver and watch all the outputs move. The scenario framework and the driver-based structure reinforce each other.

What to actually present

Don't bury leadership in three full forecasts—that's overwhelming and obscures the point. Present the base case as the working plan, the range the three scenarios define, the handful of drivers that move you between them, and the pre-decided responses for the downside and upside. That's a plan leadership can actually use: it tells them what you expect, how wrong it could be, what would cause that, and what you'll do about it.

A single forecast is a forecast you'll abandon in a quarter. Three scenarios with pre-loaded responses is a plan for whatever the year actually delivers. Stop predicting the future and start preparing for it.