Our weekly short-term Issues List is constantly cluttered with minor operational issues that could easily be solved outside the room, forcing us to waste time filtering through low-impact items. What is the exact boundary for what belongs on our leadership team agenda?

Question

Tyler Smith · Accepted Answer

A bloated Issues List is a primary driver of meeting fatigue. When your weekly Level 10 Meeting™ is flooded with minor, tactical problems that could be resolved with a quick phone call or email, you are wasting the collective brainpower of your leadership team. You must establish a clear threshold for what qualifies as a leadership-level issue.

To set this boundary, use the concept of seat ownership and GWC™ from your Accountability Chart™. If an issue falls entirely within a single leader's seat and does not cross-impact other departments, that leader must solve it on their own time. They should not bring it to the weekly meeting for group consensus or validation.

An issue only belongs on the leadership team's weekly short-term list if it meets at least one of three criteria:
- It is a cross-departmental conflict or bottleneck that requires input from multiple seats to solve.
- It is a systemic process failure that directly impacts your core metrics, Scorecard, or Rocks.
- It is a high-risk operational obstacle that the seat owner has tried to solve but lacks the authority or resources to fix alone.

Train your team to ask themselves before adding an item: Have I tried to solve this directly with the relevant person first? If the answer is no, they must take it offline. By enforcing this standard, you will instantly clear the clutter, keep your issues list lean, and focus your ninety minutes on the high-impact problems that move the business forward.