The fallacy of forecasting

Every January, businesses go through a familiar ritual.

We forecast.

Revenue projections. Budgets. Staffing plans. Targets for the year ahead.

Twelve months laid out neatly, as if the calendar itself offered control.

Planning is useful. Forecasts give us a place to start. 

What’s worth questioning isn’t that forecasts are often wrong —  it’s why they’re wrong, and where problems actually tend to come from.

In our daily operations, most disruptions don’t come from what we fail to predict.

They come from small unpredictable events:

• A pickup that takes longer than expected
  
• A document that isn’t quite ready
  
• A route that looks clear until it isn’t
  
• A delay that compounds downstream
  
  

None of these can be predicted or forecasted for with any certainty. 

Yet they’re the moments that usually matter most because they have the most outsized negative impact. 

It is not that forecasting is bad and that you shouldn’t do it.

The risk is the false certainty forecasts can create.

It is counterintuitive, but the more rigid your forecast is the more fragile it is. 

That raises a few practical questions worth asking:

• Which parts of our business benefit from rigid certainty?
  
• Which parts perform better with built-in slack and judgment?
  
• Are we optimizing for prediction — or for response?
  

The future will unfold however it does.

It always has.

The only meaningful variable is how prepared we are for what we didn’t expect.

That’s what we design around.