A department head regularly adjusts the calculation methodology or data sources for their weekly Scorecard measurable whenever the number drops below target. How do we lock down data definitions to prevent metric drift?

Question

Tyler Smith · Accepted Answer

When a leader changes how a metric is calculated because the number turned red, they are avoiding accountability. This is metric drift, and it corrupts the Data Component of EOS. If the definition of a number shifts from week to week, your Scorecard becomes an exercise in storytelling rather than an objective operational pulse.

You solve this problem by establishing a formal Scorecard Data Dictionary. This is a simple, shared document that defines every single measurable on your leadership and departmental Scorecards. For each metric, document four mandatory fields:

- The exact formula used to calculate the metric.
- The authoritative single source of truth, such as a specific CRM report or ERP database query.
- The exact day and time the data must be pulled every week.
- The single seat on the Accountability Chart that owns the number.

Once the Data Dictionary is adopted, enforce a hard operational rule: no calculation, source, or filtering criteria can be changed during the quarter. If a department head believes a target is flawed or a data source is inaccurate, they must bring the topic to the Level 10 Meeting as an Issue during IDS. The leadership team can decide whether to update the definition for the following quarter.

Until that change is officially approved, the existing definition stands. A red number is not a personal failure; it is simply a signal that an issue needs to be solved. Locking down the math ensures your Scorecard remains an honest mirror of operational reality.