When a weekly number on our scorecard is red, our leadership team immediately starts trying to solve it during the scorecard review. How do we keep our scorecard review efficient and correctly push these data deviations down to the Issues List?

Question

Tyler Smith · Accepted Answer

The biggest trap leadership teams fall into during their weekly Level 10 Meeting™ is turning the scorecard review into a fifteen-minute debate about why a number is red. This completely derails the meeting and leaves you with no time to solve actual strategic issues. The scorecard review is strictly for identifying issues, not solving them. If a number is red, the owner of that metric simply says red and the Integrator immediately adds it to the Issues List. Once the entire scorecard is reviewed in under five minutes, you move on to the rest of the agenda. Only when you reach the Identify, Discuss, and Solve (IDS™) portion of the meeting do you tackle the red numbers. When a scorecard issue is brought up in IDS™, you must first identify the root cause. Do not waste time talking about the symptoms. Ask why the target was missed and trace it back to a process failure, a capacity bottleneck, or a people issue. By separating the identification of data deviations from the solving phase, you keep your weekly meeting tight, focused, and highly productive.