Our leadership team consistently rushes through the Conclude step of our Level 10 Meeting and skips the cascading messages bullet entirely, which leads to rumors and misaligned communication with the rest of the company. How do we make the cascading messages discipline stick?
When a meeting runs behind schedule, the Conclude section is usually the first casualty. Teams slap a hurried rating on the meeting and sprint out the door. Skipping cascading messages creates a dangerous vacuum where frontline employees receive fragmented, second-hand information, fueling gossip and misalignment.
The Conclude block requires five dedicated minutes. If your meeting is scheduled for ninety minutes, IDS must stop at minute eighty-five, regardless of whether you are in the middle of a heated discussion. The Integrator must be ruthless about calling time.
Cascading messages requires answering one focused question: What, specifically, needs to be communicated from this meeting, to whom, through which channel, and by when?
Not every meeting produces a cascading message. In many weeks, the answer is nothing. But the question must be asked aloud every single week.
When there is a decision, policy change, personnel shift, or strategic update that impacts the organization, document it explicitly:
- The exact message: Agree on the precise wording in the room so every leader tells the same story.
- The audience: Specify whether it goes to the entire company, departmental managers, or a specific client-facing team.
- The messenger and medium: Assign one owner to deliver it via email, Loom video, or at the next all-hands meeting.
Finally, link that communication directly to a weekly To-Do. If an executive is tasked with cascading a message to their department, it becomes an official To-Do on the board due within seven days. When you hold leaders accountable to communicating decisions with the same rigor you hold them to hitting revenue numbers, alignment problems disappear.
Category: Level 10 Meetings