Our departmental Level 10 Meetings spend the entire IDS portion solving issues that actually belong to other departments or require cross-functional leadership approval. How do we keep departmental teams focused on issues within their own control?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings must operate strictly inside their own sandbox. When frontline teams spend forty minutes complaining about software bugs owned by IT or pricing policies set by executive leadership, they are venting rather than solving. That is not IDS. That is meeting waste.

Enforce a clear boundary rule for every departmental facilitator. A departmental team may only IDS an issue if they own both the root cause and the execution of the solution. If the solution requires a budget change, a process alteration in another department, or an adjustment to the company Accountability Chart, it does not get debated in that room. It gets escalated.

The departmental leader documents the issue clearly, defines the operational impact on their team, and carries it up to the leadership Level 10 Meeting. The departmental agenda then moves immediately to the next item on their own Issues List.

Middle managers often allow external venting because tackling localized failures is uncomfortable. It is much easier to blame marketing for bad leads than it is to address poor outbound call discipline within sales. Train your managers to ask one question the moment a topic is introduced: Do we have the authority and resources in this room to solve this permanently today? If the answer is no, drop it from the discussion, log the escalation, and refocus the team on their own measurables and Rocks.