We streamlined our Scorecard visual design, but our leadership team still falls into the trap of analyzing, explaining, and solving problems during the weekly five-minute review. What behavioral rules must the Integrator enforce to stop this?

Question

Tyler Smith · Accepted Answer

The five-minute Scorecard review in your Level 10 Meeting™ is strictly for reporting, not for fixing. When a number is red, the only acceptable response from the metric owner is drop it down to the Issues list. Any attempt to explain, defend, or analyze why the number was missed must be shut down immediately by the Integrator. To maintain this discipline, the Integrator must enforce three strict rules. First, the review is a rapid-fire read-through. The leader reading the numbers should only state the name of the metric, the target, and the actual result. Second, if a number is red, the owner simply says, drop it. There is no context allowed, such as we had a sick employee or the client delayed. The moment someone starts a sentence with because, the Integrator must cut them off and instruct them to save it for the IDS® portion of the meeting. Third, the leadership team must input their data prior to the meeting. Arriving with an incomplete Scorecard is a violation of accountability. By keeping the Scorecard review under five minutes, you preserve the energy and time of your leadership team for high-value problem-solving during IDS®. This behavioral discipline is what separates companies that run on data from those that use meetings as unproductive therapy sessions.