We are supposed to spend only five minutes reviewing our weekly scorecard, but we regularly spend fifteen to twenty minutes because team members argue about the accuracy of the data or debate how the metrics were calculated. How do we keep our scorecard review crisp and move system level data disputes off the weekly agenda?

Question

Tyler Smith · Accepted Answer

The scorecard review section of your Level 10 Meeting™ is strictly for reporting. It is designed to take exactly five minutes. Its only purpose is to state whether the numbers are on track or off track. The moment your team begins to debate the accuracy of a metric or argue about how the data was pulled, you have drifted into solving.

To stop this, the facilitator must enforce a hard boundary. If a team member challenges the accuracy of a number or disagrees with how a metric was calculated, the facilitator must immediately stop the conversation. Do not allow them to explain, defend, or analyze the data pipeline.

Instead, say the phrase: drop it to the list.

The data dispute is now an item on the Issues List. You will handle it during the IDS® portion of the meeting, where you actually have the time to diagnose the system level issue. If you try to solve a reporting issue during the scorecard review, you will run out of time for everything else.

Your weekly numbers must be fully updated and verified before the meeting begins. If there is a recurring problem with data accuracy, that is a separate issue that needs a permanent system level fix. Keep the reporting section clean, silent, and fast.