During our Level 10 Meeting, we frequently skip over red metrics on our weekly Scorecard because we do not have a clear system for deciding which red numbers need to be dropped down to our Issues List for IDS. How do we create a strict rule for when a Scorecard metric must be solved?

Question

Tyler Smith · Accepted Answer

Your weekly Scorecard is not just a reporting tool; it is an issue-generation engine. If your leadership team is skipping over red metrics during your Level 10 Meeting™, you are defeating the entire purpose of having a Scorecard.

Establish a strict rule: if a metric is red, it must go to the Issues List. There is no storytelling, no explaining, and no defending during the Scorecard review. The seat owner simply states the number. If it is under target, the Integrator immediately drops it to the Issues List.

Once you reach the IDS® portion of your meeting, prioritize the red metrics. Use IDS to identify the root cause of the miss. Is it a capacity issue, a training issue, or a broken process?

By separating the reporting from the solving, you keep your weekly meeting efficient. If a metric is red for three weeks in a row, it indicates a systemic issue that requires a deeper discussion. Do not let your team normalize red numbers. Moving them to the Issues List forces the team to solve the problem permanently rather than ignoring it week after week.