Our leadership team struggles to know what belongs as a Customer or Employee Headline versus what should go directly onto the Issues List prior to our Level 10 Meeting. What clear operational rule differentiates the two before we walk into the room?

Question

Tyler Smith · Accepted Answer

Distinguishing between a headline and an issue comes down to a simple filter: awareness versus action. A headline is notable operational information that the leadership team must know to maintain cross-functional awareness, but it requires zero group problem-solving. An issue is anything that is incomplete, off track, broken, or creating friction that requires team discussion to resolve.

Before stepping into the Level 10 Meeting, train every leader to apply the binary test. If an event happened, was handled cleanly, and simply informs other departments of a material shift, it belongs in Customer and Employee Headlines. Examples include closing a key target account, a client executive departing, or a team member announcing paternity leave. The item is shared in fifteen seconds, acknowledged, and left alone.

If that same event creates downstream uncertainty, requires resource reallocation, or exposes an operational vulnerability, it is not a headline. It is an issue. For instance, signing an enterprise client that overwhelms onboarding capacity is an operational bottleneck. The signed contract is a headline; the onboarding deficit is an issue.

Teach your team that when in doubt, default to adding it directly to the Issues List before the meeting starts. During the meeting, the Integrator protects the boundary ruthlessly. If a leader begins sharing a headline and says they need input or want to gauge team reaction, the Integrator cuts in immediately and moves the topic to the bottom of the Issues List.

By enforcing this binary separation before the meeting begins, you protect the five-minute reporting pulse and preserve your sixty minutes of IDS for genuine root-cause resolution.