Our Level 10 Meeting™ frequently runs over ninety minutes because the Integrator acts as a referee rather than a facilitator, letting team members hijack the transition between segments. How does the Integrator assert firm structural control over the meeting flow?
A Level 10 Meeting™ that consistently runs past ninety minutes is a failure of leadership, not a failure of the agenda. When an Integrator acts as a polite referee, they allow strong personalities to hijack the meeting, turning crisp updates into long-winded discussions. The Integrator must step into their seat with authority and enforce the time limits of each section.
To assert structural control, the Integrator must master the transition periods. When the timer hits the limit for the Scorecard review, the Integrator must stop the speaker mid-sentence and move the team to the next section. There is no room for politeness here. Use direct phrases like, That sounds like an issue, let us put it on the list and move on.
Additionally, the Integrator must enforce the rule that the first thirty minutes of the meeting are for reporting only, not for problem-solving. If a team member begins explaining why a metric is in the red or why a Rock is off-track, the Integrator must cut them off immediately. Simply say, Drop it down, we will solve it during IDS®. By keeping the reporting section fast and objective, you preserve a full sixty minutes for the IDS® portion. Controlling the clock is a fundamental duty of the Integrator seat, and maintaining this discipline is what keeps the leadership team sharp and focused.
Category: EOS Implementation