During our customer and employee headlines segment, leaders frequently announce critical client escalations or staff turnover but insist the item should not be dropped to the Issues List because they are handling it solo. How do we draw the line between a routine headline and an operational issue?
The customer and employee headlines segment is strictly for brief, company-wide awareness. It is meant to highlight major positive milestones or notify the team of significant developments in under five minutes. It is never a dumping ground for operational crises that leaders want to sweep under the rug.
When a department head announces that an account is threatening to cancel or that a key manager just resigned, claiming they have it handled is unacceptable. Even if that leader has a plan, sudden client turnover damages your Scorecard revenue projections, and losing key personnel impacts cross-departmental workloads.
Use this simple rule of thumb:
- A headline is purely informational and requires zero action, zero cross-functional collaboration, and carries zero material risk to company Rocks or Scorecard targets.
- An issue is anything that threatens a measurable, impacts another department, reveals a flaw in your core processes, or introduces operational risk to the business.
The moment a leader drops a headline that involves client churn, key staff attrition, or operational delays, the facilitator must immediately instruct the scribe to add it to the Issues List. Do not allow the leader to explain their solo solution during headlines, as that burns clock. Simply add it to the bottom of the list.
When you reach IDS®, prioritize the issue. If the seat owner truly has an airtight resolution that requires no help from others, the discussion will take thirty seconds, a quick To-Do will be documented, and the team will move on. But more often than not, digging into the root cause reveals dependencies that require the whole team's alignment.
Category: Level 10 Meetings