tyler-smith.com · Questions & Answers

Our weekly Level 10 Meetings consistently drag past ninety minutes or get rated a six out of ten by our leadership team. How do we fix the pacing and enforce honest ratings so the meeting actually saves time?

A Level 10 Meeting™ that runs long or consistently scores below an eight indicates that your leadership team is violating the agenda disciplines. The first twenty-five minutes of the meeting are purely for reporting, not discussion. If your team starts solving problems during the Scorecard, Rock review, or customer and employee headlines, your meeting will derail every time.

Keep the reporting sections rigid. The Scorecard review takes five minutes. State the number, report whether it is on track or off track, and drop any off-track number down to the Issues List. Do not explain why it is off track. The Rock review takes five minutes. State whether your Rock is on track or off track; if it is off track, drop it to the Issues List with zero commentary. Headlines take five minutes.

By minute twenty-five, you should transition directly to the Issues List with sixty minutes remaining. Prioritize your top three issues before talking. Never start at the top of the list just because an issue was written down first. Solve issue number one, then number two, then number three using IDS®.

At the conclusion, every leader rates the meeting from one to ten. If someone rates the meeting under an eight, ask them immediately why they gave that score and what needs to change next week. Do not get defensive. Use their feedback to correct the pacing so the meeting protects executive time instead of consuming it.

Category: EOS Implementation

← All questions