Our departments run their own Level 10 Meetings now, but unresolved departmental issues either disappear or get dumped onto the leadership team's Issues List without context. How do we cleanly escalate issues between organizational tiers?

Question

Tyler Smith · Accepted Answer

Departmental Level 10 Meetings require a strict filter to prevent issues from either falling into a black hole or clogging the executive table. An issue should only escalate from a department meeting to the leadership team if it meets one of three criteria: it requires cross-departmental alignment, it exceeds the department head's budgetary or decision-making authority, or it represents a structural break in the company's operating model.

When a departmental issue qualifies for escalation, the department head owns it. They do not casually mention it in chat or send a vague memo. They enter it directly onto the leadership Level 10 Meeting Issues List as their issue, defined by a single sentence stating the root problem and the required decision.

The same rule applies in reverse. When the leadership team identifies an issue during IDS that belongs entirely within sales, operations, or finance, the Integrator must redirect it down to that department's Level 10 Meeting. The department head adds it to their team's Issues List and reports back once resolved.

The leadership pulse exists to remove company-wide bottlenecks, not to solve tactical friction that frontline teams have the authority to fix. Enforcing this boundary builds accountability in middle management and protects the leadership team's sixty minutes of IDS for true enterprise priorities.