Explain a forecast miss in three moves: decompose the gap into drivers, name the mechanism that broke the forecast, and state what changes in the model. Boards handle misses. What they do not handle is a shortfall presented without a cause, because a miss with no identified mechanism is a miss that will happen again next period.
Decompose before you narrate
Lead with arithmetic. Revenue is deals multiplied by deal size, so the first split separates volume from value, and timing separates permanent loss from delay.
- Closed deal count against plan. - Average closed deal size against plan. - Win rate against plan, cut by segment. - Value that slipped into the next period rather than disappearing.
That decomposition changes the conversation from whether the team worked hard enough to which specific input moved. A shortfall driven by deal size is a pricing problem. A shortfall driven by count is a pipeline problem. They look identical at the total line and require opposite responses.
Name the mechanism, not the symptom
ORM's position on why forecasts fail is that the business or the market changed and the forecast was still running on old assumptions. A model that does not respond to changing conditions will miss regardless of how carefully it was built.
The changes are concrete and worth naming directly.
- A new competitor enters and creates pricing pressure, so average deal size falls. - Interest rates rise, private equity slows capital deployment, portfolio companies cut cost, and win rates drop. - Market uncertainty slows decisions, so the path from qualified to closed lengthens. - Territories get redrawn and reps are distracted, so execution suffers while coverage still looks fine.
Seasonality gets blamed less often than it should be. ORM's view is that Q2 and Q4 typically run stronger than Q1 and Q3, with the third month of a quarter stronger than the first two. A plan phased in equal quarters manufactures a Q1 shortfall that gets reported as an execution failure.
"Sales did not execute" is a symptom. It describes the outcome of a mechanism nobody identified.
Say what changes in the model
Close with the correction. If deal slippage drove the gap, the fix is watching the signal that predicts it. ORM's strongest slippage signal is a rep changing the close date, and a deal that slips from one period to the next is less likely to close even when it sits in commit. The earliest signal is the absence of any signal at all, meaning no stage change, no amount change, and no activity.
Then commit to measuring forecast accuracy as a standing metric, so the next report shows whether the correction worked. The forecasting approach that supports that is covered in how to forecast revenue.
Frequently Asked Questions
What should you say first when reporting a miss?
The size of the gap and its decomposition, before any narrative. Directors want to know whether the shortfall came from fewer deals, smaller deals, a lower win rate, or timing, because each points to a different fix. Opening with context and reaching the number on slide four reads as management by evasion, and it costs more credibility than the miss itself.
How do you explain a miss when coverage looked healthy?
By showing what the coverage number was hiding. Coverage can hold at 4x while the pipeline is aged, concentrated in a few large deals, sitting in a low-converting segment, or carrying deal values above what deals actually close for. The honest version says coverage was treated as an answer when it was only an input, and shows the composition figures the team should have been watching.
Should you revise the annual plan after a miss?
Only if an assumption underneath the plan broke rather than execution falling short. A pricing shift that resets deal sizes or a segment that stopped converting justifies a revision. A single quarter of poor execution does not. When the plan is revised, keep the original in the reporting so the board can measure against the baseline it approved.
How do you rebuild board confidence after a miss?
By forecasting the next period accurately, including forecasting bad news early. A team that calls a shortfall in week three of a quarter earns more trust than one that delivers a surprise in week twelve. Reporting forecast accuracy as a standing metric turns that from a claim into evidence the board can verify each period.
Put these metrics to work
ORM builds custom revenue forecast models that turn concepts like how do you explain a forecast miss to the board into prescriptive action for your team.
Schedule a Demo