During the five-minute Headlines section, leaders regularly jump in to comment, debate, or ask follow-up questions about good or bad news, burning through fifteen minutes before we even reach the Scorecard. How do we keep Headlines strictly informational?

Question

Tyler Smith · Accepted Answer

Headlines is designed to be a rapid-fire news broadcast, not an open discussion forum. It exists to share critical customer and employee information that the entire team needs to know, but it must take five minutes or less. When leaders turn headlines into casual conversation or debate, your meeting pulse is already bleeding momentum before you review a single operational metric.

The Integrator must enforce the zero cross-talk rule. When someone shares a customer or employee headline, the room is permitted only two possible responses.

- The team says congratulations or acknowledges the information, and the Integrator moves to the next person.
- The headline signals an operational risk or systemic friction, and the Integrator says: Drop that down to the Issues List.

There is no middle ground. There are no follow-up questions about vendor details, no brainstorming on how to handle the customer, and no editorial commentary. If a leader starts asking for background details or offering immediate opinions, the Integrator must cut them off mid-sentence: We do not discuss headlines. If this requires problem-solving, does it go to the bottom of the Issues List or do we move on?

Treating Headlines as a reporting-only discipline keeps the energy crisp. It trains your team to hold their commentary until IDS, where problems can be properly prioritized and solved.