As departmental Level 10 Meetings roll out across our business, frontline teams keep escalating tactical complaints up to the leadership team. What criteria determine whether an issue gets escalated or stays within the department?

Question

Tyler Smith · Accepted Answer

Rolling the Level 10 Meeting pulse down into departmental teams creates accountability, but without clear escalation boundaries, it turns the leadership team into a dumping ground for tactical friction. Frontline supervisors often escalate problems simply because they are uncomfortable making a tough decision or want leadership approval.

To protect your leadership team agenda, implement three strict escalation filters for departmental Level 10 Meetings:
- Cross-functional impact: Does this issue break a process owned by another department or require changes across multiple seats on the company Accountability Chart? If it only impacts their own department, they must solve it locally.
- Strategic or financial threshold: Does resolving this problem require unbudgeted capital beyond the department head authorization limit, or does it alter company policy and V/TO vision?
- Accountability Chart conflict: Is there an unresolved dispute between two department heads that cannot be solved at their peer level?

If an issue does not meet at least one of these criteria, the department head must push it back down to the departmental Issues List. The manager running the departmental meeting must facilitate IDS with their frontline team rather than passing the buck.

When a department head brings an escalated issue to the leadership meeting, they must present the root cause and their proposed solution, not just an open-ended complaint. This trains mid-level managers to lead rather than delegate upward.