Counter-Signal

Add a measure that catches the most likely way to improve the main number while destroying its value.

Your team's output numbers look great this quarter: article volume doubled, and leadership is thrilled. Meanwhile corrections are creeping up, two editors are running on fumes, and longtime readers are quietly unsubscribing. The main metric is climbing a ladder that's leaning against the wrong wall, and nothing on the dashboard is built to notice.

Counter-Signal adds a measure specifically designed to catch the most likely way of improving your main number while destroying its value. The cue: any metric under pressure, because whatever gets optimized gets gamed, often innocently. Run it in three steps. First, ask the move question: what could get worse while the main number improves? Brainstorm the cheapest paths to the metric, cutting research time, recycling ideas, pushing burnout. Second, pick one or two measures that would detect those paths: correction rate, editor workload, reader trust or retention. Third, display them beside the main metric so neither can be read alone. What changes when it works: the dashboard becomes hard to fool, and "success" that hollows out the mission gets caught early. One technical caution from the spec: choose a causally different counter-signal, not a correlated duplicate; two numbers that fail together protect nothing.