Operations ·
When dashboards disagree, define the metric first
Different numbers can come from different definitions rather than broken calculations. Agree the business event, population and time window before debating a result.
By Norwind
Describe the event behind the label
A label such as active customer can represent a login, a completed task or an account with a current contract. Those are different events, each potentially useful for a different decision. Ask what the metric is intended to help someone decide. Then describe the event in ordinary language so the people using the dashboard can recognize what is included.
Make the boundaries explicit
Record the time window, the treatment of canceled or corrected records and the source used for the calculation. Consider whether the report uses event time or the time the data arrived. These details can explain why a recently corrected record appears differently across systems. Keep examples of borderline cases so a future change does not quietly alter the meaning of the report.
Put the definition close to the number
A definition hidden in an old conversation will not help the next reader. Include a concise explanation near the dashboard or in a linked data dictionary with an owner. When the meaning changes, distinguish a new definition from a change in business performance. An integration or reporting tool can make data available, but the business still needs to agree what the result is supposed to represent.
A practical check
- State the event the metric counts.
- Document the time window and exception rules.
- Name the owner of the definition and change history.