In the conclude section of our Level 10 Meeting, team members frequently give low ratings like a 5 or 6 because they are stressed about heavy operational workloads or unhappy with a consensus decision, rather than evaluating the meeting itself. How do we keep the rating focused strictly on meeting execution?

Question

Tyler Smith · Accepted Answer

The Level 10 Meeting rating is an audit of meeting mechanics and team discipline. It is not an employee satisfaction survey or an emotional pulse check on the general state of the company.

When a leader rates the meeting a 5 simply because they had a stressful morning or because the room made a hard operational call they personally opposed, they break the utility of the tool. The facilitator must immediately redirect the feedback.

Establish the ground rules for what a 10 means:
- Did we start on time and end on time?
- Did we follow the agenda without skipping sections or lingering on status reports?
- Did we maintain total transparency and vulnerability during IDS?
- Did we identify root causes and walk away with clear, seven-day to-dos?

If the answer to those four questions is yes, the meeting was an 8, 9, or 10, regardless of whether the business is facing brutal market conditions.

When someone drops a low score, the facilitator must ask one specific question: "What specifically about our agenda, time management, or IDS discipline caused that rating?"

If their response is about general business stress or fatigue, the facilitator should respond calmly: "Understood on the operational pressure, but that belongs on the Issues List next week. Based purely on whether this meeting ran effectively, what is your score?"

Separating operational anxiety from meeting efficiency trains the team to view the weekly pulse as their anchor during chaos rather than an outlet for general frustration.