We find that our weekly Level 10 Meeting becomes bogged down because we spend too much time discussing the details of why a Scorecard metric is red before we actually get to the IDS portion of the agenda. How do we keep our Scorecard review strictly informational without letting people start solving problems prematurely?

Question

Tyler Smith · Accepted Answer

This is a common bottleneck that drains the energy right out of your Level 10 Meeting. When a metric is red, human nature makes us want to explain, defend, or solve it immediately. This turns a quick five-minute Scorecard review into a disorganized, seventy-minute free-for-all.

To fix this, enforce a strict rule of zero discussion during the Scorecard review. The meeting leader must run through the numbers rapidly. If a number is red, the owner simply says, drop it down, and the scribe adds it to the IDS list. There are no explanations, no excuses, and no context allowed.

Saving all problem-solving for the IDS portion of your agenda ensures you address issues in priority order, rather than tackling them randomly as they appear on the Scorecard. Often, a red metric is connected to a larger issue or a quarterly Rock that is already on your list.

By separating the identification of red numbers from the actual solving of the problems, you maintain the tight discipline of the Level 10 Meeting. This keeps your leadership team focused, productive, and highly respectful of everyone's time.