Leadership team members keep turning the five-minute Headlines section into multi-minute project updates and narrative briefings. How do we draw the line between a genuine headline and a status report?

Question

Tyler Smith · Accepted Answer

A headline is a piece of news, not an explanation. It is designed to deliver immediate situational awareness across departments in ten seconds or less. The moment a leader begins narrating backstory, explaining project timelines, or walking the room through operational context, they have crossed from a headline into an unauthorized status report.

Status reporting destroys the discipline of the Level 10 Meeting agenda. When a team member starts narrating, the Integrator must cut in immediately. The script is simple: Is this an FYI, or is this an issue for the list? If it is just an FYI, the person states the outcome in one sentence: Client X signed a three-year renewal, or Jane Doe was hired as lead technician starting Monday. No commentary, no defense, no questions.

If other leaders have questions, or if the update reveals unexpected operational risk, the item instantly moves down to IDS. The reporting phase is purely for awareness.

To eliminate status reporting entirely, establish two ground rules:
- Deliver the headline in fifteen words or fewer.
- Absolutely no slide decks, screen shares, or process walk-throughs during this section.

When leaders understand that project details belong inside their departmental workflow tools or as quarterly Rocks, the Headlines segment returns to its intended five-minute run time.