During our Level 10 Meeting, we tend to fly through the scorecard in two minutes, just reading the numbers without actually digging into the reds. How do we force our team to stop glossing over the scorecard and actually drop critical misses to the IDS portion?

Question

Tyler Smith · Accepted Answer

Flying through your scorecard without discussing the misses is a waste of time. The scorecard is not a status report to be read aloud. It is an early warning system designed to highlight problems. If your team is simply saying 'on track' or reading numbers off a screen and moving on, you are missing the entire value of the EOS® Data Component.

To fix this meeting hygiene issue, the person running the Level 10 Meeting™ must enforce strict discipline. The rule is simple: when a scorecard metric is red, the owner of that metric must state the number and immediately say, 'Drop it.' Do not allow them to explain why it is red. Do not allow them to apologize or start solving the problem on the spot.

The meeting leader must write the red metric on the Issues List. Only when you reach the IDS® portion of the meeting do you dig into the data. This keeps your meeting moving efficiently and prevents the scorecard review from turning into a twenty-minute session of defensive excuses.

If your team resists dropping red numbers to the Issues List, it is usually because they view the list as a punishment. You must change this mindset. The Issues List is a tool for collaborative problem-solving. By forcing every red number down to IDS®, you ensure that your leadership team actually spends their time resolving root causes rather than just looking at a colorful spreadsheet.