Our leaders are using the Customer/Employee Headlines section of our Level 10 Meeting™ to share good news that actually masks major underlying operational issues. How do we draw the line between a genuine headline and a hidden issue that needs to be on the list?

Question

Tyler Smith · Accepted Answer

Customer/Employee Headlines are meant to be quick, one-sentence updates to keep the team connected. They are not a place to hide bad news in a wrapper of good news. When a leader says a client is happy but then mentions we had to pull triple overtime to deliver, that is not a headline. That is an operational red flag.

The facilitator must immediately capture the operational strain and move it to the short-term Issues List. Do not let the team discuss it during the headlines section. Say, that sounds like a capacity issue, so let us put it on the list for IDS® later in the agenda.

Train your team to separate the human update from the structural flaw. Keep the headlines to clean, simple facts. If a headline requires more than two sentences of explanation, it is automatically an issue. This keeps the meeting moving and ensures you solve the real root cause during IDS®.

By enforcing this boundary, you stop meeting waste and prevent critical operational bottlenecks from being swept under the rug. This level of clarity is vital to build a healthy, scalable business.