Our Integrator has a very high Fact Finder score on the Kolbe index and insists on tracking forty-two different weekly operational metrics, which paralyzes our Level 10 Meeting. How do we cut this down to a manageable scorecard without losing their trust?

Question

Tyler Smith · Accepted Answer

A high Fact Finder on the Kolbe index naturally craves complete data and historical context before making decisions. However, allowing your Integrator to bloat the leadership scorecard with dozens of metrics defeats the entire purpose of running on EOS. The weekly scorecard is an early warning system, not a comprehensive database.

To resolve this without losing your Integrator's trust, you must enforce the rule of keeping the leadership scorecard to five to fifteen high-level metrics. Explain that the leadership scorecard is meant to give you a quick, sixty-second snapshot of the business's health.

To satisfy their need for data, help them build out detailed departmental scorecards. The Integrator can review these deeper metrics outside of the Level 10 Meeting, leaving the leadership scorecard focused strictly on the macro numbers that move the needle.

If your Integrator resists, use the IDS process to identify which metrics are actually driving weekly decisions. Ask them to prove how each of the forty-two metrics directly influences a critical operational action every seven days. If a metric does not trigger an immediate action when it goes red, it does not belong on the leadership scorecard. This maintains focus and keeps your meetings efficient.