tyler-smith.com · Questions & Answers

Our leadership team spends fifteen to twenty minutes arguing over scorecard rows during our weekly Level 10 Meeting instead of the allocated five minutes. How do we tighten our review so we hit the five-minute mark without missing real operational problems?

Five minutes is more than enough time to review an EOS Scorecard of 5 to 15 numbers, provided your team follows one non-negotiable rule: report numbers, do not discuss them.

Your weekly review is an audit, not a problem-solving session. The Integrator or the meeting leader calls out each measurable line by line. The seat owner gives only the number. If the target is met, move to the next row. If the target is missed, the owner says only two words: drop it. The Integrator immediately logs the metric on the Issues List for the IDS portion of the agenda.

Teams blow past five minutes because owners immediately jump into justification mode. They explain why a client delayed signing, why weather slowed down the job site, or why software went offline. The moment an owner begins defending a red number, the meeting leader must intervene and say: drop it to issues.

Context and root-cause analysis belong in the final sixty minutes of the Level 10 Meeting under IDS, where the entire team can prioritize whether that miss is one of the top three issues that day. When you forbid commentary during the Scorecard review, you will routinely review fifteen numbers in less than three minutes.

Category: Scorecards & Data

← All questions