During our scorecard review in our weekly Level 10 Meeting, we frequently miss our five-minute time limit because our team immediately starts defending and explaining their red metrics the moment we read them. How do we enforce the rule of simply dropping red numbers down to the Issues List without letting the team derail the meeting with defensive explanations?

Question

Tyler Smith · Accepted Answer

The scorecard review in your weekly Level 10 Meeting is a pulse check, not a problem-solving session. You have exactly five minutes to run through your five to fifteen metrics. If your team starts explaining, defending, or apologizing for their red numbers, your meeting will quickly devolve into a chaotic, unstructured debate. This kills your momentum and leaves you with no time to solve your actual issues.

To fix this, you must enforce a strict rule of no explanations during the scorecard review. The review process should be mechanical. The metric owner reads the name of the metric, the target, and the actual number. If the number is red, the owner simply says 'off track'.

- Do not allow anyone to explain why the number was missed.
- Do not allow anyone to start suggesting solutions.
- The leader of the meeting must immediately direct the team to drop the red metric to the Issues List.

Once the red metric is on the Issues List, you will have plenty of time to solve it during the IDS portion of your meeting. During IDS, you can dig into the root causes, debate solutions, and assign action steps. By keeping the scorecard review strictly to a high-speed pulse check, you protect your meeting schedule and ensure that you are solving your most critical issues in a structured, calm manner.