Our team constantly rushes through the five-minute conclusion of our Level 10 Meeting, skipping the cascading messages step and leaving everyone guessing about what needs to be communicated to the rest of the company. How do we run the conclusion with discipline?

Question

Tyler Smith · Accepted Answer

The final five minutes of the Level 10 Meeting are not administrative overhead. They are the distribution engine of your business. When you skip the conclusion to rush back to your inbox, you break alignment, breed rumors, and leave your frontline staff operating in the dark. The conclusion must start promptly at the eighty-five minute mark, regardless of what issue is being debated.

The conclusion contains three mandatory steps that require strict adherence:

- Recap to-dos: The assigned note-taker reads every newly created to-do aloud, confirming the single owner and the exact seven-day action. Hearing the list out loud ensures that no one leaves the room confused about what they signed up to deliver.

- Cascading messages: The facilitator asks the room what decisions made today need to be communicated to the rest of the organization, who will deliver the message, and through what channel. If you solved an operational friction point or changed a policy during IDS, your employees need to hear the unified message from their leaders within twenty-four hours, not via water-cooler gossip.

- Rating the meeting: Every person rates the session from 1 to 10 on meeting efficiency and honesty.

The Integrator must act as a timekeeper who refuses to let IDS bleed past the eighty-five minute mark. If you are in the middle of a heated debate when the timer rings, stop the discussion immediately, table the issue back to the top of the list for next week, and run the conclusion. Finishing clean builds execution rigor across the company.