The forecast that satisfies the board but surprises no one
Most forecasts are political documents, not predictive ones. They tell the board what it wants to hear, then get revised when reality disagrees.
The quarterly forecast lands in the board pack. The numbers look reasonable. The assumptions are documented. The pipeline coverage ratio is healthy. Everyone nods. The meeting moves on.
Six weeks later, the forecast is revised. Deals that were "90% likely" have slipped. The pipeline that looked healthy has not converted as expected. The assumptions that seemed reasonable have not held.
This is not a forecasting problem. It is a confidence problem. And the distinction matters.
The forecast as political document
In most organisations, the forecast serves multiple masters. It must satisfy the board's need for predictability. It must reflect sales leadership's optimism. It must account for marketing's pipeline contribution claims. It must not trigger difficult conversations about capacity, investment, or strategy.
The result is a document optimised for approval, not accuracy. The numbers are defensible. The methodology is consistent. The presentation is professional. But the forecast does not actually predict what will happen. It predicts what everyone can agree to put in writing.
This is why forecasts surprise no one when they are published, but surprise everyone when they are missed. The miss was always visible. It was simply not expressible within the political constraints of the forecasting process.
What decision-grade confidence actually requires
A forecast that enables decisions — rather than just satisfying governance requirements — needs three things that most forecasting processes lack.
First, it needs honest pipeline assessment. Not "what stage is this deal in?" but "what would need to be true for this deal to close on time, and how confident are we that those things are true?" Most pipeline reviews focus on activity and stage progression. Few focus on the actual conditions required for conversion.
Second, it needs explicit assumptions. Not buried in footnotes, but central to the conversation. What are we assuming about conversion rates? About deal velocity? About the mix of new versus expansion revenue? When assumptions are implicit, they cannot be challenged. When they cannot be challenged, they cannot be corrected until reality forces the correction.
Third, it needs early warning indicators. Not lagging metrics that confirm what has already happened, but leading signals that indicate whether the forecast is on track. If the forecast assumes 40% of pipeline will convert, what signals would tell us — in week three, not week ten — that conversion is tracking below that assumption?
The Control gap
When forecasts consistently miss, the instinct is to improve the forecasting process. Better templates. More rigorous pipeline reviews. Tighter definitions of stage criteria. More frequent check-ins.
These interventions address symptoms, not causes. The forecast is not wrong because the process is weak. The forecast is wrong because the underlying system — the commercial engine that generates pipeline and converts it to revenue — is not understood well enough to predict.
This is a Control problem. Not control in the sense of command, but control in the sense of understanding. Can leadership explain what is happening in the commercial system? Can they identify which inputs drive which outputs? Can they distinguish signal from noise in the data they receive?
Without this understanding, forecasting becomes extrapolation. We assume the future will resemble the past, adjusted for whatever growth rate feels defensible. When the future diverges from the past — as it always does — the forecast breaks.
Why more data does not help
The response to forecast misses is often to gather more data. More pipeline fields. More activity tracking. More dashboards. More reports.
But data volume is not the constraint. Most organisations have more data than they can interpret. The constraint is the ability to distinguish which data matters. Which signals are predictive and which are noise. Which metrics indicate future performance and which merely describe past activity.
Adding more data to a system that cannot interpret its existing data does not improve forecasting. It increases noise. It creates more opportunities for selective interpretation. It makes the political negotiation of the forecast more complex without making the forecast more accurate.
The upstream dependencies
Control — decision-grade confidence in revenue performance — cannot be fixed in isolation. It depends on the three forces upstream.
If Attention is broken — if the demand entering the system is inconsistent or misaligned — then conversion rates will be unpredictable. No amount of pipeline analysis will stabilise a forecast built on unstable input.
If Trust is broken — if buyers are hesitating for reasons the data cannot capture — then deals will stall in ways that stage progression does not reveal. The pipeline will look healthy while the conversion engine is failing.
If Movement is broken — if opportunities do not progress reliably from interest to decision — then pipeline stages become meaningless. A deal in "Negotiation" might be two weeks from close or two months from going quiet. The forecast cannot distinguish between them.
This is why forecasting accuracy is a lagging indicator of commercial health, not a leading one. Fix the upstream forces, and forecasting becomes easier. Try to fix forecasting without addressing the upstream forces, and you are optimising the measurement of a broken system.
What good looks like
A forecast with decision-grade confidence has a different character. It is not optimistic or pessimistic. It is not padded or sandbagged. It is honest about what is known and what is assumed.
Leadership can explain why the number is what it is. They can identify the three or four deals that will determine whether the quarter lands. They can articulate what would need to change for the forecast to be wrong — and they are watching for those changes.
The forecast does not satisfy the board by telling them what they want to hear. It satisfies the board by giving them what they actually need: enough confidence to make decisions, and enough honesty to make those decisions well.
The question
Does your forecast tell the board what will happen — or what everyone can agree to put in writing?
Part of the ATMC framework
This essay explores Control
Control is the fourth of four forces in the ATMC framework. It governs leadership's ability to make confident revenue decisions early enough to matter.
Learn more about Control →Related reading
Continue exploring
Movement
The pipeline velocity myth
Accelerating deals that were never going to close does not improve revenue. It accelerates failure.
Movement
The hidden cost of the 'quick win' pipeline
Deals that close fast feel like progress. But a pipeline optimised for quick wins often underperforms a pipeline built for reliable progression.
Attention
Why your best customers aren't who marketing thinks they are
The customers marketing targets and the customers who actually buy are often different populations. This mismatch is expensive.
