My operations manager has a high Fact Finder Kolbe score and has built a weekly scorecard with thirty rows of complex, lagging financial data that the rest of our leadership team hates reviewing. How do we simplify this report without triggering their resistance?

Question

Tyler Smith · Accepted Answer

A high Fact Finder will naturally want to collect and analyze every available piece of data to prevent mistakes. However, a leadership scorecard is not a detailed diagnostic report, it is a high-level dashboard designed to give you a quick pulse on the health of the business. Having thirty rows of lagging data defeats the purpose of your weekly Level 10 Meeting. To simplify this without triggering resistance from your operations manager, you must honor their conative style while enforcing EOS discipline. Explain that the leadership scorecard must be limited to five to fifteen vital, leading indicators. This forces the team to focus only on the metrics that predict future performance. To satisfy your operations manager's need for detail, help them establish a departmental scorecard for operations. This is where those thirty detailed operational metrics belong. They can review those numbers with their direct reports in their own departmental Level 10 Meeting. Only the top three or four high-level operational numbers, such as weekly capacity utilization or on-time delivery rate, should bubble up to the leadership scorecard. This allows your operations manager to maintain their deep data reserves while keeping the leadership team focused on the big picture. Emphasize that a simple scorecard is not a lack of detail, it is a sign of operational mastery.