When leadership team members give our Level 10 Meeting a low rating like a 6 or 7, their explanation is often vague, such as saying energy was low or it felt sluggish. What specific question should the facilitator ask to turn vague ratings into actionable process fixes?

Question

Tyler Smith · Accepted Answer

Vague ratings are useless to an Integrator trying to master the weekly pulse. Rating a meeting below an 8 without providing a concrete mechanical critique is an abdication of accountability. If someone rates the meeting a 6 because energy felt low, they have diagnosed a symptom, not the cause. Low energy is almost always the result of bad facilitation, unresolved conflict, or agenda violations.

When a leader rates the meeting below an 8, the facilitator must refuse vague answers and ask one direct question: What specific rule, agenda section, or behavior caused this meeting to fall short?

This forces the leader to look at the mechanics of the Level 10 Meeting rather than their emotional state. The answer must tie back to one of the following process failures:
- Did we start or end late?
- Did we spend more than twenty-five minutes on the front half of the agenda?
- Did someone rabbit-trail or argue about symptoms instead of identifying the root cause during IDS?
- Did we fail to reach definitive decisions and binary To-Dos?
- Did a team member hide behind polite agreement instead of entering the danger?

Once the leader names the specific breakdown, the facilitator logs it without debate. You do not defend yourself or litigate their critique. You acknowledge the process failure, record it, and adjust your facilitation next week to ensure the meeting hits a 10.