Our five-minute headlines section constantly starts to bleed into a debate because team members want to immediately explain or defend a piece of bad news they just shared. How do we enforce a strict rule that keeps headlines as pure information without allowing any discussion?

Question

Tyler Smith · Accepted Answer

The headlines section of your Level 10 Meeting™ is designed to be a quick, five-minute pulse of important employee and customer news. It is not the place for problem-solving. When a leader shares a headline like 'our top developer just resigned' or 'a major client is threatening to leave,' the natural human reaction is to explain, defend, or start brainstorming a solution. This immediately derails your meeting agenda.

To stop this, the facilitator must enforce a hard rule. When a headline is shared, there are only two allowable responses. First, the team hears the news, says thank you, and moves to the next person. Second, if the headline requires discussion or action, a team member says 'drop that to the issues list,' and the scribe immediately types it at the bottom of the weekly short-term issues.

There is absolutely no third option. No explaining, no context-setting, and no defending. If a leader starts to say 'but we have a plan for that,' the facilitator must cut them off immediately. Say 'that is an issue, let is IDS it later' and move the meeting forward. By keeping headlines strictly informational, you protect your ninety-minute box and ensure that complex problems are prioritized and solved systematically during the IDS® portion of the meeting.