Our leadership team constantly confuses customer and employee headlines with operational issues, turning five minutes of reporting into twenty minutes of storytelling. How do we draw the line?
Headlines exist to share critical information across departments, not to solve operational problems. The agenda allocates exactly five minutes for this section. When leaders bring storytelling, emotional reactions, or unsolicited advice into headlines, they steal valuable time from IDS.
The rule is straightforward: a headline is a one-sentence factual update about a key customer or employee. You state the fact, and nothing more. For example, you say that a key enterprise account renewed for three years, or that your head of engineering submitted two weeks notice. There is no background story, no explanation of why it happened, and no spontaneous discussion.
The Integrator must act as a strict gatekeeper. The moment a leader shares a headline and starts explaining their action plan, the Integrator must cut in and ask one question: Is this just an awareness item, or is it an issue for the list? If it requires action, debate, or cross-departmental coordination, write it down on the Issues List immediately and move to the next person. Do not allow a single follow-up question.
Remind your team that dropping a headline onto the Issues List does not mean it is a crisis. It simply means it requires discussion, and discussion belongs exclusively in the final sixty minutes of the meeting. Keep reporting purely informational, kill the context, and protect your problem-solving block.
Category: Level 10 Meetings