Our team members frequently bring ambiguous rumors, employee venting, or vague customer complaints into the Headlines section. What exact test determines whether a headline belongs in the meeting at all or immediately becomes an issue?

Question

Tyler Smith · Accepted Answer

Customer and People Headlines exist strictly to broadcast material facts across departments. They are not an open forum to air gripes, share hallway gossip, or seek emotional validation.

Apply a simple binary filter to any headline:
- Is this news purely informational, praise-worthy, or a standard operational milestone that other departments simply need to be aware of? If yes, it is delivered in ten seconds, acknowledged, and you move to the next person.
- Does this piece of news require an action, a decision, a policy change, or cross-departmental coordination? If yes, it is not a headline. It drops straight to the bottom of the Issues List as a new issue, with zero discussion allowed during the reporting pulse.

The Integrator must actively police the language during this five-minute segment. If someone starts with phrases like "I am concerned that" or "We need to talk about," cut them off immediately. Say: "Headline only. Do you want that on the Issues List, yes or no?"

If the answer is yes, record the issue title, assign an owner, and keep the reporting pulse rolling. If the team member cannot articulate a specific issue, the item is dismissed. This operational boundary stops vague rumors from polluting your meeting and forces leaders to translate vague complaints into clear, actionable business problems.