← ccPlanning Academy

Forecast value add (FVA)

Free visual lesson · about 5 minutes · short quiz at the end

ccPlanning academy · forecasting

Forecast value add

The humbling question that closes the loop: is your work actually helping?

The big idea

Is your forecast better than doing nothing?

Forecast value add measures whether each step of effort — the model, the manual override, the analyst’s tweak — actually improves accuracy versus a simple naive baseline. Sometimes the honest answer is no.

The benchmark

Naive is the line in the sand.

“This week equals last like-week” costs nothing and takes no skill. So it’s the perfect benchmark: any model, any adjustment, has to beat it on accuracy to justify its existence.

How to read it

Compare accuracy at each step.

Score the naive forecast, the statistical forecast, and the final human-adjusted forecast on the same period. Positive FVA at a step means it added value. Negative FVA means that step made the forecast worse.

naivemodel+ override override hurt it

The uncomfortable finding

Manual overrides often destroy value.

Study after study finds that well-meaning human tweaks frequently make a good statistical forecast worse — gut-feel adjustments, “it feels low,” padding for safety. FVA exposes this, gently and with data, instead of by blame.

Why it’s powerful

It turns “trust me” into evidence.

FVA lets you retire effort that doesn’t pay — stop running a model that loses to naive, stop an override step that adds nothing — and defend the steps that genuinely help. It’s how a planning function proves its own worth.

How to start

You can run it this quarter

Pick one metric (WAPE or bias), one period, and score three versions on the same actuals: naive, your statistical forecast, your final human-adjusted forecast.

Two columns of difference is all it takes to see where value is added — and where a step is quietly making things worse. No new tooling required.

The takeaway

Beat naive, or stop doing it.

Benchmark every step against the free, skill-free forecast. Keep what adds value, cut what doesn’t, and let evidence — not seniority or habit — decide. That’s the loop that turns forecasting from craft into discipline.

That’s the track — now test yourself ↓

1 / 7

Slides done? Here’s the same idea in a bit more depth — the part worth keeping.

In depth: the question that closes the loop

Every other forecasting lesson is about making the forecast better. Forecast value add asks the harder, more honest question: is all that effort actually helping? It measures whether each step you take — the statistical model, the analyst’s adjustment, the manual override — genuinely improves accuracy against a baseline that costs nothing. Sometimes the answer is uncomfortable, and that’s exactly why it’s valuable: it turns “trust me, the model helps” into evidence one way or the other.

Naive is the line in the sand

The benchmark is the simplest forecast imaginable — “this week equals the same week last cycle.” It takes no skill, no model and no time, which is precisely what makes it the right yardstick. Any model, any human tweak, has to beat that free baseline on accuracy to justify its existence. You score the naive forecast, the statistical forecast and the final adjusted forecast over the same period, and the differences tell you where value was added. A positive step earned its keep; a negative step made the forecast worse.

The finding that stings — and why it helps

Study after study finds the same thing: well-meaning manual overrides often destroy value. Gut-feel nudges, “it feels a bit low,” quiet padding for safety — these frequently take a good statistical forecast and degrade it. FVA surfaces that gently, with data rather than blame, and that’s its real power. It lets a planning team retire the effort that doesn’t pay — switch off a model that loses to naive, drop an override step that adds nothing — and confidently defend the steps that genuinely help. It’s how forecasting stops being craft defended by seniority and becomes a discipline defended by evidence.

The principle to remember: benchmark every step against the free, skill-free forecast. Keep what beats naive, cut what doesn’t, and let evidence — not habit or hierarchy — decide.

Quick quiz

Five questions. Pick an answer to each, then check your score.

1. What does forecast value add measure?

FVA checks whether the model, the override, the tweak actually beat doing the simple naive thing.

2. Why is naive the benchmark?

Naive is free and skill-free — the perfect bar for everything else to clear.

3. What does negative FVA at a step mean?

Negative FVA = that step (often a manual override) reduced accuracy versus the step before it.

4. What does FVA frequently reveal about manual overrides?

Gut-feel adjustments and safety padding often destroy value — FVA shows it with data, not blame.

5. What’s the discipline FVA gives a planning team?

FVA turns “trust me” into evidence — retire effort that doesn’t pay, defend what does.