During the Customer and Employee Headlines section of our Level 10 Meeting, our leaders frequently share negative feedback as a headline but then immediately begin explaining the background and telling a story before we can move it to the Issues List. How do we cut off this storytelling and transition the headline directly to IDS without losing the context?

Question

Tyler Smith · Accepted Answer

The five-minute Customer and Employee Headlines section is designed for brief, high-level awareness, not for debate. When a leader starts explaining the backstory of a client issue or an employee complaint, they are engaging in premature problem-solving. This practice drags down the energy of the meeting and wastes valuable time.

To stop this, the facilitator must enforce the one-sentence headline rule. When a leader shares a headline that requires action, the facilitator must interrupt immediately and say, Let's drop that to the Issues List.

Do not allow the leader to explain the context or justify why it is an issue. The headline itself should be captured on the Issues List in five words or less.

For example, if a leader says, Our largest client is upset about our onboarding speed, the facilitator stops them right there and tells the scribe to write, Client onboarding delay, on the Issues List.

The time to explain the context is during the IDS portion of the meeting, when the team has agreed to prioritize that specific issue. If the issue does not make the top three priorities for the day, the backstory was not worth sharing anyway. Keep this section binary and moving fast.