When a Scorecard metric is slightly off-track but still healthy overall, our department heads get defensive and demand to explain the context, which eats up our five-minute Scorecard review. How do we enforce a strict drop-it-to-the-Issues-List policy for minor deviations without making the team feel micromanaged?

Question

Tyler Smith · Accepted Answer

The Scorecard review is a five-minute high-level check of your weekly numbers. If a metric is red or off-track, the seat owner has only two options: say off-track or ask to drop it to the Issues List. There is absolutely no room for explanations, excuses, or defensive context during the review phase.

When team members start explaining why a number is red, they are trying to protect themselves rather than solve the problem. This defensiveness slows down the meeting and prevents the team from looking at the raw truth of the data. The facilitator must immediately cut off any explanation with a simple, let's drop that to the issues list.

Explain to the team that dropping a red number to the Issues List is not a punishment or a performance critique. It is simply a recognition that a leading indicator needs attention so we can IDS® it at the right time. By removing the stigma of a red number, you remove the need for defensiveness.

Keep the Scorecard review moving at a rapid clip. If a number is red and does not require discussion, keep moving. If it does require attention, put it on the list and move on. This discipline preserves your energy for the actual IDS® portion of the meeting.