When our Level 10 Meeting hits the 85-minute mark, we are often deep in the weeds of an intense, unresolved IDS debate. How should the Integrator enforce the hard stop without abandoning critical work half-done?

Question

Tyler Smith · Accepted Answer

The ninety-minute rule is sacred. A Level 10 Meeting starts on time and ends on time every single week. The moment you permit a meeting to stretch to 95 or 105 minutes because you were close to a breakthrough, you destroy the integrity of your Meeting Pulse. Leaders stop trusting the calendar, they schedule padding after the meeting, and they stop fighting hard to solve issues efficiently within the allocated time.

When the clock strikes minute 85, the Integrator must cut the conversation off mid-sentence. It does not matter how passionate the debate is or how close the team feels to a consensus. Call time loudly and cleanly.

At that exact moment, take five seconds to capture where the debate stands. You have two operational choices for an unresolved issue:

First, if the problem is not an existential emergency, keep it on the Issues List. It will be prioritized as number 1 at next week's Level 10 Meeting. Often, sleeping on an intense debate gives leadership team members the space they need to reflect, collect real data, and arrive next week ready to resolve it in five minutes.

Second, if the issue is truly critical and waiting seven days will damage customer relationships, revenue, or operations, schedule a dedicated, off-agenda session. Assign a specific owner a To-Do to book a separate sixty-minute working block with only the necessary participants before Friday.

Once that decision is made, transition immediately into the final five minutes: review the weekly To-Dos, confirm any cascade messages that need to flow down to departments, and rate the meeting. Respecting the clock forces your leadership team to sharpen their communication and stop wasting minutes during IDS.