Our Level 10 Meeting always hits the 85-minute mark while we are still deep in the third issue, causing us to skip the conclude section entirely. Why is shortchanging the wrap-up so destructive, and how do we enforce the hard stop?

Question

Tyler Smith · Accepted Answer

Skipping the conclude section of the Level 10 Meeting is the fastest way to turn a ninety-minute working session into an expensive rumor mill. When you blow past the eighty-five-minute mark without wrapping up, three critical things fail: To-Dos go unconfirmed, cascading messages get forgotten, and meeting quality deteriorates without feedback.

The conclude section takes exactly five minutes, but it provides the glue for the entire week of execution.

The Integrator or meeting facilitator must enforce an ironclad rule: at minute eighty-five, whatever discussion is happening in IDS stops immediately. It does not matter if the team is in the middle of a sentence or close to a breakthrough. You push the remaining issue back down to the Issues List for next week or assign an owner a discovery To-Do to gather facts.

During the final five minutes, execute three steps without exception:
- Recap To-Dos so every individual verbally confirms their assigned action items and due dates.
- Determine cascading messages by asking what information needs to be communicated to the rest of the company and who owns delivering that message.
- Rate the meeting from one to ten, demanding that anyone rating under an eight state their specific reason so the team can self-correct next week.

A meeting that ends without clean To-Dos and aligned messaging guarantees that execution stalls until the next session. Protect the final five minutes at all costs.