During the five-minute People Headlines section of our Level 10 Meeting, our team constantly derails into storytelling and problem-solving instead of dropping the headline and moving on. How do we keep customer and employee headlines purely informational without turning them into premature debates?

Question

Tyler Smith · Accepted Answer

The reporting track of the Level 10 Meeting exists to broadcast information, not to solve problems. People Headlines is allocated five minutes for a specific reason: to share customer and employee wins or critical alerts across departments. When teams start dissecting a customer complaint or celebrating a new hire with a fifteen-minute narrative, the meeting collapses before IDS even begins.

The facilitator must set a strict standard for what constitutes a headline. A valid headline is a single sentence delivered without editorializing. It sounds like: John Doe submitted his two-week notice in operations. Or: ABC Corporation signed a three-year contract renewal. That is the entire update.

Enforce two rigid facilitation rules to kill conversational drift:
- Cut off any story that exceeds thirty seconds. The facilitator must intervene immediately: Is there an issue here, or is this just an update?
- If the headline requires action or discussion, the facilitator drops it directly to the bottom of the Issues List with a one-to-three-word title and cuts the conversation off instantly.

Do not allow the team to debate whether the event was fair, how it happened, or what steps need to be taken next. Drop it to the list, assign an owner, and move to the next person. Your ninety minutes will constantly run out if you let reporting slide into early problem-solving.