3.1 Why project plans fail

Weak plans often list topics rather than work. An entry such as “forecasting” does not identify what will be produced, which data are required, who is responsible, how the result will be checked, or when the work must be stable enough to support the report. The label creates the appearance of planning without making the project easier to manage.

A useful plan converts broad work into observable outputs. Instead of “do forecasting,” a team might plan to:

1. confirm the response variable and forecast horizon;
2. identify complete historical periods;
3. create a baseline forecast;
4. fit and compare candidate methods;
5. validate using a time-ordered holdout period;
6. document assumptions and limitations; and
7. prepare a reviewed figure and interpretation for the report.

This level of detail makes dependencies visible and allows progress to be evaluated before the final deadline.