Our Integrator spends the first fifteen to twenty minutes of our Level 10 Meeting reviewing previous meeting notes, reading email threads, and rehashing background on unresolved items before getting to IDS. How do you eliminate this administrative drag?

Question

Tyler Smith · Accepted Answer

A Level 10 Meeting is an operational engine, not a history lesson. Spending twenty minutes rehashing past context, reading background documents, or reviewing old minutes drains the energy in the room and steals time directly from solving high-priority issues during IDS.

The Level 10 Meeting agenda is specifically engineered to prevent administrative drag. The first twenty-five minutes must follow a strict, rapid-fire sequence:
- Good News Segue: 5 minutes.
- Scorecard: 5 minutes. Say on track or off track only.
- Rock Review: 5 minutes. Say on track or off track only.
- Customer and Employee Headlines: 5 minutes. Brief news only.
- To-Do List: 5 minutes. Say done or not done only.

Meeting notes should not be read aloud. In fact, comprehensive meeting minutes are unnecessary in EOS. The only documentation generated during a Level 10 Meeting is the updated Scorecard, the binary status of Rocks and To-Dos, and the written decisions or new To-Dos created during IDS.

To eliminate background rehashing, enforce pre-meeting discipline. Any data, financial report, or proposal required for IDS must be attached to the issue in your meeting software or sent at least 24 hours prior. Leaders must read the context beforehand.

When the room reaches IDS, the issue owner states the issue in one or two sentences: What is the specific problem, and what does success look like? No background monologue is permitted. If someone begins reading historical context, the Integrator must cut them off immediately: What is the core issue today?