Challenges naturally arise, and they serve as valuable discussion points with clients. For instance, we must align on core questions, ensuring everyone is clear on what we’re actually trying to answer, whether that’s market size, penetration, revenue, risk, scenario planning, etc.
Before a project gets underway, we must agree on defining the appropriate forecasting approach, whether it’s a high-level model, a bottom-up demand build, an analog-based approach, or a detailed scenario framework.
It’s also important for us to reconcile forecast differences, helping clients understand why our numbers differ from their internal forecast which may be down to methodology, scope, data, or assumptions.
Uncertainty and risk are inherent in forecasting, so it’s my job to transparently communicate caveats, such as data limitations (especially for early assets), and how to resolve them.
Challenges remain once the project is completed. I owe it to clients to explain complex outputs clearly, translating technical modeling logic into simple, intuitive explanations that resonate with non-technical stakeholders.