What you get
- A driver-based model built on the few assumptions that really matter.
- Best-case, base-case, and worst-case scenarios side by side.
- Sensitivity analysis showing which inputs move the result most.
- Simulations that show the range of possible outcomes and how likely each is.
- A clean input panel that non-technical users can change safely.
Modern scenario modeling techniques
Driver-based modeling
A good model separates inputs, calculations, and outputs. Every number traces back to a clearly labeled assumption, such as price, volume, churn rate, or hiring date, so anyone can see why the answer is what it is.
Excel's built-in what-if tools
Scenario Manager stores named sets of assumptions. Data Tables calculate a result across a whole grid of inputs at once. Goal Seek works backward from a target, such as the sales volume needed to break even, and Solver finds the best answer under constraints, like the most profitable product mix with limited capacity.
Sensitivity analysis and tornado charts
Changing each assumption up and down, one at a time, shows which inputs your plan is most exposed to. A tornado chart ranks them visually, so you know where better information or a contingency plan is worth the effort.
Monte Carlo simulation
Instead of one guess per input, Monte Carlo simulation uses a realistic range and runs the model thousands of times. The result is a statement like "there's about a 70% chance we stay above break-even," which is far more useful than a single number. I build simulations in Excel with RANDARRAY and dynamic arrays, or in Python with NumPy for larger models, including inputs that move together.
Interactive scenario dashboards
Sliders on a web page or what-if parameters in Power BI let leadership explore scenarios live in a meeting, rather than waiting for a new version of the spreadsheet.
Tools and technologies
- Scenario Manager
- Data Tables
- Goal Seek
- Solver
- LET and LAMBDA
- RANDARRAY
- Python
- NumPy
- SciPy
- Power BI
- Tornado charts
Common questions
What's the difference between scenario analysis and sensitivity analysis?
Scenario analysis changes several assumptions together to tell a complete story, like a recession case. Sensitivity analysis changes one input at a time to see how much it matters on its own. Good models use both.
Is Monte Carlo simulation overkill for a small business?
Not if a decision is big and the inputs are uncertain. It can run in an ordinary Excel workbook, and it answers the question owners actually ask: how likely is this to work?
Can you build a scenario model my team can use in Excel?
Yes. Most of the scenario models I build live in Excel, with a protected input panel, clear labels, and notes explaining each assumption.