We know the EOS® rule is to review our weekly Scorecard in under five minutes during our Level 10 Meeting™, but we always get bogged down. Someone explains why a number is red, or we start discussing a fix right there. What is the exact mechanical protocol for the Integrator and the team to review fifteen numbers in less than five minutes without stopping?

Question

Tyler Smith · Accepted Answer

To review your weekly Scorecard in under five minutes during your Level 10 Meeting™, you must enforce a strict operational protocol. The common failure point is when the team starts telling stories. If a number is red, someone immediately starts explaining why the market shifted, why a vendor was late, or why they will hit it next week.

The correct discipline is to go down the list of metrics one by one. The person who owns the metric simply reads the name of the metric, the current number, and whether it is on or off target. If the number is on target, move to the next. If the number is off target, the person says 'drop it'.

This means the red number is immediately dropped down to the Issues list at the bottom of your agenda. There is absolutely no discussion, no defense, and no problem-solving during the Scorecard review. The Integrator must ruthlessly police this boundary. If anyone starts a sentence with 'because', the Integrator must cut them off and say, 'we will IDS® it'.

By following this exact routine, a leadership team can easily review fifteen numbers in under three minutes. You save all your collective intelligence and time for the IDS® portion of the meeting where you can actually solve the root cause of the missed numbers instead of listening to weekly excuses.