Our leadership team keeps dropping minor operational reminders and administrative requests onto the Level 10 Issues List, which crowds out real business bottlenecks during IDS. How do we screen out administrative noise before the meeting?

Question

Tyler Smith · Accepted Answer

When a leadership team clogs the Level 10 Issues List with minor administrative chores, FYIs, and transactional tasks, the meeting loses its power. The Issues List exists to solve structural obstacles, remove friction, and capitalize on business opportunities, not to serve as an executive bulletin board.

To purge task dumping, the Integrator must establish a strict filter before any item is added to the list. An item is only an IDS® issue if it meets at least one of three criteria:
- It is an off-track Scorecard metric or Rock.
- It requires cross-departmental alignment or consensus from two or more leadership team members.
- It represents a systemic obstacle threatening quarterly priorities or company culture.

If a department head wants to inform the team that the office carpet will be cleaned on Friday, that is a one-sentence Headline, not an issue. If someone needs an approval from the finance director, that is a quick direct message or a one-on-one operational interaction outside the room, not a topic for seven executives to debate.

During the meeting, the moment an issue is introduced, the Integrator should ask: "Is this a leadership-level issue, or is this a two-person conversation?" If it is a two-person conversation, the Integrator cuts off discussion immediately and creates a single To-Do for those two individuals to talk after the meeting. Keep the Issues List reserved for high-impact problems.