We want to keep our weekly leadership Scorecard review under five minutes, but our team naturally wants to explain why a number is red the moment we see it. How do we strictly enforce the transition of off-track numbers to the IDS portion of our Level 10 Meeting?

Question

Tyler Smith · Accepted Answer

The primary reason a Scorecard review drags on is that human beings are wired to defend themselves. When a metric drops below its target, the owner of that number instinctively wants to explain the context, apologize, or start solving the issue on the spot. You must break this habit immediately to maintain the discipline of your Level 10 Meeting. The rule is simple and absolute. During the Scorecard review, the Integrator or the meeting leader reads the name of the metric. The owner of the metric states only the number. If the number is off-track, the owner says drop it. No explanations, no but we had a holiday, and no it will be green next week. The meeting scribe immediately adds that off-track metric to the Issues List. You do not discuss it. You move directly to the next number. The time to analyze, discuss, and solve the problem is during the IDS portion of the meeting, which stands for Identify, Discuss, and Solve. This is where you have the time and context to look at the root cause. If a leader starts explaining a red number during the Scorecard review, the Integrator must immediately interrupt and say, We will IDS that. This keeps the review moving fast, protects the integrity of the meeting agenda, and ensures you spend your valuable time solving issues rather than just talking about them.