When a leadership team member rates our Level 10 Meeting lower than an 8 during the conclusion, what is the exact operational protocol to address it without getting sucked into a new thirty-minute debate?

Question

Tyler Smith · Accepted Answer

When someone rates the Level 10 Meeting a 7 or lower, the goal is not to solve the problem on the spot. The goal is to capture the diagnosis clearly and protect the hard stop at minute ninety. Teams run into trouble when a low rating triggers defensiveness, prompting an immediate argument that blows past the scheduled end time.

The facilitator must execute a strict, four-step protocol:

- First, ask the rater for the single root cause in one sentence. The rater must name the structural failure, not vent emotions. Acceptable reasons include going down tangents during IDS, failing to start on time, or not reaching clear To-Dos on prioritized issues.

- Second, prevent all cross-talk and rebuttal. No one is permitted to argue with the rating, defend the agenda, or explain why things happened. The team must simply listen and absorb the feedback.

- Third, the Integrator decides whether the failure was a facilitation error or a systemic issue. If it was a facilitation breakdown, such as letting a debate run too long without forcing a decision, the Integrator owns it and commits to tightening discipline next week.

- Fourth, if the rating reflects an unresolved operational friction or interpersonal conflict that needs problem solving, the Integrator immediately adds it to the top of next week's Level 10 Issues List.

Once the feedback is stated and logged, the meeting adjourns immediately. A low rating is data. You do not litigate it at minute eighty-nine. You document it, respect the time boundary, and use your EOS tools to correct the behavior in the subsequent pulse.