Our weekly Level 10 Meeting ratings have steadily declined from a solid nine to hovering around a six or seven, and our weekly ratings review has turned into a defensive session where leaders justify the meeting's flaws instead of diagnosing the root cause. How do we use a declining meeting rating to diagnose systemic operational issues without letting the team get defensive?

Question

Tyler Smith · Accepted Answer

A declining meeting rating is not a personal insult to the facilitator. It is an objective metric showing that your weekly pulse is losing its effectiveness. When your ratings slide into the sixes and sevens, it means your leaders feel the meeting is a waste of time. Allowing defensive justifications to derail the rating review only makes the problem worse.

To stop the defensiveness and find the root cause, you must change how you process low ratings. The rating is a tool to protect your time and maintain accountability.

Use this process to handle declining ratings objectively:
- First, enforce the rating rule. Every leader must give a number from one to ten based on how well the team followed the agenda and solved problems. No half points and no safe eights.
- Second, if anyone rates the meeting below an eight, they must state exactly why in ten seconds or less. They do not get to give a speech or defend their seat. They simply state the gap. For example, we spent too much time debating instead of solving, or we did not get to our top issues.
- Third, do not solve the rating feedback during the ratings block. If a rating is low, the Integrator must immediately drop the feedback to the Issues List for the following week.

By treating low ratings as data points rather than personal attacks, you remove the emotion. This allows the team to identify and solve the underlying process issues during the next IDS session, restoring your meeting to a high-performing level.