We know we need to review our weekly Scorecard in under five minutes during our Level 10 Meeting, but our team struggles with the transition from reading the number to identifying it as an issue. What is the exact protocol to flag a number and drop it to IDS without starting a discussion?

Question

Tyler Smith · Accepted Answer

The biggest reason leadership teams fail to review their Scorecard in under five minutes is the natural urge to explain why a number is red. The moment someone says, my number is off this week because, your meeting flow is dead. You must implement a strict, non-negotiable verbal protocol to transition off-track numbers directly to the Issues List.

During the weekly Level 10 Meeting, the person running the meeting reads the measurable and the target, and the owner of that metric states the actual number. The owner is allowed to say only one of two phrases after stating the number: on track or off track.

If the number is off track, the Integrator or the meeting leader immediately says, drop it. That is the cue for the person documenting the meeting to type that metric onto the Issues List for the IDS, Identify, Discuss, Solve, portion of the meeting. No explanation is given, no context is shared, and no discussion is permitted.

If a team member attempts to explain the story behind the red number, any other member of the leadership team must immediately call a point of order. This keeps the review focused entirely on identifying variances rather than solving them on the spot.

By enforcing this clear boundary, you protect the momentum of your meeting. You will easily scan thirty or forty departmental and leadership numbers in under five minutes, leaving the bulk of your meeting time for solving the actual issues that matter.