Since launching departmental Level 10 Meetings, our supervisors are kicking frontline operational issues straight up to the leadership team's Issues List instead of resolving them locally. How do we stop departments from using their meeting as an escalation chute?

Question

Tyler Smith · Accepted Answer

When frontline managers push every issue upward, it is usually a symptom of two problems: unclear authority on the Accountability Chart or a lack of problem-solving confidence inside the departmental Level 10 Meeting. A departmental meeting pulse exists to solve frontline issues at the frontline level. If those issues bypass middle management and land on the leadership team agenda, the business will remain trapped in owner-dependent, tactical firefighting.

To stop this flow, the leadership team must enforce a strict issue escalation filter. Before any department head brings an issue from their team meeting up to the leadership Level 10 Meeting, they must answer three specific questions:

- Does this issue require a change to the core V/TO vision, budget, or quarterly Rocks?
- Does this issue impact another department that cannot be resolved peer-to-peer between the respective leaders?
- Has the departmental team actually attempted to IDS the issue and hit a genuine structural barrier?

If the answer to those questions is no, the Integrator must reject the issue and send it back down. The department head must facilitate IDS with their own team and make the call.

Leadership teams often accidentally encourage upward dumping because they jump in and solve frontline problems out of habit. That habit must be broken. When an Integrator or owner solves a frontline process issue, they rob the departmental manager of authority and train them to be helpless. Force the departmental manager to take ownership, decide the fix within their seat, and only escalate true cross-departmental or strategic bottlenecks.