When a metric on our Scorecard turns out to have been reported inaccurately due to bad CRM data or calculation mistakes, who is held accountable on the Accountability Chart: the seat that owns the number or the person who pulled the data?
The seat that owns the measurable on the Scorecard is entirely accountable for the accuracy of that number, regardless of who pulled the report or which software generated the export.
In an EOS organization, putting your name next to a number means you vouch for its truth. If a sales director reports 14 qualified opportunities in the Level 10 Meeting, and three days later explains that the CRM had duplicate records and the true number was eight, the sales director owns that miss. Blaming administrative assistants, bad database filters, or messy software integrations is an abdication of leadership.
If a leader relies on data from a CRM or an automated dashboard, verifying the integrity of that data before the meeting starts is part of owning the seat. They must understand the underlying logic of the metric. If the numbers look irregular or disconnected from ground-level reality, they must catch the discrepancy before reporting the score.
When bad data enters the Scorecard, do not let the conversation devolve into an IT debugging session. Identify the owner, note the inaccuracy, and drop it to the Issues List. In IDS, solve the root cause: either clean up the reporting process or simplify the metric so human verification takes under two minutes.
Category: Scorecards & Data