datarekha

Sensitivity Analysis

Your spreadsheet says profit is $800,000 — but it rests on five guesses. Sensitivity analysis tells you which guess, if wrong, would hurt the most.

7 min read Intermediate Business Analytics Lesson 15 of 21

What you'll learn

  • What sensitivity analysis is and why every business model needs it
  • How to build a tornado chart and read it instantly
  • Why fixed costs barely moved the profit number — and price moved it the most
  • The difference between sensitivity analysis and scenario analysis
  • How to prioritise your research effort using the tornado

Before you start

Every business plan is a chain of assumptions. Price will hold. Customers will show up. Costs will stay under control. The spreadsheet confidently prints a single answer — $800,000 profit — but that number is only as trustworthy as its weakest assumption. Sensitivity analysis (changing one input at a time to see how much the output moves) tells you exactly which assumption is the weak link. Once you know that, you know where to spend your research budget — and where it is safe to make a quick guess.

The model we will stress-test

We will use a stripped-down profit formula throughout this lesson:

Profit = (Price − Unit Cost) × Volume − Fixed Costs

Base case — the numbers the team agreed on:

AssumptionBase value
Price per unit$50
Unit cost per unit$30
Volume (units sold)100,000
Fixed costs$1,200,000

Plugging in:

Profit = ($50 − $30) × 100,000 − $1,200,000
       = $20 × 100,000 − $1,200,000
       = $2,000,000 − $1,200,000
       = $800,000

Good. The base case is $800,000. Now the real question: which assumption, if wrong, wipes out that profit?

Varying one assumption at a time

The core mechanic of sensitivity analysis is simple: hold every assumption at its base value, nudge just one up and down over a plausible range, record what happens to profit, then move on to the next assumption. Repeat for every input. The result is a table of swings — how far profit can move if that single assumption is off.

Price ±10 %

Price is often the assumption the team feels most confident about — and most often wrong about. A 10 % range ($45 to $55) is realistic given competitive pressure or discounting.

At $45:  ($45 − $30) × 100,000 − $1,200,000 = $1,500,000 − $1,200,000 = $300,000
At $55:  ($55 − $30) × 100,000 − $1,200,000 = $2,500,000 − $1,200,000 = $1,300,000
Swing:   $300,000 to $1,300,000  →  ±$500,000 from base

A 10 % price miss cuts or adds half a million dollars. That is the biggest swing of any assumption.

Volume ±20 %

Volume (the number of units customers actually buy) is notoriously uncertain for new products. A ±20 % range is conservative.

At 80,000:   $20 × 80,000  − $1,200,000 = $1,600,000 − $1,200,000 = $400,000
At 120,000:  $20 × 120,000 − $1,200,000 = $2,400,000 − $1,200,000 = $1,200,000
Swing:   $400,000 to $1,200,000  →  ±$400,000 from base

Unit cost ±10 %

Unit cost (the variable cost to produce or deliver each unit — materials, labour, fulfilment) moves with supplier prices and operational efficiency.

At $33:  ($50 − $33) × 100,000 − $1,200,000 = $1,700,000 − $1,200,000 = $500,000
At $27:  ($50 − $27) × 100,000 − $1,200,000 = $2,300,000 − $1,200,000 = $1,100,000
Swing:   $500,000 to $1,100,000  →  ±$300,000 from base

Fixed costs ±10 %

Fixed costs (rent, salaries, insurance — the bills you pay regardless of volume) feel like the big scary number at $1.2 M. But watch what happens when they shift.

At $1,320,000:  $2,000,000 − $1,320,000 = $680,000
At $1,080,000:  $2,000,000 − $1,080,000 = $920,000
Swing:   $680,000 to $920,000  →  ±$120,000 from base

The largest cost line in the model produces the smallest swing. Why? Because a 10 % change on $1.2 M is only $120,000 — and fixed costs have no leverage with volume. Price, by contrast, multiplies across every single unit.

The tornado chart

A tornado chart is a horizontal bar chart where each bar represents one assumption’s full swing around the base case, sorted widest-on-top and narrowest-on-bottom. The sorted shape (wide at the top, narrow at the bottom) is why it is called a tornado. The top bars are where to spend your diligence.

Profit Sensitivity — Tornado ChartBase-case profit $800,000 · Each bar holds all other assumptions constant−$500k−$300k−$120k$800k (base)+$300k+$500k−$500k+$500kPrice ±10% ($45−$55)−$400k+$400kVolume ±20% (80k−$120k units)−$300k+$300kUnit Cost ±10% ($27−$33)−$120k+$120kFixed Costs ±10% ($1.08M−$1.32M)$800,000Downside (low assumption)Upside (high assumption)

Tornado chart: each bar shows the profit range when that assumption moves over its plausible range. Sorted widest-to-narrowest. Base profit = $800,000 (center line).

The takeaway is stark: price drives five times more swing than fixed costs — even though fixed costs look like the big scary number. If you spend a month negotiating a lease to save 10 % on fixed costs, you save $120,000 in expected profit uncertainty. If you spend the same month stress-testing your pricing strategy, you protect $500,000.

What the tornado tells you to do

Reading the chart top-to-bottom gives a direct prioritisation list:

  1. Price — nail down your pricing power. Talk to customers. Run pricing experiments. Understand competitor moves. This is where bad assumptions kill plans.
  2. Volume — validate demand. A pilot, a waitlist, a small test market. Getting ±20 % tighter on volume is worth more than any other data-gathering effort.
  3. Unit cost — get supplier quotes locked in. Understand your variable cost drivers.
  4. Fixed costs — yes, model them, but once they are known (signed lease, headcount plan) they barely move the needle. Don’t over-invest here.

This is the payoff of the analysis: don’t research every assumption equally. The tornado tells you the few inputs that actually move the decision, so you concentrate time and money where it changes the answer.

From sensitivity to scenario analysis

Sensitivity analysis is a one-at-a-time tool. That is its strength for ranking — and its limitation for realism.

Scenario analysis (also called what-if analysis) is the practice of varying several assumptions together into coherent stories: a best case (high price, high volume, low cost), a base case, and a worst case (low price, low volume, high cost). Because in reality assumptions move together — a price war usually comes with volume pressure at the same time — scenarios are more realistic than single-variable swings.

Use both: tornado to rank priorities, scenarios to stress-test the full picture.

Summary

Sensitivity analysis is a one-variable-at-a-time diagnostic that turns a single-point forecast into a ranked priority list. The tornado chart makes the ranking visual and immediate. In our model, a 10 % price miss creates a $500,000 swing; a 10 % fixed-cost miss creates only a $120,000 swing. That gap tells every business analyst exactly where to spend their next week.

Next

Monte Carlo simulation — instead of nudging one variable at a time, Monte Carlo varies all assumptions simultaneously, thousands of times, drawing from probability distributions for each. The result is a full distribution of outcomes: not just “profit could be $300k or $1.3M” but “there is a 12 % chance profit is negative.” It is sensitivity analysis grown up.

Quick check

0/3
Q1In the model above, why does a 10% change in price produce a larger profit swing than a 10% change in fixed costs?
Q2A startup's tornado chart shows: Customer Acquisition Cost (±$200k swing), Monthly Active Users (±$180k swing), Server Cost (±$40k swing), Office Rent (±$15k swing). The founder wants to spend the next sprint negotiating the office lease down. Based on sensitivity analysis, what should she do instead?
Q3You run a sensitivity analysis and find that profit barely changes when you vary fixed costs. A colleague says: 'Great — we can assume fixed costs won't be a problem.' What is wrong with that conclusion?

Practice this in an interview

All questions
How do you choose the classification threshold for a model when the goal is a business outcome, not pure accuracy?

The default 0.5 threshold optimises for balanced accuracy but is rarely the right choice for business objectives. The correct threshold is found by translating the business cost of false positives and false negatives into a cost matrix, then sweeping the threshold on a held-out set to find the point that minimises expected cost or maximises expected profit. Operational constraints — such as review-team capacity — further bound the feasible region.

How do you calculate sample size, statistical power, and minimum detectable effect for an A/B test?

Sample size, power, and MDE form a three-way trade-off: fix any two and the third is determined. You choose the MDE based on business materiality, then solve for the sample size that delivers 80–90 % power at alpha = 0.05.

When should you optimize precision and when should you optimize recall?

Optimize precision when a false positive is costly — spam filters, ad targeting, legal evidence — because you'd rather miss some positives than act on wrong ones. Optimize recall when a false negative is costly — cancer screening, fraud detection, safety systems — because missing a true positive can be catastrophic. The business cost of each error type should drive the choice, not the metric itself.

Tell me about a time a model or analysis you built failed or underperformed.

Interviewers ask this to test intellectual honesty, ownership, and how you learn from setbacks — not to embarrass you. The strongest answers name a real failure, explain the root cause clearly, describe what you did to fix or contain the damage, and articulate the lasting lesson you carried forward.

Sign in to track your progress

Completed lessons, your XP, level, and streak save to your account — it's free and takes a few seconds.

Explore further

Related lessons

Skip to content