Our Integrator feels overwhelmed managing the operational debate while also running the Level 10 Meeting agenda, and has suggested rotating the facilitator role weekly among the leadership team. Does rotating the facilitator work in EOS?

Question

Tyler Smith · Accepted Answer

Rotating the facilitator is a common trap that usually degrades meeting discipline. The Level 10 Meeting requires firm, consistent enforcement of the EOS process: cutting off tangent drift, enforcing the ninety percent To-Do standard, policing the segue, and driving IDS to definitive solves. When you rotate the role weekly, meeting quality drops to the lowest common denominator of whoever is holding the timer.

In EOS, the Integrator is accountable for running the cadence and ensuring organizational traction. That accountability naturally includes facilitating the weekly leadership team Level 10 Meeting. If your Integrator is struggling, it is almost never because facilitation is inherently impossible; it is because they are trying to facilitate and dominate the debate simultaneously.

To fix this dynamic without rotating the facilitator role, separate facilitation from record-keeping. The Integrator should facilitate the meeting, but assign another team member, such as an operational coordinator or a detail-oriented executive, to serve as the scribe. The scribe manages the software, logs To-Dos, moves issues, and keeps the visual timer running.

This frees the Integrator to observe the room, watch body language, keep the agenda on schedule, and direct traffic during IDS. When the Integrator needs to contribute their direct functional opinion on an issue, they should verbally announce the shift: Stepping out of facilitator mode for a minute, here is what Operations needs.

If the Integrator still cannot manage the room, it points to a skill gap or a lack of authority on the Accountability Chart. Handing the gavel to a different leader every week merely masks the Integrator's facilitation weakness instead of resolving it.