Why your sales team hates forecasting, and how to fix it
Sales teams resist forecasting for three specific reasons, and none of them is laziness. The number is used against them rather than for them, they are held to a figure that depends on a buyer's behaviour rather than their own, and the exercise returns nothing they can use. Fix those three and the compliance problem mostly dissolves.
1. The number is only ever used against them
In most organisations the forecast appears in exactly one context: a meeting where someone senior asks why it is not higher. A rep who learns that any number they give becomes a stick has two rational responses — give a low number and sandbag, or give a high one and deal with it later. Both wreck the forecast.
The fix is to give something back from the same data. Show a rep their own calibration: of the deals you called at 70%, this many closed. That is genuinely useful to a professional, it is about their judgement rather than their effort, and it is the first time most reps have seen the forecast produce something for them.
The question "is your 70% a real 70%" lands completely differently from "why is your number down". The first is a craft question. The second is an interrogation.
2. They are judged on something they do not control
A rep controls the meetings they take, the questions they ask, and how honestly they assess a deal. They do not control whether a buyer's budget survives a reorganisation. Holding someone to a close date that depends on another company's procurement cycle produces either anxiety or fiction, usually both.
The fix is to separate the two things you are asking for. Hold them to the quality of the call, which they control, and treat the outcome as information. A rep whose deals close at the rate they predicted is doing the job well, even in a bad quarter.
3. It costs them time and returns nothing
Updating twenty CRM fields on a Thursday night, to populate a dashboard nobody discusses with them, is pure overhead. It is not surprising it gets done badly.
The fix is to cut what you ask for and move when you ask for it. Five fields, filled in during the review while you talk through each deal, rather than twenty filled in alone beforehand. The data gets better because it is collected in conversation rather than from memory, and the overhead disappears because it happens inside a meeting that was happening anyway.
Three things that make it worse
- Public forecast-versus-actual leaderboards. They convert a measurement problem into a status problem, and the reliable outcome is conservative numbers from everyone.
- Asking "will it close?" in a group. The question has a socially correct answer. Ask what has to be true for it to close, and what would be the first sign it will not.
- Changing the method when the number disappoints. Everyone notices, and it teaches the team that the forecast is a negotiation rather than an estimate.
What changes when it works
The signal that you have got it right is small and specific: a rep lowers their own number before you ask. That only happens when lowering it is safe, which means it has stopped being a commitment and started being an estimate.
It is worth saying plainly to the team that this is the goal. Most reps have never worked anywhere the forecast was treated as a measurement rather than a promise, and they will not assume it unless told, repeatedly, and shown by what happens when the first person tries it.