**Our Take**
Excel's FORECAST.ETS function has barely changed in years, and that silence from Microsoft speaks volumes. For a tool that millions of people open daily to make decisions about inventory, revenue, or headcount, stagnation is not neutrality, it's a slow erosion of trust. The user who posted this thread has five years of professional forecasting experience and returned to find a single algorithm, no outlier handling, no multivariate capability. That's not a feature set; it's a ceiling.
The practical consequence for planners is clear. If you rely on Excel's built-in forecasting for anything beyond a rough directional estimate, you are working around its limits rather than with its strengths. The software can handle a clean, univariate time series with minimal anomalies. The moment your data includes a promotional spike, a weather event, or a macroeconomic shift, the model has no way to incorporate that information. You are left stacking external variables in adjacent columns and hoping the correlation survives the manual effort. That is not planning, it is patchwork.
What makes this particularly frustrating is that the simplicity is often framed as a virtue. Teams can audit the logic. New hires can follow it. But simplicity becomes a liability when it prevents you from asking better questions. A single algorithm treats every forecast as the same problem, which is the opposite of how serious planning works. Real forecasting demands context: seasonality that shifts, promotions that distort baselines, and external drivers that deserve their own coefficients. Excel offers none of that natively, and the user community has been expected to make peace with the gap.
The takeaway is not that Excel is useless. It is that the tool has not kept pace with the needs of people who plan for a living. If your forecasting process requires outlier detection, multivariate inputs, or any form of automated adjustment, you are already operating outside the boundaries of what FORECAST.ETS can deliver. The honest question becomes whether your organization is better served by a tool that everyone can understand but that cannot handle reality, or by one that may take a few hours to learn but actually matches the complexity of the work you do. We know which side of that trade we would choose.