tyler-smith.com · Questions & Answers

Several of our key operational metrics swing wildly from week to week because of irregular project delivery schedules, making the Scorecard feel like a roller coaster. Should we report raw weekly numbers or use rolling averages to smooth out the trend?

Raw weekly numbers are almost always better for driving immediate operational accountability. When you use rolling averages or smoothed numbers on a weekly Scorecard, you often mask the very friction you need to see. Smoothing is what corporate accountants do to hide volatility. A Scorecard is designed to expose operational reality so you can fix it.

If your numbers swing from zero to twenty week after week, the roller coaster is not a reporting flaw. It is a symptom of batch processing in your operations. It means your team is waiting until the end of a sprint or billing cycle to dump completed work, rather than maintaining a continuous, predictable flow of output.

Here is how to handle volatile operational metrics without destroying the weekly pulse:
- Keep the primary Scorecard cell as the actual number achieved during the prior seven days. If the team delivered zero projects this week, write zero. Let it show up red.
- If the work truly has an unavoidable multi-week cadence, establish a four-week rolling total as an adjacent companion measurable, but do not replace the weekly figure.
- Redefine the measurable to track the smaller, continuous milestones within that project delivery rather than just the final handoff. Track weekly milestone stage gates completed rather than final project delivery.

Looking at thirteen weeks of raw weekly data side by side on your Scorecard sheet will reveal patterns you can actually solve in IDS. Smoothing the number removes the urgency to fix the underlying operational batching.

Category: Scorecards & Data

← All questions