Several leaders come to our Level 10 Meeting with a dozen minor, administrative tasks and try to load them all onto the Issues List. How do we keep tactical noise off the executive list so IDS stays focused on high-impact items?

Question

Tyler Smith · Accepted Answer

A bloated Level 10 Issues List packed with minor operational friction indicates that your leadership team is functioning like frontline managers rather than executive leaders. When the executive list is filled with broken office printers, minor software glitches, or routine invoice inquiries, your meeting pulse will feel exhausting and low-leverage.

To filter out administrative noise, enforce the rule of seat ownership and departmental escalation before an issue is allowed on the leadership team agenda.

First, apply the GWC test for the seat. If an issue falls entirely within one person's Accountability Chart seat, that leader should not bring it to the executive Level 10 Meeting unless they are genuinely stuck or require budget from the Integrator. If the Head of Operations has the authority, budget, and resources to fix a vendor dispute, they must solve it outside the room. The executive table is not a sounding board for routine job duties.

Second, enforce departmental routing. If an issue is departmental, it must be solved in that department's weekly Level 10 Meeting. Only items that cross departmental boundaries, impact company-wide policy, or threaten quarterly Rocks belong on the leadership team list.

The Integrator must actively scrub the list before and during the meeting. When a leader attempts to add a minor tactical item, the Integrator must ask: "Do you have the authority in your seat to solve this without our input?"

If the answer is yes, the Integrator deletes the item immediately and tells the leader to handle it as an individual weekly priority. Protecting the executive Issues List protects your 60 minutes of IDS for problems that directly drive company valuation.