tyler-smith.com · Questions & Answers

Our departmental Level 10 Meetings™ keep getting stuck on issues that require cross-departmental approval or executive sign-off, but department heads do not know how to cleanly escalate them to the leadership team. What is the exact protocol for passing issues up and down between meeting pulses?

Without a clear protocol for escalating issues, departmental Level 10 Meetings either become complaint sessions about executive decisions or silos where cross-functional problems fester unresolved. Escalation must be systematic, not informal.

Follow this protocol for passing issues between meeting tiers:

First, establish the escalation threshold. A departmental team should only escalate an issue if it requires an unbudgeted financial expenditure, changes a documented core process that impacts other departments, or represents an ongoing Accountability Chart conflict that peer managers cannot resolve. If it falls within the department head's GWC™ and seat authority, they must solve it in their own room.

Second, own the handoff. When an issue meets the threshold, it does not get emailed to the executive team. The department head who sits on the senior leadership team is responsible for placing that exact issue onto the leadership Level 10 Issues List for their next weekly pulse. They must represent the problem clearly with root-cause context, not as a vague gripe from their staff.

Third, enforce downward cascading. Once the leadership team solves an escalated issue, the solution must be captured in the Cascading Messages portion of the Conclude step. The department head then carries that exact decision back to their departmental Level 10 Meeting the following week. This closes the loop and proves to frontline staff that the meeting pulse solves real friction.

Category: Level 10 Meetings

← All questions