During our weekly Level 10 Meeting, our leadership team instinctively starts diagnosing and defending off-track Scorecard metrics instead of just dropping them to the Issues List. How do we break the habit of problem-solving during the Scorecard agenda item to keep it under five minutes?

Question

Tyler Smith · Accepted Answer

The weekly Scorecard review is an operational pulse check, not an autopsy. Its sole purpose is to identify whether the business is healthy or wounded, not to treat the wound in real time. The moment a leader begins explaining why their number is off track, they steal time from the IDS portion of the meeting and obscure the root issue behind defensive storytelling.

To enforce the five-minute cap, your Integrator must establish a strict verbal reporting protocol. When reviewing the Scorecard, the leader reads their metric, states the actual number achieved, and states whether it is on track or off track. Only four phrases are permitted: on track, off track, drop it, or keep it off. No context, no background stories, and no apologies.

If a number is red, the Integrator immediately asks: Do you want to drop this to the Issues List? If the metric affects quarterly goals or indicates operational drift, it is added to the list with a one-to-three-word title. The team moves to the next number without debate.

If team members continue attempting to justify red metrics, implement these tactical boundaries:
- The Integrator physically holds up a hand or states drop to issues whenever an explanation starts.
- No problem-solving is allowed until the meeting reaches the sixty-minute IDS block.
- The owner of the seat must bring the proposed issue description already clarified, removing the need for preliminary discussion.

By treating the Scorecard purely as data ingestion, your leadership team protects the structural discipline of the Level 10 Meeting and guarantees that genuine issues receive dedicated, unemotional problem-solving later in the agenda.