Our leadership team brainstormed thirty metrics for our company Scorecard and now everyone is defending their pet metric. What exact filtering criteria do we use to cut that list down to ten without triggering political turf wars?

Question

Tyler Smith · Accepted Answer

Cutting an oversized list of numbers down to a functional EOS Scorecard requires objective operational criteria rather than subjective consensus. The purpose of the Scorecard is not to prove that everyone is working hard. Its purpose is to give the leadership team an accurate pulse of the business so you can predict the future.

Apply three strict filtering questions to every proposed metric:

- Does this metric provide a weekly leading pulse, or does it merely report history after the money is spent or lost?
- If this number turns red for two consecutive weeks, does it demand executive attention and prompt an immediate Issue for the Level 10 Meeting, or can the department handle it internally?
- Is there an existing seat on the Accountability Chart with the direct authority to move this number within seven days?

If a measurable fails any of these tests, it does not belong on the leadership Scorecard. It belongs on a departmental scorecard or in a reporting dashboard.

Remind the leadership team that keeping a metric off the company Scorecard is not a demotion of that function. It is an operational filter. The leadership table only tracks the five to fifteen vital pulses that protect overall enterprise health, revenue velocity, client satisfaction, and cash flow. When team members understand that departmental scorecards still exist to monitor their functional priorities, political friction disappears.