We have cascaded Level 10 Meetings™ down to our departmental teams, but we now have issues getting stuck in a vacuum where middle managers solve departmental symptoms while the root leadership issues go unaddressed. How do we build a clean system for cascading issues up and down our meeting structure?

Question

Tyler Smith · Accepted Answer

Cascading Level 10 Meetings™ down to your departmental teams is critical for scaling, but it often creates communication silos. When issues are solved in isolation, middle managers end up treating local symptoms while the true root causes, which often cross departmental lines, remain untouched. You need a transparent system for routing issues up and down your Accountability Chart.

To do this, establish a clear rule for when an issue must be escalated to the leadership team's Level 10 Meeting™. If a departmental issue cannot be resolved within that department, requires resources from another division, or impacts the company's overall Rocks or V/TO®, it must be sent up. The departmental manager simply moves that item to the leadership team's issues list.

Conversely, the leadership team must run a tight cascading message process. When a decision is made during the leadership's IDS® session that impacts a department, it must be noted in the cascading messages section of the wrap-up. This ensures the departmental managers receive the decision and can add it to their own Level 10 Meeting™ agenda for implementation.

Do not let issues linger in a middle-management vacuum. Keep the communication lines clear, use your Accountability Chart to define who owns the resolution, and ensure that departmental lists are regularly purged of high-level strategic debates. This keeps local execution sharp while keeping leadership informed.