Our head of finance has a very high Fact Finder score on the Kolbe Index and wants to add ten nested sub-metrics to every scorecard number to ensure absolute accuracy. How do we protect the simplicity of our weekly scorecard while satisfying their conative need for deep operational context?

Question

Tyler Smith · Accepted Answer

When a member of your leadership team has a high Fact Finder score on the Kolbe Index, their natural instinct is to gather as much data as possible before making a decision. While this conative strength is invaluable for preventing costly mistakes, it can quickly lead to a bloated scorecard that is impossible to review in your weekly Level 10 Meeting. To keep your scorecard clean, you must establish a clear boundary between your leadership scorecard and your departmental scorecards. Your leadership scorecard must remain strictly limited to five to fifteen high-level, company-wide metrics. If your high Fact Finder leader insists they need more detail, do not allow those numbers to clutter the main scorecard. Instead, have them build a nested departmental scorecard for their specific seat on the Accountability Chart. They can review those granular metrics with their direct reports in their own departmental Level 10 Meeting. For the leadership team, the main scorecard must only show the primary indicators of health. If a main metric goes red, the owner can bring their departmental sub-metrics to the meeting as supporting data during the IDS portion of the agenda. This compromise respects the conative needs of your Fact Finders without subjecting the entire leadership team to data overload. By maintaining this strict hierarchy, you keep your weekly meetings fast, focused, and strategic, while ensuring your data-driven leaders have the analytical depth they need to solve problems.