Our weekly business numbers fluctuate wildly from week to week due to client billing cycles and sporadic deliveries. Should our leadership Scorecard track raw weekly snapshots or a trailing 4-week rolling average to smooth out the noise?

Question

Tyler Smith · Accepted Answer

As a foundational rule, an EOS Scorecard must track raw weekly numbers. Smoothing out the data with rolling averages inside your primary weekly meeting dilutes accountability and obscures immediate operational reality.

When you use a trailing 4-week average, a disastrous single week is hidden beneath the performance of the prior three weeks. By the time the rolling average finally turns red, the operational breakdown occurred a month ago, robbing your leadership team of the opportunity to intervene early.

If your numbers fluctuate wildly, that volatility itself is valuable diagnostic data. Rather than smoothing the number to make the Scorecard look orderly, investigate why the volatility exists. In service companies, lumpy numbers usually point to operational batching:
- Invoicing is held until the end of the month instead of executed weekly upon milestone completion.
- Delivery teams log work sporadically rather than maintaining a disciplined daily rhythm.
- Sales reps hold signed contracts to drop them all at once.

The correct approach is to track raw weekly actuals against a weekly target on your primary Scorecard. If an operational metric has natural, uncontrollable variation, you can display a secondary trailing 4-week trend column next to the weekly entry for context.

However, the weekly review must remain focused on the actual performance of the prior seven days. That discipline forces your team to eliminate lumpy execution.