Webinar Recap: From What-If to What Next
Scenario Planning Done Right: What We Covered in Our Latest Webinar
Most finance teams can already run a sensitivity analysis. Drop revenue 5% and you know exactly what happens to margin. But that's not the hard part. The hard part is answering three questions: Which scenario are we actually moving toward? What signals will tell us it's happening? And what have we already agreed to do when it does?
That gap, between running a sensitivity analysis and running an actual scenario planning process, was the focus of our recent webinar. If you missed it, the recording is above. Here's the recap.
Why so few teams do this well
The data on this is worth sitting with. According to a 2026 AFP benchmarking survey of 332 finance and FP&A teams, only 38% use structured scenario planning. The organizations that do report meaningful gains: 13 to 14% improvements in strategic alignment, integration of external factors, and business alignment, plus budgets that close 11% faster. Perhaps the most striking number is that teams running scenarios year-round, rather than only during the annual budget cycle, report 51 to 66% higher effectiveness than those that don't.
So why isn't everyone doing it? Four obstacles come up again and again: speed (spreadsheet-based models that are out of date before they're reviewed), version control (no single source of truth for what's current), weak cross-functional alignment (finance building scenarios in isolation from the teams who actually see the business changing), and the resulting bind of either taking too long to build a scenario or building one fast that doesn't tell you anything useful. Either way, scenario planning becomes a bottleneck instead of a habit, and teams fall back on quick sensitivity checks instead.
That's a real cost, because the environment isn't getting calmer. New administrations, tariffs, shifting interest rates, and for public sector and nonprofit organizations in particular, sudden funding or grant cuts, mean most teams aren't dealing with just one disruption at a time. They're dealing with several at once.
Sensitivity analysis vs. structured scenario planning
The line between the two is clear once you see it. A sensitivity analysis adjusts one or two inputs, revenue, say, and shows you the resulting impact on EBITDA or margin. Useful, but shallow.
Structured scenario planning starts earlier and goes further. It begins with intent: what you want to happen, what you realistically expect, and what else could plausibly happen. It connects financial and operational drivers across functions, not just finance, but RevOps, HR, and the teams closest to the signal. And it doesn't stop at "what could happen." It answers "what would we do when it does." Crucially, it's never a one-time exercise. The scenarios get monitored and recalibrated on an ongoing basis, not set once and forgotten.
Four traits of scenario planning done right
Four practices separate the teams getting real value from scenario planning from the ones treating it as a once-a-year exercise:
A rolling cadence. The strongest plans aren't built once a year alongside the budget. They roll forward with the forecast, getting revisited and recalibrated continuously.
Driver-based, not line-by-line. Instead of adjusting every line item, the goal is to identify the handful of key drivers, labor cost, capacity, bookings, churn, that move the whole model.
Defined triggers. For each driver, teams pre-identify what in the business or the broader environment would push it up or down, so they're watching for signals rather than reacting after the fact.
Cross-functional ownership. HR, RevOps, and other business teams are part of building the scenarios, not just finance working alone.
The payoff is faster, more useful analysis: budgets and scenarios that are ready when you need them, instead of finished just in time to be out of date.
On how many scenarios to build, the guidance is simple: a base case plus two alternatives, a downside and an upside, is typically enough. More variations rarely add clarity. They mostly add build time.
Seeing it in action: a live model walkthrough
The webinar included a live demo in Workday Adaptive Planning, built around a straightforward business (think a generic manufacturer, though the same structure extends to other industries; in higher ed, for example, units becomes enrollment, price becomes tuition, and discount becomes financial aid). The model connects revenue (driven by units, price, and discount percentage) to COGS, a roster-based personnel plan, an OPEX model benchmarked against prior-year actuals, and a capital projects plan, in this case including a large planned expansion into Tokyo.
The scenario set was built around two indicators that tend to be historically predictive: unit volume and discount percentage. Rising discounts tend to mean the sales team is giving more away to close deals, an early sign of softening demand. Units falling off trend is a similar signal. On the flip side, rising unit demand suggests room to increase pricing, which is the basis for the upside case. Thresholds were set in advance: units down more than 7 to 8%, or discounts up more than 10%, as the signal that the business was trending toward its downside case.
To show how this plays out, the demo walked through a "2+11" forecast: two months of actual results (January and February) rolled into an 11-month forecast. The actuals showed discounts climbing and units falling, two consecutive revenue misses, putting the business squarely on the downside trajectory that had already been modeled and planned for.
Because the response had already been agreed upon, the team could act immediately: pushing new hire start dates out to protect cash without cancelling the hires, reallocating and trimming travel and expense spend for certain sales groups, and moving the Tokyo expansion project to pending status to delay the associated cash outlay (with minimal net income impact, since most of the cost was depreciation rather than immediate expense). The result: margin came back in line, cash was protected, and the impact to net income stayed contained, despite a real drop in units and rise in discounting. The point wasn't that the numbers moved. It was that the plan already knew what to change and could move on it immediately.
What our audience told us
Two live polls during the session backed up exactly what the data shows. When asked about the biggest obstacle to structured scenario planning, attendees most often pointed to the business not being sufficiently involved, and scenario planning not being part of the regular management cadence. When asked how their organization currently uses scenario planning, the most common answer was "primarily during the annual budget," rather than on a rolling, year-round basis. In other words, the gap in the data is the same gap most attendees see in their own organizations.
Four things to take back
Four practical takeaways close out the session, each tying directly back to the framework above:
Start with a decision. The purpose of a scenario is to improve a decision, not to produce another forecast.
Use a small set. A base case plus a downside and an upside creates more clarity than a long list of slight variations.
Add triggers and actions. A scenario without a response plan is just an alternative forecast.
Make it part of the rhythm. Revisit your scenarios during forecasts, business reviews, and strategic decisions, not just once a year.
Structured scenario planning isn't about predicting the future with precision. It's about preparing your organization to recognize change early and respond to it quickly. Start with one material decision, build a base case and two plausible alternatives, agree on the indicators that matter, and define, in advance, what your organization will do if those conditions emerge.
Watch the full recording above for the complete walkthrough, including the live model demo. Want help applying this framework to your own planning process? Contact us today!
Comments