When departmental Level 10 Meetings try to solve issues during IDS, frontline supervisors often spin their wheels attempting to fix company-wide policies or cross-functional systems that they have no authority to change. How do mid-level managers keep departmental IDS focused strictly on local execution?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings collapse when frontline supervisors confuse operational execution with strategic architecture. A customer support team cannot redesign company pricing policy during their weekly pulse, and an operations team cannot unilaterally alter sales commission structures.

Departmental facilitators must train their teams on the boundary of their Accountability Chart seats. When an issue is raised during departmental IDS, the manager must immediately ask one filtering question: 'Do we possess the authority, resources, and accountability within this room to permanently solve this root cause?'

If the answer is yes, proceed with IDS. If the answer is no because the issue touches company-wide policy or cross-departmental systems, halt discussion immediately. Do not spend forty minutes venting about corporate rules.

The manager then directs the team to package the issue for escalation. Escalating an issue does not mean dumping a vague complaint upward. The frontline team must define the operational symptom, document specific ground-level data showing the business impact, and submit it to their department head.

The department head then carries that clean, data-backed issue into the executive Level 10 Meeting. This keeps departmental IDS focused entirely on what frontline supervisors actually control: executing standard operating procedures, hitting weekly Scorecard numbers, and delivering on their seven-day To-Dos.