tyler-smith.com · Questions & Answers

Certain operational metrics on our Scorecard fluctuate wildly from week to week due to client billing cycles and batch processing. Should we track rolling four-week averages on our weekly Scorecard, or does that obscure immediate operational problems?

Do not use rolling averages on your weekly Scorecard. Rolling averages smooth out volatility, but the primary job of a weekly Scorecard is to show you raw, unfiltered operational friction. Smoothing out the data dulls your pulse and hides the exact bottlenecks your leadership team needs to solve.

When you use a rolling four-week average, an operational collapse in week one is masked by strong numbers in weeks two, three, and four. By the time the rolling average turns red, the operational failure has been compounding for a month. A Scorecard should act like an emergency room monitor; you want to see the immediate heartbeat, not a smoothed curve over the past hour.

If a metric swings wildly because of batch processing or billing cycles, the problem is usually that you are tracking an output instead of an input. For example, if cash collected swings between zero and two hundred thousand dollars depending on the week your billing runs, stop tracking cash collected on the weekly Scorecard.

Instead, track the weekly activities that govern billing health, such as timecards submitted on time by Friday at five, unbilled work-in-progress aged over seven days, or invoices sent within twenty-four hours of milestone completion.

By tracking the daily or weekly disciplines that lead to consistent billing, you eliminate the artificial lumpiness. Keep raw, weekly numbers on your company Scorecard and leave trailing averages for monthly financial reviews.

Category: Scorecards & Data

← All questions