Even when our Scorecard numbers are updated before our Level 10 Meeting, our leadership team still drags out the review by debating why a number dropped. How does an Integrator enforce a strict five-minute review?

Question

Tyler Smith · Accepted Answer

A Scorecard review drags out for one reason: the team is trying to solve issues while they are reporting data. The Level 10 Meeting™ has a strict architecture. The Scorecard review agenda item is built solely to identify that a problem exists, not to understand it, explain it, or fix it.

To execute a clean five-minute review, the Integrator must enforce four non-negotiable operational rules:

- Pre-meeting completion: All numbers must be logged by their single accountable owner at least one hour before the meeting starts. If a number is blank, it is automatically marked red.
- Only say two words: When the Integrator reads down the Scorecard, the owner of that measurable speaks only two possible words: on track or off track. No context, no apologies, no disclaimers.
- Zero discussion allowed: The moment an owner attempts to explain why their number missed, the Integrator interrupts and asks whether they want to drop it to the Issues List or move on.
- Immediate drop to Issues: If a measurable missed its weekly target, the Integrator immediately logs it on the Issues List. You do not discuss the cause until the meeting reaches the IDS® portion.

When the leadership team knows they will have dedicated time during IDS® to dig into root causes, the anxiety to defend themselves during the Scorecard review disappears.