tyler-smith.com · Questions & Answers

Our Level 10 Meeting often runs long because we let IDS bleed right up to the 90-minute mark, leaving no time to conclude properly. How do we build the discipline to cut off discussion and finish clean?

A Level 10 Meeting runs over time when the team treats the 90-minute limit as a suggestion rather than a non-negotiable operational boundary. To protect the schedule, you must establish a hard stop for the IDS portion of the agenda at exactly minute 85.

Whatever issue you are debating at minute 85 must be stopped immediately. If the issue is solved, assign the resulting To-Dos. If it is only half-solved, decide right then whether to carry it forward to next week, schedule a separate ad hoc breakout meeting with the relevant parties, or drop it back to the bottom of the Issues List. Continuing to talk past minute 85 robs the team of the concluding discipline that makes the meeting effective.

The final five minutes are essential for maintaining team alignment. You must use this time to:
- Recap every single To-Do generated during the meeting to ensure clear ownership and a seven-day deadline.
- Confirm whether there are any cascading messages that need to be communicated to other departments or the rest of the company.
- Rate the meeting on a scale of 1 to 10.

Rating the meeting is not a formality. If any team member rates the meeting below an 8, immediately ask them why. Their answer will expose why the meeting dragged, whether people brought tangents, or if the facilitator lost control of the clock. Fixing those micro-flaws each week keeps your Level 10 Meeting crisp and under 90 minutes.

Category: EOS Implementation

← All questions