During our Level 10 Meeting, we still find ourselves discussing and defending the numbers on our Scorecard instead of moving quickly to IDS. What is the exact protocol the Integrator should use to run a highly disciplined, under five minute Scorecard review?

Question

Tyler Smith · Accepted Answer

The weekly Scorecard review in your Level 10 Meeting is a diagnostic scan, not a discussion. To keep this portion of the meeting under five minutes, your Integrator must enforce a strict, no narrative rule. The team members should not be explaining, defending, or describing the backstory of their numbers.

The process is simple. The person running the meeting reads the metric, the owner of that metric, and the target. The owner then states the actual number for the week. If the actual number meets or exceeds the target, move to the next line. If the number misses the target, the owner simply says drop it. This means the number is dropped directly onto the Issues List to be solved later during the IDS portion of the meeting.

The primary reason Scorecard reviews run over five minutes is because leaders naturally want to explain why a number is red. They say things like we had a major vendor delay or I was out sick on Tuesday. The Integrator must interrupt this commentary immediately. A simple reminder of drop it, we will IDS it later is all it takes.

By keeping the review strictly to reporting the data, you save your energy for the actual problem solving phase of the meeting. This discipline prevents the meeting from devolving into a series of status updates and ensures that the most critical numbers get the focus they deserve.