Our weekly Level 10 Meeting constantly gets derailed because leaders debate the accuracy of the CRM or ERP data instead of discussing the red Scorecard number. How do we stop data integrity arguments during Scorecard review?

Question

Tyler Smith · Accepted Answer

Debating data sources during the Scorecard agenda item is an avoidance tactic. When a leader is uncomfortable with a red number, questioning the integrity of the report is the easiest way to shift attention away from poor performance.

Your Integrator must enforce strict boundaries to protect the Level 10 Meeting cadence:
- Enforce the reporting rule: The Scorecard review takes five minutes. The leader reads the number and states whether it is on track or off track. No explanations, no backstories, and no debates about database syncing are permitted. If the number is off track, drop it down to the Issues List.
- Assume the number is correct until proven otherwise: When the issue comes up during IDS, the owner cannot dismiss the red flag by saying the data is bad. If the data is truly inaccurate, the issue to solve is not the metric itself, but broken data reporting.
- Make the seat owner accountable for data accuracy: The leader who owns the metric is responsible for auditing their data before the meeting begins. If their CRM or ERP reporting is buggy, they must reconcile it before stepping into the room. Showing up with unverified data is an accountability failure.

Assign a clear to-do to audit and fix the underlying tracking mechanism. If a leader claims the data has been flawed for multiple weeks, treat that as a process failure. The standard is simple: either the operational activity missed the goal, or the tracking process is broken. Both require an honest solution, but neither excuses dodging accountability during the Scorecard pulse.