We struggle to draw a clear line between a quick Customer/Employee Headline and a major issue that needs to go on the IDS list, which means our five-minute headlines section constantly morphs into a troubleshooting session. How do we keep this section strictly informational?

Question

Tyler Smith · Accepted Answer

The headlines section of your Level 10 Meeting™ is meant to be a quick, five-minute pulse of the company's human element. It is a broadcast, not a discussion. A headline is a completed event, a win, or a notable change, such as a client signing a contract or an employee beginning parental leave.

When a leader shares a headline that requires any action, decision, or debate, it is no longer a headline. It is an issue. For example, if a department head says a major client is threatening to leave, that is not a headline. That is a red-alert operational issue.

To maintain this boundary, the facilitator must intervene immediately. The moment a headline sparks a follow-up question or an explanation, the facilitator must say, "That sounds like an issue. Let's drop it to the bottom of the short-term Issues List." Do not allow the presenter to explain. Do not allow other team members to offer advice.

By immediately logging the item on the Issues List, you respect the agenda. The presenter feels heard because their concern is captured, but the team is protected from premature discussion. Train your team to recognize that if a headline requires more than two sentences to explain, or if it demands a response from anyone else in the room, it belongs in IDS® later in the meeting.