We have successfully implemented Level 10 Meetings at the leadership level, but as we roll them out to departmental teams, they are degenerating into status updates rather than issue-solving. How do we keep departmental L10s sharp?

Question

Tyler Smith · Accepted Answer

This is a common friction point when cascading the Level 10 Meeting pulse down the Accountability Chart. Departmental teams often default to status updates because discussing what they did is easier and safer than identifying and solving root-cause problems. They treat the meeting as a reporting mechanism for their manager rather than a tool for peer-to-peer execution.

To fix this, you must train your department heads to be strict facilitators who understand the difference between reporting and solving. First, enforce the binary nature of the reporting section. The Scorecard, Rock Review, and To-Do List must be covered in less than fifteen minutes. If a metric is red or a Rock is off track, the only acceptable response is to drop it to the Issues List. No explanations, no storytelling, and no status reports are allowed during this portion.

Second, ensure the department's short-term Issues List is populated before the meeting starts. If the list is empty, the facilitator should pull issues directly from the red Scorecard metrics or off-track Rocks.

Third, focus on the IDS process. Departmental issues are often highly tactical, but they still require identifying the root cause. If team members are hesitant to speak up, the facilitator must ask open-ended questions to draw out the real friction points.

Finally, audit these meetings. As the Integrator, you should occasionally sit in on departmental Level 10 Meetings as an observer. Do not run the meeting, but provide direct, constructive feedback to the manager afterward on their facilitation and their ability to keep the team focused on solving issues permanently.