During the Level 10 Meeting, our facilitator gets pulled into solving the problems instead of holding the team to the agenda, which ruins our pacing. How do we keep the facilitator focused strictly on managing the meeting framework rather than participating in the debate?

Question

Tyler Smith · Accepted Answer

When your facilitator drops the whistle to play in the game, your meeting pacing collapses. This usually happens because the person leading the meeting is also the most operationally vocal person in the room, typically the Integrator. While the Integrator naturally facilitates, they must separate their role as meeting quarterback from their role as a leadership seat holder.

The first step is to establish a hard rule: the facilitator must remain an objective gatekeeper of time and process. If they need to participate heavily in a specific IDS debate, they should explicitly state that they are stepping out of the facilitator role for a moment, state their piece, and then step back in. This verbal cue signals to the team that they must help keep the clock.

Alternatively, you can assign a co-facilitator or a timekeeper whose sole job is to call out pacing. When a discussion begins to loop or drift, this person's only responsibility is to say that the team is off track or running out of time. If the facilitator cannot remain neutral, look at your Accountability Chart and see if another leader who GWCs the role can take over the facilitation. This keeps the meeting objective and ensures that your weekly ninety minutes are spent solving critical issues rather than chasing rabbit trails.