During the Customer/Employee Headlines segment of our Level 10 Meeting™, our team members consistently drop positive news that actually hides a deeper systemic issue, or they bring up a headline that needs immediate problem-solving but we fail to migrate it to the Issues List. How do we draw a hard operational line and smoothly transfer these inputs into the IDS® block?

Question

Tyler Smith · Accepted Answer

The Customer and Employee Headlines segment of your Level 10 Meeting™ is a five-minute rapid-fire reporting block, not a discussion block. The primary failure here is when a leader shares a headline, such as a major client complaining about delivery, and the team immediately starts diagnosing the problem. To fix this, you must build a strict cognitive firewall between reporting a headline and solving the underlying operational breakdown. The rule is simple: you have thirty seconds to state the headline. If it requires more than a simple sentence of context, or if it demands an action plan, it must be dropped directly onto the short-term Issues List. For example, if a leader says a client is upset because of a delayed shipment, the facilitator must immediately say, 'Drop that to the Issues List,' and move to the next headline. Do not let anyone ask follow-up questions during this segment. This discipline keeps the meeting on track and protects your time. By migrating these items directly to the Issues List, you ensure they undergo the full rigor of the Identify, Discuss, and Solve process later in the meeting, rather than being patched over with quick, unthoughtful comments during the opening minutes.