During our weekly Scorecard review, we have several metrics that are technically marked green because they met the target, but our gut tells us there is a major underlying issue brewing. How do we flag these watermelon metrics without derailing the quick reporting section?

Question

Tyler Smith · Accepted Answer

A watermelon metric is green on the outside but red on the inside. This happens when a number looks healthy on paper, but the underlying activities or trends are failing, or the data is being manipulated to look good. If your team ignores these warning signs just because the box is green, you are failing to use your Scorecard as an early-warning system. However, you must not start debating the metric during the reporting section. The rule of the Scorecard review is strict: read the number, confirm it is on track, and move on.

If a leader has a gut feeling that a green metric is hiding a deeper issue, they must simply say, drop that to the Issues List, as they read it. The facilitator will write it down on the Issues List under a title like Scorecard Metric Underlying Issue. Do not allow any discussion of why it is being dropped during the first fifty minutes of the meeting. Once you reach the IDS® portion of the agenda, you can prioritize that item. During the discussion, dig into whether the metric is actually measuring the right activity, if the target is too low, or if the data collection method is flawed. This keeps your reporting fast while ensuring your intuition is fully leveraged.