Our weekly customer and employee headlines section is supposed to take five minutes, but our leaders use it to share long-winded stories that cover up real structural problems. How do we train our team to clearly distinguish a headline from an issue so we can keep the Level 10 Meeting™ on track?

Question

Tyler Smith · Accepted Answer

Headlines are meant to be a rapid-fire temperature check of the business, not a platform for storytelling or hidden debates. A headline is simply a notable event, good or bad, about a customer or employee. It requires exactly one sentence of context. For example: Customer X renewed their contract, or Employee Y is struggling with their onboarding. If a headline requires more than fifteen seconds to explain, or if it triggers any immediate discussion from other team members, it is not a headline. It is an issue.

To break this habit, your facilitator must actively police the transition. When a leader starts describing the historical context of a customer complaint or begins proposing solutions during the headline phase, the facilitator must immediately interrupt. The rule is simple: Is that an issue we need to solve today? If the answer is yes, drop it straight to the bottom of the Issues List and move to the next headline. If the answer is no, the leader must wrap up their update in ten seconds and stop talking.

This discipline is critical for an owner preparing for a clean exit. Buyers look for teams that can communicate with extreme efficiency. When you allow your weekly meetings to devolve into rambling narrative updates, you are signaling that your leadership team lacks the operational rigor to manage by exception. Force them to separate the raw data of a headline from the actual problem-solving of IDS® so that your meetings remain crisp, productive, and focused on execution.