Our Integrator handles facilitation, manages the meeting timer, and types out notes and To-Dos in our software all at once, which makes our Level 10 Meetings choppy and slow. How should these meeting roles be divided to keep IDS sharp?
Expecting your Integrator to facilitate healthy debate, enforce strict timekeeping, and type detailed notes into your software simultaneously is a recipe for terrible meetings. When the facilitator is staring at a screen trying to capture notes, they lose eye contact with the room, miss non-verbal tension, and fail to catch rabbit trails before they eat ten minutes.
Facilitation requires complete presence. The Integrator must be observing the room, managing emotional energy, pushing the team to identify root causes, and keeping the discussion focused on a single issue at a time.
To fix this friction, separate the roles.
Keep the Integrator as the facilitator. Their only focus during IDS should be guiding the team through Identify, Discuss, and Solve.
Appoint a dedicated scribe from the leadership team. This person is responsible for managing the software, updating Scorecard numbers, logging newly created issues, and typing out clear To-Dos with designated owners and due dates. The scribe can be rotated quarterly or assigned permanently to a detail-oriented leader who enjoys operational documentation.
Assign the timekeeper role to someone else, or use an automated visual timer visible to everyone in the room.
When your Integrator is freed from keyboard duty, they can hold leaders accountable, challenge superficial root causes, and keep the team moving at pace. A clean division of labor transforms a clunky, sluggish meeting into an intense, high-output working session.
Category: Level 10 Meetings