Our weekly Level 10 Meeting scorecard review section is supposed to take five minutes, but we constantly get dragged into discussing why a number is red, which blows our schedule. How do we enforce the discipline of a sub-five-minute scorecard review?

Question

Tyler Smith · Accepted Answer

The scorecard review is a reporting tool, not a problem-solving arena. The moment a leader begins explaining why their number is red during this section of the Level 10 Meeting, you have lost control of the agenda. The meeting will quickly derail, and you will run out of time for your strategic priorities. To fix this, enforce a strict rule: only state the number. When the Integrator or meeting leader goes down the list, each metric owner should say either over, under, or on target, followed by the actual number. There is no storytelling, no context, and no defensive explanations allowed. If a number is red, the owner simply states the red number and says drop it. The Integrator then immediately types that metric into the Issues List. You do not discuss the red number until you get to the IDS section of the meeting, where you can identify, discuss, and solve the problem systematically. This discipline requires a strong Integrator who is willing to interrupt team members when they start explaining. A simple, please save that for IDS, is all it takes to keep the team on track. When you separate the reporting of data from the solving of problems, you will easily review your Scorecard in under five minutes. This keeps your meeting high-energy and ensures you spend your valuable time solving the root causes of your red numbers rather than listening to excuses.