Our weekly Level 10 Meeting™ runs long because we spend fifteen minutes discussing and debating every scorecard number. How do we review our scorecard in under five minutes without missing critical operational warning signs?

Question

Tyler Smith · Accepted Answer

The scorecard review in your Level 10 Meeting™ is not a time for discussion, debate, or storytelling. It is a rapid diagnostic check designed to identify issues, not solve them. If your review takes longer than five minutes, your leadership team is breaking the cardinal rule of the scorecard: you must drop the story and just report the numbers.

To fix this, establish a strict protocol. The meeting leader runs down the scorecard line by line. The person responsible for each metric states the actual number. If the number is within target, the leader moves to the next line. If the number is off-target, the owner says 'Drop it.' This means the number is added to the Issues List to be solved later during the IDS® portion of the meeting. No explanation is allowed, no 'we had a holiday' or 'the system was down.' Just 'Drop it.'

Ensure your scorecard is clean and visible to everyone before the meeting. There should be no surprise red numbers. Leadership team members should input their data before the meeting starts, allowing everyone to scan the sheet in advance.

If a number is consistently red, do not let it drag down the weekly scorecard review. Keep the focus on identifying the variance and moving on. By separating the identification of issues from the solving of issues, you respect the team's time and protect the integrity of the Level 10 Meeting™.