Don't Panic — Spreadsheet Modeling and Scenario Analysis

A spreadsheet model is not a prettier table. It is a machine with three moving parts: assumptions you type, formulas that encode relationships, and outputs people argue about. Scenario analysis is what happens when you refuse to rebuild that machine every time someone asks "what if revenue is worse?"

Before interactive spreadsheets, changing an assumption meant erasing and rewriting dependent totals by hand. VisiCalc and its descendants made the grid recalculate for you. The habit stuck: keep drivers in cells, keep logic in formulas, then ask the grid to show alternate futures.

Everything else hangs off three tools and one boundary. Scenario Manager saves named sets of inputs (Worst, Base, Best) and flips them into the sheet — up to thirty-two changing values per case. Data Tables paint a sensitivity grid for one or two drivers across as many values as you list. Goal Seek works backward: you name the result you want and Excel hunts for the single input that gets there. Solver is the boundary. When several inputs must move under constraints, you have left everyday what-if and entered optimization.

The surprise is how often models look flexible and are not. A growth rate typed inside a formula is invisible to Scenario Manager. A data table pointed at the wrong input cell fills with identical numbers and looks authoritative anyway. A scenario summary is a snapshot; edit the cases and the old report will lie with perfect formatting. Payment formulas often return negative cash outflows, so a Goal Seek target with the wrong sign fails for a boring reason that still ruins an afternoon.

Google Sheets keeps the same modeling shape in a shared browser grid, but Goal Seek shows up as an Extensions add-on rather than Excel's built-in Data Tables suite. The questions transfer. The menus do not always.

Read the Intro when you need the architecture. Use the Cheatsheet when you are choosing among Scenarios, Data Tables, Goal Seek, and Solver. The Practice Reference and Exercise are where a loan model stops being abstract. Field Notes are where the operational bruises live: buried constants, stale summaries, and why inspection still beats confidence after the scenarios look polished.