liveBook · Manning

One number mindset

As explained in Demand Forecasting Best Practices

A one number mindset is an alignment approach in which stakeholders share assumptions, data, and a vision of the future without requiring identical forecasts.

A one number mindset aligns supply-chain stakeholders around shared assumptions, data, and a vision of the future without forcing everyone to use an identical forecast. It addresses a practical planning problem: marketing, supply, finance, and logistics may need different forecasts to make different decisions, yet their decisions must remain coordinated. section 7.0 section 7.4

The approach distinguishes alignment from numerical uniformity. A production team may forecast long-term demand by month and raw-material type, while logistics forecasts distributor demand by day, incorporating promotions and shortages. Their numbers can differ slightly because their processes, aggregation levels, and decisions differ. section 7.2 section 7.4

A practical one number mindset requires teams to:

  • Use the same reconciled demand, pricing, master data, and other relevant information sources. section 7.4
  • Share information about demand-shaping events, including price changes, marketing events, product introductions, and competitor actions. section 7.4
  • Make forecasts accessible across functions and investigate significant deviations; differences above 5% globally may indicate weak alignment. section 7.4
  • Use S&OP as a possible channel for sharing information while allowing each function to choose an appropriate forecasting process and model. section 7.4

One launch, several useful forecasts

If marketing plans a product launch in Q2, supply planning can prepare enough inventory by the end of Q1. Production may model monthly raw-material demand, while logistics models daily distributor demand around promotions and shortages. Shared launch information aligns the decisions even when the forecasts are not identical. section 7.0 section 7.2

How Demand Forecasting Best Practices covers it

How deep it goes
Explains shared inputs, event communication, forecast access, deviation limits, and function-specific processes, but not forecasting-model internals.
Examples
Uses a Q2 product launch, Q1 inventory preparation, monthly raw-material forecasts, and daily distributor forecasts shaped by promotions and shortages.
What it assumes
Assumes familiarity with supply-chain functions, forecasts, demand drivers, and S&OP while distinguishing alignment from a single forecast.
What you can do after
Operate cross-functional forecasting with shared data while preserving the granularity and processes each function requires.
How it connects
Connects S&OP, demand forecasting, supply planning, inventory, pricing, marketing events, product introductions, and forecast reconciliation.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Demand Forecasting Best Practices. The section links point to the parts of the book it draws on.