tyler-smith.com · Questions & Answers

My COO is a high Fact Finder on the Kolbe Index and wants to track 40 different metrics on our scorecard. How do I rein this in?

A high Fact Finder on the Kolbe Index instinctively wants to gather detailed data, establish historical precedence, and eliminate all ambiguity before taking action. While this is an incredible strength for operational design, it can quickly paralyze a leadership team's scorecard.

If your leadership scorecard contains 40 metrics, you don't have a scorecard; you have a spreadsheet of noise. A true EOS® scorecard must consist of only 5 to 15 high-level, critical metrics that give you a pulse on the health of the entire organization. For guidance on selecting these, consider [how to choose five to fifteen scorecard metrics](/qa/how-to-choose-five-fifteen-scorecard-metrics).

To resolve this conflict without frustrating your COO, introduce the concept of tiered scorecards.

Implementing Tiered Scorecards

Explain that the leadership team's scorecard must remain at a high level to avoid "losing the forest for the trees." This keeps the team focused on strategic execution rather than minor operational details, which is crucial for efficient [Level 10 Meeting™ facilitation](/qa/should-integrator-facilitate-level-10-meetings).

Here's how to structure it:

• Leadership Team Scorecard: This should contain only the 5 to 15 critical, high-level metrics that reflect the overall health and strategic direction of the company. These are the numbers the entire leadership team reviews weekly. If you're struggling to keep scorecard reviews quick, check out [how to review your weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes).
• Departmental Scorecards: Your COO's operations department, and other departments, can have their own detailed scorecards containing 30 or 40 specific metrics that they review with their direct reports. These deeper dives satisfy the Fact Finder's need for granular data and support departmental accountability.

Only the critical, rolling summary metrics from the departmental scorecards should bubble up to the leadership scorecard. This approach:

• Satisfies your COO's need for deep data integrity.
• Keeps the leadership team focused on strategic execution.
• Allows you to run your weekly Level 10 Meeting™ efficiently without drowning in minor operational details.

AI and Scorecards

AI can play a crucial role in supporting this tiered system.

• AI works before the Level 10 Meeting to prep the data, ensuring it is accurate and summarized appropriately for each tier. This can streamline the process for [optimizing EOS Scorecard metrics](/qa/ai-in-optimizing-eos-scorecard-metrics-and-accountability).
• AI works after the meeting to capture and track what was decided, helping to maintain accountability.
• The 90 minutes of the Level 10 Meeting™ remain human focused: your leadership team, the scorecard review, the issues list, and the IDS conversation.

Related questions

• [How to choose five to fifteen scorecard metrics](/qa/how-to-choose-five-fifteen-scorecard-metrics)
• [How to review your weekly scorecard in under five minutes](/qa/how-to-review-scorecard-under-five-minutes)
• [What concrete weekly measurables should we track for our accounting and IT seats to keep them accountable without resorting to subjective check the box metrics?](/qa/back-office-weekly-scorecard-measurables)
• [How do we shift our focus from lagging results to weekly leading indicators?](/qa/leading-vs-lagging-scorecard-metrics)
• [What is the best way to leverage AI to optimize EOS Scorecard metrics and improve accountability?](/qa/ai-in-optimizing-eos-scorecard-metrics-and-accountability)

Category: Scorecards & Data

← All questions