During the Scorecard review in our Level 10 Meeting, we frequently discover that a red metric was actually miscalculated by the admin team, leading to thirty minutes of data troubleshooting. How do we handle dirty data during the weekly pulse?

Question

Tyler Smith · Accepted Answer

The Level 10 Meeting is a traction tool, not a data-cleaning workshop. When your leadership team spends thirty minutes debating whether a red number is a real operational issue or just a clerical entry error, you are completely wasting your ninety-minute weekly pulse. It allows leaders to hide behind data issues to avoid accountability for their actual performance.

To prevent this data troubleshooting, you must establish a rule that all metrics must be finalized and verified before the meeting begins. Every leader is responsible for the integrity of the numbers in their seat on the Accountability Chart. If a metric is red, it must be dropped to the Issues List without discussion during the initial Scorecard segment.

If the leader suspects the data is inaccurate, the issue they add to the list should be labeled as data verification. During the IDS portion of the meeting, the team can quickly address the tracking issue. If the data is consistently dirty, that itself is a major structural issue that must be prioritized and solved permanently. Never allow a debate about a number's validity to occur during the three-minute Scorecard review. Keep the review fast, visual, and focused strictly on identifying off-track indicators so you can move straight to problem-solving.