Keep the lesson for the next incident
Keep the revealing example
Store a fixture with repeated events, shared membership, and the intended count at each grain. Record the source revision, filters, aggregation, visible label, and export header. Preserve the original misleading interpretation beside the corrected definition for future review.
Classify recurrence patterns
Review earlier metric questions for hidden joins, repeated memberships, changed grouping, ambiguous labels, and visuals that used different grains. Group by the missing contract or review signal. Use named examples and observed consequences instead of claiming a universal source of error.
Assign a definition owner
Make the metric owner maintain the row-unit statement and the report reviewer check it when measures or joins change. Add a trigger for new aggregations, drill paths, or exports. State which grain cases the fixture detects and which business definitions still need human judgment.
What to carry forward
The learning record is complete when it connects confusion to a missing grain definition or review cue, preserves an interpretable fixture, and names an owner and trigger. Keep intentional measures at different grains explicit so future readers do not mistake a valid distinction for a defect.
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