Our weekly operational data fluctuates drastically from week to week due to uneven project schedules, creating constant red-and-green whiplash. Should we use trailing rolling averages on our Scorecard instead of discrete weekly numbers?

Question

Tyler Smith · Accepted Answer

Trailing rolling averages feel comfortable because they smooth out volatility and produce stable, pleasant trend lines. However, substituting rolling averages for discrete weekly numbers on your primary EOS Scorecard is usually a mistake. Rolling averages disguise acute operational failures by burying recent bad news inside the mathematical cushion of the previous three or four weeks.

The weekly Scorecard is designed to provide an unvarnished pulse of the past seven days. If a milestone missed or output dropped to zero, your leadership team needs to see that red box immediately. If you replace that discrete miss with a rolling four-week average, the number stays comfortably green, delaying your reaction until systemic damage is already done.

If your business experiences natural weekly cyclicality due to deliverable timing, address it with clear structural rules:

- Track the discrete weekly number in the current week column to preserve accountability.
- Use the trailing thirteen-week view on the Scorecard to observe macro trends and multi-week trajectories.
- If a metric must be evaluated as an average due to extreme daily variance, clearly label it as a rolling four-week average while setting a secondary threshold that triggers an issue if any single week drops to zero.

Do not use mathematical smoothing to protect your leadership team from the discomfort of a red number. A volatile Scorecard is operational reality speaking to you. If project delivery creates extreme whiplash, the solution is not smoothing your spreadsheet; it is leveling your operational throughput.