Our Level 10 Meeting gets bogged down because team members drop vague, multi-paragraph paragraphs onto the Issues List right before the meeting. What standard must an Integrator enforce for teeing up an issue for rapid IDS?

Question

Tyler Smith · Accepted Answer

When team members write novels on the Issues List or drop ambiguous phrases like client communication into the queue, your Level 10 Meeting™ wastes twenty minutes just figuring out what the conversation is about.

The Integrator must establish a firm standard for how issues are submitted. Every issue added to the list must follow a simple three-part format: the owner, the title, and a single-sentence statement of the problem.

Enforce these rules for issue entry:
- The title must be three words or fewer. Use clear labels like Pricing Variance, Warehouse Bottleneck, or Hiring Capacity.
- The submitter must identify the specific seat on the Accountability Chart that owns the issue.
- The problem statement must define the exact variance between expectation and reality in one sentence. For example: Marketing delivered 40 leads against our goal of 80 this week, or Customer Onboarding averaged 21 days instead of our 14-day SLA.

Background details, email chains, and proposed solutions do not belong on the agenda document. When the team prioritizes an item as number one, two, or three during IDS®, the owner of the issue gets sixty seconds to state the facts. They do not get ten minutes to give an emotional monologue.

By forcing team members to distill their thoughts before speaking, the Integrator eliminates ninety percent of meeting posturing. Clear, concise issue identification allows the leadership team to move straight to discussing root causes and deciding on concrete seven-day To-Dos.