Keep the lesson for the next incident
Cluster the confusion
Group prior cases by inheritance, grouping, date scope, empty results, or navigation context. For each cluster, capture the exact parent question and the child interpretation users expected. Keep intentional differences separate from defects that share only a similar symptom.
Record the contract
Write a concise parent-to-child scope statement with examples and counterexamples. Add representative values, date boundaries, and empty behavior to a fixture. Explain whether the child answers a detail, subgroup, or filtered aggregate question.
Set a change trigger
Name the report owner and list changes that require rechecking the drilldown, such as metric definitions, grouping dimensions, filters, or navigation links. Link future reviews to the contract and fixture so new cards do not silently inherit an unclear relationship.
What to carry forward
The learning record is useful when it preserves the confusing click, states the intended child question, and supplies a fixture that catches recurrence. If teams still disagree about the relationship, record the disagreement as a definition decision instead of teaching a possibly wrong interpretation.
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