Variance Analysis and Driver Trees
Moving from what changed to why it changed and what to do about it. Building a driver tree (price, volume, mix, and cost), producing a primary explanation plus alternative hypotheses, and adding the decision-quality layer that turns analysis into a recommendation. Includes when the model is likely to be confidently wrong just past the edge of its competence, and how a second hypothesis guards against it.
120 min
6
16
5
Learning Objectives
By the end of this chapter you should be able to:
- 1Decompose a revenue variance into a price effect and a volume effect, and read what each piece says about whether the movement is likely to persist.
- 2Build a driver tree that separates price, volume, and mix so a top-line movement traces to a specific cause rather than to a single lump sum.
- 3Design the decompose-then-explain workflow so a deterministic bridge holds the price-volume math and the model reasons only about cause.
- 4Guard driver analysis with the red-lines check for budget-versus-actual data, and keep the explanation inside the normal FP&A review chain.
- 5Validate a decomposition by confirming price and volume sum to the total variance and that each named driver matches its computed effect.
- 6Add a decision-quality layer of alternative, falsifiable hypotheses, applying the jagged-frontier lesson that a single confident story just past model competence is where errors hide.
- 7Frame a driver-based recommendation that leads with the cause, sizes it, and makes the remaining uncertainty explicit for the decision-maker.
Part One: From How Much to Why: Reading a Revenue Variance. Section 1 of 6.
Part One · From How Much to Why: Reading a Revenue Variance
From How Much to Why: Reading a Revenue Variance
Part One
From How Much to Why: Reading a Revenue Variance
The quarter closed ahead of plan on revenue, and the good news lasted about a minute. The CFO's next question is not how much you beat by; it is why, by product line, and whether it holds. This module builds the workflow that answers that question, and it starts with what a good answer looks like.
The favorable number that hides two stories
You are an FP&A analyst at Meridian Components, a mid-market industrial parts maker. The quarter beat the revenue plan by 850,000 dollars, and the bridge lands on your desk with a single favorable figure at the top. That number is true, and on its own it is close to useless. A revenue beat can come from charging more, from selling more, from shifting the sales mix toward higher-priced lines, or from some combination that partly cancels out. A decision-maker who hears only the net has no way to separate a durable pricing win from a one-time order that will not repeat.
This is a good candidate for an AI-assisted workflow because the hard part is reasoning about cause, not arithmetic. Splitting a revenue change into a price piece and a volume piece is a mechanical calculation with one right answer for a given set of units and prices. The judgment sits in what the split means: which driver is real, whether it persists, and what a second, competing explanation would be. That division, deterministic math on one side and cause-and-uncertainty reasoning on the other, is the design of the whole module.
What a good driver explanation looks like
Before pointing a tool at the bridge, define the finish line. A decision-quality driver explanation has four properties. It decomposes the movement, separating the price variance (the part explained by a change in selling price) from the volume variance (the part explained by a change in units) rather than reporting one lump sum. It sizes each piece, so the reader knows whether the story is mostly price or mostly volume. It grounds each named cause in something the data supports. And it carries a decision-quality layer: at least one alternative explanation for the same numbers, so the analysis does not rest on a single confident story.
The first two properties are arithmetic and belong in a bridge or template. The price variance holds volume fixed and asks what the price change alone did; the volume variance holds price fixed and asks what the unit change alone did. Under a consistent convention, the two pieces sum back to the total revenue movement, which is what makes the decomposition checkable. The last two properties, grounding and alternatives, are where an analyst's judgment earns its keep, and they are where the rest of this module concentrates.
Check Your Understanding
Knowledge Check 1
Variance Analysis
A product line sold 2,000 units at $50 each in the prior period and 2,300 units at $55 each in the current period. Using the convention that the volume variance holds price at the prior level, what is the volume variance?