During the five-minute customer and employee headlines section, our leaders keep sharing minor, day-to-day status updates about their departments instead of high-level company news. How do we draw a hard boundary between a true headline and a boring status update?

Question

Tyler Smith · Accepted Answer

The headlines section of your Level 10 Meeting™ is designed to share major, high-level organizational updates that impact the team, not to serve as a weekly status report for individual departments. When leaders share minor updates, it drains the meeting's energy and eats into your valuable problem-solving time.

To fix this, define a headline with a simple rule: a headline must be a significant, company-wide piece of news regarding a client or employee that the rest of the leadership team needs to know. Examples include a major client signing, an employee resignation, a significant customer complaint, or a major system outage. If the update does not directly affect how other departments run or require immediate awareness, it is not a headline.

If a leader begins sharing a detailed status update, the facilitator must interrupt immediately. Use a direct phrase like: That sounds like a departmental update rather than a leadership headline. If there is a problem there, do we need to drop it to the issues list, or can you handle it within your department?

Keep this section limited to five minutes total. By enforcing a hard time limit and stopping status reports on the spot, you force your team to filter their updates beforehand. Real organizational alignment comes from solving systemic issues during IDS®, not from listening to polite departmental summaries during the first ten minutes of the meeting.