What happens when our weekly Scorecard shows a metric is off track, but the seat owner claims the data is simply delayed and will normalize next week? Do we drop it, or how do we handle data latency without losing the weekly pulse?

Question

Tyler Smith · Accepted Answer

Delayed data is useless data. If a seat owner tells you that a red number is just a reporting delay, they are missing the point of running on a weekly pulse. The Scorecard is designed to give you a real-time snapshot of the business's health right now, not a history lesson.

When data is delayed, that metric is red. You do not skip it, and you do not accept excuses. The target was not met because the data was not delivered on time, which is itself an operational failure. If a leader cannot produce the number by the time of your Level 10 Meeting™, they do not GWC™ their seat's data responsibilities.

You must handle this by creating a clear standard for data latency. If a system lag prevents weekly reporting, the owner of that metric must find a manual leading activity that can be measured weekly, or they must fix the data pipeline as a quarterly Rock.

Never let delayed reporting become an acceptable reason for a red metric. If you allow exceptions, your team will quickly realize they can hide poor performance behind the excuse of slow reporting. Hold the line on weekly accountability, and require your team to solve the data bottleneck instead of tolerating it.