Leaders on our team treat the weekly Issues List as a substitute for direct communication, saving up simple two-person operational friction points all week instead of resolving them immediately peer-to-peer. How do we stop the Level 10 Meeting from becoming a dumping ground for everyday communication breakdowns?

Question

Tyler Smith · Accepted Answer

The Level 10 Meeting™ Issues List is intended for systemic organizational hurdles, cross-functional dependencies, and strategic roadblocks. It is not an administrative escrow account where department heads stash interpersonal annoyances or basic operational coordination issues until Tuesday morning.

When executives stockpile minor friction points for the weekly meeting, they delay execution by up to six days and waste sixty minutes of leadership team horsepower on issues that required a five-minute phone call.

The Integrator must filter the Issues List before and during the meeting using a simple operational test: "Is this an enterprise issue, or is this a two-person coordination issue?"

If an item only involves the Sales Director and the Operations Director coordinating an invoice handoff, the Integrator should challenge it immediately: "Why is this on the leadership agenda? Have the two of you discussed this directly?"

If the answer is no, strike the issue from the list on the spot. Assign a single To-Do: "Sales Director and Operations Director meet for ten minutes today to resolve invoice process."

Teach your leadership team the rule of direct communication: if an issue can be resolved peer-to-peer between two individuals, waiting for the Level 10 Meeting is operational negligence. The leadership room should only debate issues that require collective intelligence, impact company-wide Rocks, or remain stuck after direct communication has failed. This keeps the meeting lean and elevates enterprise speed.