Our Level 10 Meeting regularly runs over 90 minutes because we let the IDS portion drift without prioritizing the top three issues, or people re-open solved items. What mechanics enforce a hard 90-minute stop?

Question

Tyler Smith · Accepted Answer

The 90-minute timebox fails when the Integrator acts as a passive participant instead of an aggressive clock manager. The meeting fails in the transition to IDS®. Teams often scan a list of twelve items and start chatting about the easiest one. That guarantees you run out of time on the problems that actually threaten company revenue.

To lock down the schedule, enforce three non-negotiable mechanics:

- Force the prioritization vote. Before anyone speaks on a problem, the team must select the number one, two, and three issues. No one touches issue four until the top three are dead and buried.
- Demand an explicit solution statement. As soon as the root cause is named and a course of action is identified, the Integrator must cut off the debate. State the to-do, assign it to a single owner, confirm the seven-day due date, and push it to the list. Do not allow anyone to restate their agreement or add extra color commentary once the to-do is recorded.
- Treat minute 85 as an unmovable wall. At five minutes before the hour or half-hour, stop whatever conversation is happening, even if an issue is midway through discussion. Push the remainder of that issue to next week and run the conclude step: recap the to-dos, identify if there are any cascading messages, and rate the meeting.

If the meeting is consistently a six out of ten because you ran out of time, that rating is honest feedback that the team lacked the discipline to state the problem, solve it, and move on. Respect the clock, cut off circular dialogue, and end on the minute.