Leaders on our team frequently submit giant, multi-headed topics to our Issues List, like cross-departmental communication breakdown, which leads to rambling discussions that never produce clear action. How do we force leaders to break down bundled issues before IDS®?

Question

Tyler Smith · Accepted Answer

Vague, bundled issues kill meeting momentum. When someone drops a massive topic like operational communication onto the Issues List, the team spends thirty minutes swirling in abstract philosophy and storytelling without identifying a single actionable cause.

The Integrator must reject bundled issues before the discussion begins. Apply a strict rule: An issue must be stated in one clear sentence that identifies the specific person, process, or metric that failed.

When a leader presents a compound issue, stop the room and make them isolate the components:
- What specific breakdown happened this week that prompted you to list this?
- Which two seats on the Accountability Chart are misaligned?
- What metric or customer was impacted?

If the topic actually contains three separate problems, split it into three standalone line items on the Issues List. For example, change communication breakdown into three distinct items: Sales not updating deal stages in the CRM, Operations missing handoff deadlines, and Warehouse inventory discrepancy.

Once the issues are separated, the team can vote on their true priority. Solving three tightly defined problems takes twenty minutes and produces clear, binary To-Dos. Debating one bundled, generic topic wastes an hour and solves nothing.