When closing the spreadsheet gap hides the revenue gap.
When I owned an annual revenue plan north of $100 million, there were months when my forecast didn't line up with my target.
Let's say my monthly target was $10 million.
My forecast said $9 million.
That left me with a $1 million problem.
And there was a convenient place to put that problem: stretch.
I'd put $1 million into the stretch bucket. Now the consolidated report showed a $10 million target and a $10 million forecast.
Forecast to target: 1:1.
Gap: zero.
And, at least temporarily, I stayed off the radar.
The problem, of course, was that nothing had actually changed.
I hadn't closed another deal. I hadn't created another qualified opportunity. The customer hadn't suddenly found another million dollars. My sales team wasn't a million dollars closer to the target.
I'd closed the gap in the reporting—not in the business.
There was certainly some momentary relief when that consolidated report came out. Nobody was immediately asking why I was forecasting below target.
But the $1 million problem hadn't disappeared.
It was waiting for me.
And as the month progressed, the pressure increased because eventually that stretch had to become real revenue. Now we were looking for deals to accelerate, opportunities to expand, additional customer demand, or anything else that could legitimately close the gap.
That's where I learned an important distinction.
Stretch can be a useful management mechanism. It is a dangerous forecasting mechanism.
There is nothing wrong with saying:
Target: $10M
Forecast: $9M
Gap: $1M
Stretch opportunity: $1M
That tells leadership something useful.
We have a $1 million risk, and management is actively working to close it.
The problem starts when we report:
Target: $10M
Forecast: $10M
Gap: $0
Now we've taken information that should trigger management attention and made it disappear.
And if an organization does this often enough, stretch can become organizational camouflage.
The dashboard looks healthy. Forecast-to-target alignment looks healthy. Senior leadership moves its attention somewhere else.
Meanwhile, the underlying problem may still exist.
Maybe there isn't enough pipeline. Maybe opportunities aren't progressing. Maybe qualification is weak. Maybe conversion rates are deteriorating. Maybe customers have stopped spending. Maybe the target itself is unrealistic.
Those are precisely the things a good management system is supposed to expose.
Because eventually, someone has to turn that stretch into an actual customer commitment.
And Excel has never signed a contract.
The lesson I took from this wasn't to eliminate stretch.
It was to stop confusing ambition with forecast confidence.
A forecast should tell us what we reasonably expect to happen based on the evidence we have today.
Stretch should tell us what else we believe we might achieve if specific actions, opportunities or assumptions materialize.
Keeping those numbers separate can make the reporting look less comfortable.
But that's the point.
A good management system doesn't keep leaders off the radar. It puts the right problems on the radar early enough to do something about them.
Key Takeaways
- Stretch doesn't eliminate a forecast gap. It identifies what must happen to close it.
- Keep target, evidence-based forecast, gap and stretch visible as separate measures.
- A persistent reliance on stretch can mask pipeline, qualification, conversion or market problems.
- Forecasting should expose risk early, not make the dashboard look better.
- The uncomfortable number is often the number management most needs to see.
