One manager reports twelve completed requests. Another reports nine. Both figures may follow their own logic. An operations metric dictionary defines precisely what each dashboard number counts, where it comes from and how people should interpret it.
Photo by Vitaly Gariev on Unsplash.
This is a practical agreement about meaning. It is especially useful when teams draw figures from different systems or change reporting responsibility. A polished chart cannot resolve an undefined calculation.
Define the decision first
Ask what action the metric supports. A count used to plan next week's workload may need different detail from a financial reconciliation. If no one can describe the decision, challenge whether the measure belongs on the dashboard.
Choose a small number of useful measures before documenting every available field. Start with the numbers people already dispute or use to make commitments.
Use a metric definition card
Name and purpose: what the measure means and which decision it supports.
Unit and population: requests, hours or cases, including the relevant team or service.
Start and finish events: the exact points used in the calculation.
Formula and exclusions: treatment of duplicates, reopened work and cancelled cases.
Source and owner: authoritative record and person responsible for the definition.
Refresh timing: when the information is updated and its reporting period.
Interpretation: limitations and useful companion measures.
Include an example calculation. It exposes ambiguity more effectively than a long abstract definition.
An illustrative completion definition
A team defines completed requests as cases accepted by the requester during the reporting week. A case marked internally finished but awaiting acceptance is excluded. A reopened case is shown separately rather than counted as another new completion without explanation.
The dashboard owner documents that rule and reconciles a sample against the underlying cases. Another team may need a different definition, but comparisons should make those differences visible.
Control definition changes
Record the date, reason and owner of a change. Explain whether historical figures have been recalculated. A rise after a definition change is not automatically evidence of better performance.
Review definitions when workflows or systems change, and keep the current dictionary accessible from the dashboard. If people still use competing spreadsheet definitions, resolve the operating agreement rather than adding another visualisation.
Related guidance: practical process-mapping guide.
