Our leadership team consistently rates our weekly Level 10 Meeting an 8 or 9, yet our company Rocks are slipping and Scorecard metrics are frequently red. How do we reconcile high meeting ratings with poor operational execution?

Question

Tyler Smith · Accepted Answer

When a team hands out glowing meeting ratings while the business is missing its quarterly commitments, your Level 10 Meeting is suffering from polite delusion. Rating the meeting an 8 or 9 under those circumstances means leaders are scoring how comfortable the conversation felt, not whether the pulse is producing commercial traction. A meeting that feels pleasant while the Scorecard bleeds red is a failed meeting.

The Integrator must reset the team standard for what an 8, 9, or 10 actually represents. An effective Level 10 Meeting is not measured by camaraderie. It is measured by whether you identified root causes and made hard, irreversible decisions that change real-world performance.

Enforce two structural rules during the concluding rating pulse:
- Anchor ratings to IDS effectiveness: If the team spent sixty minutes discussing an issue without assigning clear, single-owner To-Dos that move red metrics back to green, the meeting cannot be rated higher than a 6, regardless of how friendly the room felt.
- Audit prior commitments first: If your seven-day To-Do completion rate sits below the 90 percent standard, the meeting score starts at a maximum of 7 before anyone speaks.

When someone gives an unearned high score despite operational failure, challenge them directly: Our revenue metric has missed target for three weeks and two critical Rocks are off track. What specifically did we solve today that guarantees those numbers turn around next week? If they cannot point to a decisive solve, the rating drops.