Our weekly Level 10 Meeting routinely exceeds 90 minutes because our Integrator lets people tell long backstories and debate side topics during IDS. How do we establish the conversational discipline needed to solve issues fast and finish on time?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting that consistently blows past 90 minutes is failing because of poor facilitation, not an overload of issues. When meetings run long, leadership teams develop meeting fatigue, disengage from the process, and rush through the final items. The culprit is almost always unstructured storytelling during the IDS portion.

The Integrator must ruthlessly police the conversation. When an issue is selected from the Issues List, the person who raised it must state the problem in one or two clear sentences. They must not provide five minutes of context, justify their actions, or assign blame. If they begin detailing background history, the Integrator must cut in and ask: What is the specific problem we need to solve right now?

Keep the discussion focused strictly on root causes and solutions. Watch for rabbit holes where two team members debate operational minutiae that does not require the entire leadership team. When that occurs, the Integrator must step in, assign those two individuals an offline To-Do to resolve the detail, and pull the room back to the core issue.

Enforce the hard stop. When minute eighty-five arrives, the Integrator must cut off whatever discussion is underway, drop the unresolved issue back to the list, and execute the five-minute conclude step. Knowing that the meeting ends at ninety minutes no matter what forces the team to abandon discursive monologues and speak with brevity.