Keep the lesson for the next incident
Document units with the measure
State the source unit, intended display unit, aggregation, and conversion boundary. Explain any mixed-unit comparison and the labels each surface should use. Keep this information with the measure definition so a future dashboard author does not need to infer semantics from a short axis abbreviation or an example screenshot.
Retain a discriminating magnitude
Keep a small known-value fixture that reveals an omitted or repeated conversion. Record expected query, display, and export values with their units. Include a neighboring reused measure if the original defect came from a shared formatter, so future checks preserve the distinction rather than accepting one correct-looking chart.
Review conversion and reuse changes
Assign review when a source unit, formatter, measure aggregation, or export path changes. Compare the known value across affected surfaces. Track confirmed unit interpretation problems separately from numeric calculation errors, while keeping their connection visible when a conversion boundary rather than the final label caused the misleading result.
What to carry forward
Close with an explicit unit contract, a readable known-value fixture, and an owner for conversion or formatter changes. Preserve any unsupported mixed-unit comparison in guidance. The next maintainer should be able to explain what a displayed number measures without guessing from its magnitude or borrowing the label from a superficially similar report.
Technical background: Metabase documentation.
Keep the decision with the work.
Use a Work Item in Aglet to record the problem, the evidence you have, and the next decision. Add an owner and priority, then keep updates in the discussion so the next person can follow the reasoning.
Create an account See the product workflow