Our Integrator gets so absorbed in debating issues during IDS that they let the conversation run past the 60-minute mark, leaving us two minutes to rush through Conclude and drop critical To-Do confirmations. How do we enforce the time boundary without truncating high-priority decisions?

Question

Tyler Smith · Accepted Answer

The Level 10 Meeting agenda is a hard ninety-minute time box, not a guideline. When an Integrator allows IDS to swallow the Conclude section, they compromise the operational output of the entire meeting. A decision without clear, confirmed To-Dos is merely a conversation.

The rule is absolute: at minute eighty-five, IDS stops immediately, regardless of where you are in the discussion. The Integrator or the designated timekeeper must call hard stop.

If the issue being debated is unresolved at the eighty-five minute mark, you have three clean operational choices:
- Push the issue to next week's Level 10 Meeting as the number one priority.
- Schedule a dedicated thirty-minute working session outside the Level 10 pulse with only the essential people required to solve it.
- Make an executive call on the spot if an immediate decision is operationally mandatory.

You cannot borrow time from the Conclude section. You need those final five minutes to read every new To-Do aloud, confirm single-point ownership, verify seven-day deliverability, clarify whether any customer or employee messages must be communicated, and collect honest ratings.

If your Integrator struggles to watch the clock while contributing their functional perspective, assign a team member to act as a strict timekeeper with the explicit authority to cut the Integrator off at minute eighty-five.