During our Level 10 Meeting, leaders constantly want to explain why their Scorecard metric is red instead of just dropping it down to the Issues List. What is the exact protocol for reporting off-track numbers without burning meeting time?

Question

Tyler Smith · Accepted Answer

The Scorecard reporting section of a Level 10 Meeting must take exactly five minutes. Yet, weak teams routinely turn it into an hour-long storytelling session. A number comes in red, the seat owner feels exposed, and they instantly launch into a three-minute narrative explaining the client delays, seasonal anomalies, or external vendor failures that caused the miss.

That behavior destroys meeting rhythm and obscures operational accountability. The reporting section is strictly for data transmission, not discussion. You are checking the vital signs of the business. You do not treat the patient while taking their pulse.

The protocol for an off-track metric is absolute:
- The seat owner reports the number and states only one word: on-track or off-track.
- No background stories, no context, and no defense are permitted from anyone in the room.
- If the number is off-track, the Integrator asks a single question: drop it or leave it?
- If it needs attention, the metric is placed directly onto the Issues List as a single line item, and the facilitator moves immediately to the next number.

When you push the problem down to the Issues List, you preserve the five-minute timebox and give the metric the dedicated problem-solving time it deserves during IDS. In IDS, the team can analyze the trend, uncover the operational breakdown, and assign a definitive To-Do to fix the root cause. Keep reporting cold and save analysis for the list.