Our team constantly clogs the Issues List with simple informational updates, policy announcements, or minor client wins that require zero debate or decision-making. How do we train the team to distinguish what belongs in Headlines versus what belongs on the Issues List before the meeting starts?

Question

Tyler Smith · Accepted Answer

A headline is an announcement that requires zero discussion, zero debate, and no collective decision. An issue is an obstacle, an opportunity, or a broken process that requires the leadership team to Identify, Discuss, and Solve (IDS®). When teams mix these up, the Issues List bloats and executive time gets burned listening to monologues.

The Integrator must establish a strict filter during the Headlines section. A customer or employee headline gets stated in one or two sentences. If the update requires nothing from the rest of the room other than awareness, it stays a headline. The moment anyone asks a question that requires collective problem solving, process changes, or resource reallocation, the Integrator cuts the conversation short and drops it to the bottom of the Issues List.

To stop team members from dropping informational notices onto the Issues List prior to the meeting, enforce a simple prerequisite. Before any item is added to the Issues List, the owner must be able to state the issue in one clear sentence that specifies the gap between expectations and reality. If an item does not have an owner, a clear problem statement, or a required decision, it does not belong on the agenda. It belongs in a company-wide communication channel, an email, or the five-minute Headlines block.