We implemented the Level 10 Meeting™ agenda, but our leadership team consistently runs over ninety minutes and we rarely get to the bottom of our Issues List. How do we keep the meeting tight and efficient without cutting off valuable discussions?
A ninety minute meeting is not a suggestion. It is a hard boundary designed to force discipline and prioritization. When meetings run long, it is usually because the team is trying to solve issues during the reporting segments or because the Issues List has not been curated.
First, enforce a strict policy of zero discussion during the first twenty-five minutes. The Segue, Scorecard, Rock review, customer and employee headlines, and To-Do list are for reporting only. If a metric is off or a Rock is off-track, the only acceptable response is to say 'off track' and drop it to the Issues List. Do not explain, defend, or strategize in the reporting phase.
Second, when you transition to IDS®, do not work the list from top to bottom. The team must vote on the top three issues that will move the needle most. If you only solve those three, you have had a successful meeting.
Third, appoint a strong meeting leader who acts as a gatekeeper. If someone starts telling a long story, the leader must intervene immediately and ask to drop it to the Issues List or redirect back to the topic. Finally, end on time. If you reach the ninety-minute mark and only solved one issue, stop the meeting, rate it, and transition. This discomfort forces the team to become more efficient next week.
Category: EOS Implementation