Most forecast meetings are status updates dressed up as inspections. The rep walks through their commit list. Numbers are confirmed. Heads nod. Forty-five minutes later, nothing has changed about anyone's actual understanding of where the quarter sits.
There is one question that breaks the pattern, asked at the same point in every forecast meeting, every week: What changed on this deal since last Tuesday?
Why the question works.
Change is the only thing that moves the slope. Pipeline that sits is pipeline that's stalling. A forecast that holds week-over-week without specific changes is forecast that's coasting on assumptions made eight weeks ago.
Change is also the hardest thing for a rep to articulate. It requires distinguishing real progress from activity. It requires admitting when a deal hasn't moved. It requires having paid attention.
Most reps, the first time they're asked, will say nothing major. That answer is the data. Nothing major on a deal that's been in commit for three weeks is a yellow flag. Nothing major twice in a row is a red one.
The three forms of change.
- Buyer signal. Something the buyer did, said, or escalated. A new stakeholder appeared. A timeline shifted. A question came in that wasn't there before. The buyer revealed something about budget cycle, procurement, or competing priorities. This is the highest-quality form of change — it tells you the deal is actually moving inside the buyer's organization.
- Seller action. Something the rep did. Multi-thread expanded. Pricing discussion advanced. Champion alignment validated. This change is in the rep's control and should happen in most cycles.
- Context. Something external. Market news. A competitive event. An organizational shift in the buyer's company that wasn't initiated by the rep but changes the deal's posture. Real but rarer.
A deal that produces no change in any of three categories for two weeks is not in commit. It is in hope.
The dashboard tells you what's there. The Tuesday question tells you what's moving. Most leaders run one and assume it answers the other.