When we occasionally get an honest, low rating of a six or seven at the end of our Level 10 Meeting™, the feedback session instantly devolves into a defensive debate that runs past our hard stop time. How do we capture honest feedback on our meeting quality without letting the final two-minute rating segment derail our schedule?

Question

Tyler Smith · Accepted Answer

The final two minutes of your Level 10 Meeting are meant for a quick, objective pulse check, not a post-mortem debate. When a leader rates the meeting a six or seven, the natural instinct of a driven leadership team is to immediately defend their performance or start solving the meeting quality issues on the spot. This causes the meeting to run late, violating the hard stop rule. To protect your schedule, you must establish a strict rule for ratings under an eight. When a leader gives a low score, they must state the specific reason in ten words or less, with zero follow-up discussion allowed from the rest of the team. For example, they might say, we spent too much time on the scorecard and rushed IDS. Once the low score and reason are stated, the Integrator simply writes it down and ends the meeting. Do not allow anyone to argue, explain, or apologize. The feedback is now data. If a specific trend emerges over two or three weeks, such as consistent complaints about scorecard debates, that trend is added as an issue for the next weekly meeting. By deferring the discussion to the actual IDS portion of the next Level 10 Meeting, you respect everyone's time, maintain meeting discipline, and ensure that the root cause of the poor meeting quality is solved systematically rather than in a rushed, emotional state.