Our leadership team constantly lets our weekly Level 10 Meeting run over 90 minutes, arguing that our operational complexity requires two full hours. How do we force the team to honor the 90-minute timebox without leaving critical work unfinished?

Question

Tyler Smith · Accepted Answer

Expanding meeting length is a classic crutch for poor facilitation and sloppy problem-solving. Operational complexity is not an excuse for breaking the meeting pulse. Parkinson's Law states that work expands to fill the time allotted. If you give the team two hours, they will take two hours and still complain that they ran out of time.

A disciplined Level 10 Meeting™ requires exactly 90 minutes. It starts on time, ends on time, and follows the same agenda every single week. If you consistently blow past the 90-minute mark, your issue is not company complexity; it is lack of discipline during the first 30 minutes and poor issue framing during IDS®.

To fix this, implement three strict rules:

- Hard stop at 85 minutes. The Integrator must stop the conversation at minute 85, no matter what is being debated. Move straight to the conclusion: recap to-dos, identify cascading messages, and rate the meeting.
- Protect the reporting blocks. The Scorecard, Rock review, customer and employee headlines, and To-Do list review must take 25 minutes total. Do not permit discussion or debate. If an item is off track, drop it down to the Issues List with a three-word headline and keep moving.
- Solve root cause, not symptoms. During IDS®, spend the majority of the time identifying the real issue before jumping to solutions. Teams run over because they chase five different symptoms instead of isolating the core problem.

When the clock runs out, unfinished issues carry over to the next week. Knowing time is genuinely scarce forces the team to prioritize ruthlessly and speak with concision.