In our weekly Level 10 Meeting, our Integrator tries to facilitate the discussion while simultaneously typing live notes, logging to-dos, and navigating our software, which slows down the meeting pace. Who should actually document the meeting, and how do we eliminate this bottleneck?

Question

Tyler Smith · Accepted Answer

When the Integrator acts as both lead facilitator and administrative scribe, meeting velocity dies. Facilitating a Level 10 Meeting requires intense active listening, reading room dynamics, catching subtle body language, and driving teams through the IDS process. If the facilitator is staring at a screen, typing verbatim sentences, or fiddling with software drop-downs, they cannot hold the room accountable.

The solution is to separate the facilitator role from the scribe role.

Assign a different leadership team member to serve as the scribe, or rotate that administrative duty on a quarterly basis. The scribe is responsible for updating the Scorecard colors, tracking Rock statuses, writing down new issues on the list, and capturing agreed-upon to-dos in the software.

The scribe must follow strict documentation standards to keep the meeting fast:

- To-dos must be captured as short, binary, seven-day action items starting with an active verb, assigned to a single owner.
- Issues must be logged using concise language, usually one short sentence defining the root problem, not a paragraph of narrative context.
- Notes during IDS should be minimal or non-existent. A Level 10 Meeting is a problem-solving session, not a transcription exercise. Diligence and accountability come from clear decisions and assigned to-dos, not meeting minutes.

Freeing the Integrator from the keyboard allows them to focus 100 percent of their energy on managing the clock, pressing the team on tough issues, and keeping the pulse locked at a world-class level.