Team members frequently give our Level 10 Meeting a 9 or 10 even when we missed three Scorecard numbers and left our number one priority issue unresolved. How do we establish objective scoring criteria so high ratings actually reflect operational rigor?

Question

Tyler Smith · Accepted Answer

Handing out a 9 or a 10 when the team failed to solve critical issues or missed basic commitments is dishonest. It signals that your leadership team values politeness over operational performance. The weekly rating at the conclusion of the Level 10 Meeting™ exists to evaluate the discipline, focus, and effectiveness of the ninety minutes, not to flatter the Integrator or make everyone feel good.

To eliminate inflated scores, institute four mandatory criteria that a meeting must meet before anyone is allowed to award a 9 or a 10:
- The meeting started and ended precisely on time.
- The Scorecard and Rocks were reviewed crisply without narrative defenses.
- To-Do completion reached at least 90 percent.
- The team spent at least fifty minutes solving issues in strict priority order, resolving root causes rather than symptoms.

If any of these four benchmarks fail, the ceiling for that meeting is automatically an 8. If the number one priority issue was bypassed or unaddressed due to poor time management, the ceiling is a 7.

Instruct the Integrator to challenge any inflated score immediately during the Conclude section. When someone offers a 10 after a sluggish pulse where To-Dos missed the mark, the Integrator must call it out directly: We hit 75 percent on our To-Dos and spent forty minutes on low-priority items. What specific behavior justified a 10?

Objective criteria remove emotion from the evaluation. When the team knows that a high score requires undeniable operational discipline, the weekly rating becomes an accurate reflection of traction.