When a scorecard metric is missed, the owner of that metric often insists on giving a brief context update during the review, arguing that without this context, dropping it to the Issues List is a waste of time. How do we handle this resistance?

Question

Tyler Smith · Accepted Answer

This resistance comes from fear of looking bad in front of the team. When a leader insists on giving context during the scorecard review, they are trying to pre-solve or justify the miss before the team has agreed to prioritize it. This is a major source of meeting waste.

You must enforce a strict, non-negotiable rule: the scorecard review is a data-only zone. When a number is read, it is either on track or off track. If it is off track, the only acceptable response is, Drop it.

Remind the metric owner that dropping the number to the Issues List is not a punishment or an accusation. It is simply a mechanism to ensure the team allocates dedicated time to look at the issue during IDS®.

If the context is truly important, they will have ample opportunity to share it when the issue is prioritized and brought to the floor during IDS®. By keeping the scorecard review to under five minutes, you protect the ninety-minute meeting pulse.

If you let one person tell their story, everyone will want to tell theirs, and your meeting will quickly devolve into a series of status reports. Keep the discipline tight. Drop the number, move to the next item, and solve it during the designated time.