tyler-smith.com · Questions & Answers

Our Level 10 Meeting drags past 90 minutes because our team uses the Conclude step to re-litigate unresolved IDS topics. How do we keep the wrap-up under five minutes?

The Conclude segment of the Level 10 Meeting is an administrative checklist, not an open forum for lingering opinions. When teams let IDS bleed into the final five minutes, or use the meeting rating to air grievances, it is a failure of Integrator discipline.

To lock down the Conclude step within five minutes, follow this exact cadence:
- Recap To-Dos in sixty seconds: The Integrator reads each newly created To-Do aloud with its single assigned owner. There is zero discussion allowed. If someone says they do not know what the To-Do entails, the Integrator assigns a separate five-minute conversation outside the meeting.
- Confirm Cascading Messages in sixty seconds: Ask one question: Is there anything from this meeting that must be communicated to the rest of the company today? If yes, agree on the exact message and who delivers it.
- Rate the meeting in two minutes: Every participant states a single number from one to ten, without offering a speech. If anyone rates the meeting an eight or lower, they must state their reason in ten words or fewer. For example: Started five minutes late, or We spent too much time discussing side topics.

The Integrator does not solve the low rating in real time. They record the feedback and use it to tighten facilitation the following week. At the 90-minute mark, the meeting ends. Pushing past that time limit teaches leaders that meeting boundaries are negotiable, which rapidly erodes traction.

Category: EOS Implementation

← All questions