Why Forecast Misses Are a Leadership Problem, Not a Forecasting One
- Jonathan Bouchier
- Jun 21
- 7 min read
Forecast misses are almost never caused by poor forecasting. They are caused by weak management disciplines upstream: in qualification, pipeline coverage, coaching, and deal progression. The forecast is a readout of how well those disciplines are being held. Fix the system, and the number takes care of itself.
When a forecast misses, the instinct is to fix the forecasting. That instinct is almost always wrong.
I have sat in too many quarter-end rooms where a capable, honest team rebuilt their model for the third time in a year, added another weighting, tightened another stage definition, and missed by the same margin they missed before. The spreadsheet was not the problem. The deals inside it were never as real as the column they sat in. You can sharpen a forecasting process until it gleams, and it will still produce a confident, precisely formatted untruth, because a forecast cannot be more honest than the management system feeding it.
That is the uncomfortable thing worth sitting with before you touch the model again.
The forecast is a readout, not the source of the problem
Most commercial leaders treat a forecast miss as a forecasting failure. It rarely is.
A forecast is a downstream output. By the time a number lands on the leadership report, it has already passed through how deals were qualified, how the pipeline was built, how managers coached their teams, and how honestly risks were surfaced and discussed. If those upstream disciplines are loose, the number will be loose too, no matter how carefully the final column was assembled.
This reframe matters, because the talent framing sends leaders looking in the wrong direction. They hire a sharper ops lead, buy a better tool, or lean on the rep who always calls it right. But accuracy is not a gift some people have and others lack. A forecast inherits every weakness in the management disciplines that feed it. Fix those disciplines, and ordinary people produce accurate numbers. Leave them broken, and your best person still produces a confident miss.
The miss is not the disease. It is the symptom. And the disease almost always lives upstream.
What is the "what must be true" test?
The most practical tool for rebuilding forecast integrity is deceptively simple: for every deal in the commit column, ask what must be demonstrably true for it to close on that date, and refuse to count the deal until the evidence exists.
Not what the rep hopes is true. Not what the buyer implied on a good call. What must actually be in place, and what evidence have you seen of it.
Take a deal sitting in commit for the 28th. For that to close, the buyer must have agreed the problem is worth solving now. The economic decision-maker must have been in the room. The procurement and legal path must be mapped. The budget must exist in this period, not the next one. And there must be a reason that date matters to the buyer, not only to you. Walk a typical forecast through those questions out loud, and the column thins quickly. The deals that survive are the ones you can stand behind. The ones that fall out were never a forecast entry. They were a wish wearing a date.
A CRO I worked with started applying this test to every deal above a threshold, every Friday. The first month, the committed number dropped by a third and the board flinched. By the end of the quarter, the forecast landed inside two per cent, the first time in two years it had landed at all. Nothing about the forecasting process changed. The honesty about the foundation did.
Qualification and pipeline coverage are where forecast accuracy is decided
If the "what must be true" test exposes the gap at deal level, qualification discipline and pipeline coverage are where that gap is either built or avoided in the first place.
Qualification determines whether the deals entering your pipeline are genuinely winnable or simply optimistically logged. When qualification standards are loose, when deals are entered at the most optimistic moment and never seriously tested again, the forecast is inflated before anyone has touched a spreadsheet. The miss was built in weeks earlier. We explore this in more depth in our post on why qualification fails when you treat it as a gate rather than a continuous discipline.
Pipeline coverage compounds the problem or protects against it. Most teams default to a flat three-times multiple and treat it as a law of physics. It is not. The right coverage formula is quota divided by win rate divided by cycles per year. A team winning one deal in three with a long cycle needs a very different cushion from one winning one in two and turning deals over quickly. Use the blunt multiple and you will systematically over-cover in easier quarters and run dangerously light when it matters. We cover the maths and the method in our post on why the 3x pipeline rule quietly breaks forecasts.
Get qualification and coverage right, and the forecast almost builds itself. Get them wrong, and no weighting model will save you.
Why optimism keeps finding its way back in
Even when leaders understand the problem, optimism tends to re-enter the system. Not through dishonesty, but through structure.
Sales careers reward optimism. The rep who keeps believing, keeps working, keeps showing up: that resilience is genuinely valuable in the act of selling. The trouble is that the same instinct that wins deals corrupts forecasts. The quality that makes someone effective at chasing an opportunity makes them poorly suited to calling it objectively. Optimism is not a flaw to be coached out. It is a working trait that has to be deliberately separated from the forecast, by evidence, every time, or it leaks straight back in.
The structural problem sits with leadership behaviour. If the forecast meeting rewards the big confident commit and penalises the cautious, evidenced one, you have trained your people to inflate. Every rep in the room learns what the organisation actually pays for, and it is not the truth.
The fix is not a reminder about honesty. It is to visibly back the rep who downgraded a deal on real evidence, and to treat a clean miss caused by a genuine buyer change very differently from a miss caused by a deal that was never qualified. When honesty is the safe choice rather than the brave one, the forecast straightens out. Until then, you are asking people to be truthful inside a system that quietly fines them for it.
Coaching is where forecast accuracy is actually built
Forecasting accuracy is not manufactured in a forecast meeting. It is built in the coaching conversations that happen in the weeks before it.
One important distinction is worth naming here: interrogating a deal in a forecast meeting is not the same as coaching the person who owns it. The first is inspection. The second is development. Confusing the two costs you both. You lose pipeline truth and you lose the capability building that prevents the same mistakes recurring. We examine this distinction in detail in our post on why deal reviews and coaching are not the same thing.
The best coaching conversations are where the "what must be true" test stops being a slogan and becomes a habit, one deal at a time, one manager at a time.
Forecast accuracy sits at the end of a management system
This is the reframe I most want a commercial leader to hold onto. The Forecasting and Reporting discipline does not sit independently. It is the readout of everything upstream of it: qualification rigour, pipeline coverage, coaching quality, deal progression honesty, and the standards a manager holds in every review.
When you treat a missed forecast as a forecasting failure, you are treating the smoke and ignoring the fire. The leadership move is to resist the urge to re-engineer the model and instead ask what the miss is telling you about the disciplines feeding it. The number is honest about your management system, even when the system is not being honest with itself.
For leaders who want to see how these disciplines connect, our post on the Sales Management Puzzle sets out how qualification, pipeline management, coaching, and forecasting function as an integrated system rather than separate activities.
Stop interrogating the forecast. Start interrogating the system behind it.
The next time the forecast misses, do not open the model. Open the pipeline. Run the "what must be true" test on the deals that slipped. Ask whether your coverage was built on a real win-rate calculation or a comfortable multiple. Look hard at whether your own reactions in the forecast meeting reward truth or punish it.
The forecast is a mirror. If you do not like what it shows, the work is behind the glass, not on it. That work, rebuilding accuracy from qualification and coverage upward rather than from the spreadsheet down, is exactly the work we do. Get in touch to see how we approach it.
Common Questions
Why are my sales forecasts always wrong?
Usually because the pipeline and qualification beneath them are weak, so the forecast is wrong before anyone forecasts. Fix the inputs, and the number straightens out without changing the model.
Is forecasting a talent problem?
Rarely. Talent cannot make an unqualified pipeline accurate; foundations do that. A disciplined ordinary team will out-forecast a brilliant team working from a wishful pipeline.
What is the "what must be true" test?
Asking what evidence must exist for a deal to close on its date, and not counting it until that evidence is real. It thins the forecast fast and leaves only deals you can stand behind.
How do qualification and coverage affect forecasts?
A forecast is qualification and coverage expressed as a number, so weak inputs produce a weak forecast. Generous qualification inflates it and thin coverage makes it fragile.
How do I get a more honest forecast?
Make it safe to commit a smaller, evidenced number, and coach the evidence rather than reward the optimism. When honesty is the safe choice rather than the brave one, accuracy follows.
