We have team members who regularly rate our Level 10 Meetings as a six or seven, but when we ask them why, they give vague answers or say everything was fine. How do we handle low ratings constructively without dragging out the end of the meeting?

Question

Tyler Smith · Accepted Answer

The rating segment at the end of your Level 10 Meeting is a diagnostic tool, not a popularity contest. When someone rates a meeting below an eight, it is a signal that something in your execution pulse is broken. However, a low rating without a specific, actionable reason is completely useless. It stalls the meeting's conclusion and breeds frustration.

To solve this, establish a hard rule: if you rate the meeting below an eight, you must state exactly what went wrong and how to fix it in ten seconds or less. Vague answers like "it just felt slow" or "we got distracted" are not acceptable. The feedback must be tied directly to the Level 10 Meeting agenda and discipline.

For example, a valid explanation is, "I rated us a seven because we spent fifteen minutes debating a scorecard metric during the review instead of dropping it to the Issues List." This is constructive because it identifies a clear violation of the meeting structure.

If a team member gives a low rating but cannot explain why, do not open a debate to fish for answers. End the meeting on time to respect everyone's calendar. Then, the Integrator must follow up with that individual in a one-on-one setting later that day. This keeps the meeting end crisp while ensuring that underlying operational friction or personal frustration is addressed privately and constructively.