Members of our leadership team frequently use the People and Customer Headlines section to float soft complaints or passive-aggressive rumors without officially logging them as issues. How do we stop this backchannel storytelling and force these items straight onto the Issues List?

Question

Tyler Smith · Accepted Answer

The Headlines section of the Level 10 Meeting agenda exists solely for rapid awareness, not editorial commentary or passive venting. It should take no more than five minutes total. A headline is a binary announcement: a key hire joined, a customer renewed, an employee went on leave, or an account cancelled. If there is no action required from the room and no systemic breakdown, it stays a headline.

When a leader drops a headline that contains an underlying frustration, rumor, or veiled critique, the facilitator must cut off the commentary instantly. Do not let them explain the context or test the waters. Ask one direct question: Is that an issue for this team to solve today?

If the answer is yes, instruct the scribe to drop it directly onto the Issues List with a clear, objective topic name. If the leader says no, cut the discussion off immediately with no further remarks allowed. If the leader claims they just wanted to bring awareness to a recurring frustration, the rule is simple: awareness without action is company gossip. Gossip has no place in the Level 10 Meeting pulse.

For teams preparing for an acquisition or clean exit, this discipline is vital. Prospective buyers evaluate leadership efficiency and cultural hygiene. A team that uses headlines to drop hints rather than owning issues directly signals passive leadership and poor accountability. Enforce this standard: state the fact, state whether it is an issue, and move to the next person.