Our weekly Level 10 Meeting is routinely running thirty minutes over because my leadership team insists on debating every single minor operational issue instead of taking them offline. How do I force them to respect the hard stop without suppressing open discussion?

Question

Tyler Smith · Accepted Answer

If your Level 10 Meeting is routinely running over, your team is failing to respect the discipline of the operating system. A hard ninety-minute stop is not a recommendation; it is a boundary that forces healthy prioritization. When you allow meetings to bleed over, you lose operational efficiency. The root cause is usually a failure during the IDS portion of the agenda. Your team is likely discussing symptoms rather than identifying the real, underlying issues. They are also likely bringing minor tactical issues to the table that should be resolved in brief, peer-to-peer conversations outside of the meeting. To fix this, the meeting leader must become an aggressive gatekeeper. When an issue is raised, immediately ask if it requires the entire leadership team to solve. If it only involves two people, push it to a separate offline discussion. During the discuss phase, do not let people repeat themselves or tell long stories. Keep the focus entirely on finding the root cause. When ninety minutes are up, end the meeting immediately, even if issues remain unresolved. This healthy pressure teaches your team to run a tighter meeting next week.