Our leadership team spends half our weekly Level 10 Meeting arguing over why a Scorecard metric dropped into the red instead of actually solving the problem. What is the exact protocol for dropping a red number down to the Issues List and processing it through IDS?

Question

Tyler Smith · Accepted Answer

The Scorecard review in your weekly Level 10 Meeting should take no more than five minutes. It is a reporting pulse, not an open debate. The moment leadership team members start explaining, rationalizing, or debating why a number is red, the meeting falls apart and your Integrator loses control of the agenda.

Follow this exact protocol to keep the Scorecard clean and disciplined:

The Integrator reads down the list of measurables row by row. The owner of the number states one of two phrases: on pace or off pace. They do not say why. They do not give background context. They report the actual number versus the target.

If a measurable misses its target, anyone in the room can say drop it. The Integrator immediately writes the issue on the Issues List. The team does not discuss the miss. The Integrator moves instantly to the next row on the Scorecard.

Once the Scorecard, Rock review, customer headlines, and To-Do list are complete, the team moves into IDS. During IDS, the team prioritizes the top three issues for the week. If a dropped Scorecard metric is one of the top three priorities, you solve it then.

During IDS, you identify the real root cause of the red number. Is the target unrealistic? Was there an execution failure? Has the market changed? You discuss solutions and assign a concrete To-Do to an individual seat with a seven-day deadline.

This strict boundary prevents meeting fatigue. It ensures that off-track metrics get genuine, root-cause resolution rather than hurried defensive explanations during the first ten minutes of the meeting.