When cascading Level 10 Meetings down to department teams like sales and operations, managers often turn the 60 minutes of IDS into superficial project status updates. How do we teach departmental teams to uncover and solve real root issues?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings fail when middle managers mistake the pulse for an administrative status report. Department heads are often conditioned by corporate habits to present polished updates rather than expose operational vulnerabilities. If an operations or sales team spends sixty minutes reviewing ongoing work instead of identifying, discussing, and solving problems, the meeting is wasting company capital.

To break this habit, the leadership team must enforce the strict boundary between reporting and IDS. The first twenty-five minutes of the meeting are for reporting: Scorecard numbers, departmental Rocks, Headlines, and To-Dos. If an item is off track, nobody is permitted to explain why or deliver a status briefing during that window. It simply gets dropped to the Issues List with a clear, concise title.

When the team arrives at IDS, the departmental facilitator must force prioritization. The team selects the top three issues and attacks issue number one. If managers claim they have no issues to solve, look directly at their departmental Scorecard and Rock completion. If targets are missed but the Issues List is empty, the team is hiding reality.

Teach departmental leaders that an empty Issues List is not proof of operational excellence. It is proof of fear or lack of standards. Demand that every off-track measurable generates a corresponding issue, and train managers to solve root causes so problems do not recur.