This article is mostly pseudo-science: lots of charts that (nicely) illustrate the author’s opinion, not data. But when you get down to the bottom, there’s a great little data-driven marketing idea in there:
My recommendation is something called metric of the month. In metric of the month, you choose a problem area for the next month. Then you try to find the best metric which is connected to that problem. Run with the metric for one month, try to improve the reading as much as you can, and then throw the metric away. Start over with a new metric for the next month.
This way you can maximize on the excitement of the fast initial progress with a new metric. Our compilation warning chart is no longer useful to us, for example. It has lost it’s mojo. So, it makes sense to change focus as soon as that happens, and pick the low hanging fruit from a new area. It keeps things improving, and helps keep things interesting.
Whatever you do, don’t tell developers to improve on a metric like the corporate operating profit, EBIT, the stock price, or anything like that. You could just as well tell them to control the weather.