Define the metric once, and let two panels agree
Most dashboard arguments are not about the number. They are about two charts that computed it differently. The fix is a single definition everyone reads from.
The longest meeting a data team ever sits in is the one where two dashboards show a different figure for the same thing. Net revenue retention is 113% on one screen and 108% on another, and the next hour goes to working out which query was wrong instead of what the number means.
Neither query is wrong. They just disagree about whether a downgrade that later re-upgrades counts as churn, and about which day the month closes on. Both are defensible. That is the problem: a metric with two defensible definitions has no definition at all.
One definition, versioned
Halvard keeps a metric definition in one place, reviewed like code and versioned like code. Net revenue retention is written once — what counts as expansion, what counts as contraction, when the window closes — and every panel that shows it reads that definition. When someone changes it, the change has an author and a date, and both panels move together.
This is unglamorous and it is most of the value. A console is only worth watching if the people watching it have stopped arguing about whether it is telling the truth.
What this costs you
You lose the ability to quietly fudge a number to make a slide look better, which is the point. You gain a room where the figure on the wall is the figure, and the meeting is about what to do rather than whose export to believe.