Metric governance is the set of rules that decide how a metric gets created, defined, owned, changed and retired. It is the difference between a measurement program that holds up for five years and one that quietly rots.
A single agreed definition for each metric, written down, including the exact population in the numerator and denominator.
A named owner for every metric, responsible for the definition rather than for the value.
A versioning rule, so a change in method is recorded and dated rather than absorbed.
An approval path for creating a new metric, which is mostly there to slow creation down.
A retirement path, so metrics nobody uses get removed instead of accumulating.
Measurement programs do not usually fail from having too few metrics. They fail from having too many, defined inconsistently, owned by nobody in particular.
The pattern is familiar. Four teams each build a version of “patch compliance”. None of them are wrong. All of them differ in scope, timing or denominator. A year later the executive committee is presented with three different figures for the same thing in the same meeting, and the credibility of the whole set takes the hit.
Governance is cheap to install at thirty metrics and painful at three hundred.
You do not need a committee. You need a written definition per metric, one owner, a change log, and a quarterly review that asks of each metric: did anyone act on this, and does the definition still match what the tools return.
Most of the value comes from the first two.
Metric Maestro holds definitions centrally and versions them, so the same formula is applied every period and any change is recorded with the date it took effect.
Definitions sit above the tools rather than inside them. Replacing a scanner or an endpoint agent changes the mapping underneath and leaves the metric definition alone, which keeps the history intact and removes the most common source of ungoverned change. Ownership, evidence and computation history are stored with the metric rather than living in a spreadsheet somebody maintains on the side.
From the blog