Aglet

Learn From Repeated Chart Axis Confusion

An axis lesson preserves the values and visual treatment that produced a misleading comparison. Record domain, scale, zero policy, ticks, units, labels, and intended question. Then improve chart review so a change in data range or configuration exposes its interpretive boundary before the visual is reused.

Keep the lesson for the next incident

  1. Retain range exemplars

    Keep ordinary, outlier, negative, zero, narrow-range, and unit-change fixtures with expected axis and mark behavior. Record filter state, chart revision, companion table, and export. Preserve the original rendering beside the agreed treatment to make the lesson inspectable.

  2. Classify visual recurrence

    Review earlier questions for truncated domains, hidden zero, log choices, unit conversions, rounded ticks, and charts whose purpose was never stated. Group named cases by missing metric contract or review cue. Avoid assigning a universal visual rule when comparisons intentionally differ.

  3. Assign chart stewardship

    Make the chart designer maintain scale fixtures and the metric owner approve units and analytical purpose. Add a trigger when data range, scale type, axis formatter, or comparison question changes. State what the fixture detects and which legend, color, or accessibility checks remain separate.

What to carry forward

The learning record is complete when it links axis confusion to a missing scale, unit, or purpose statement, preserves range fixtures, and names an owner and trigger. Keep intentional log or bounded views labeled so future readers do not reopen a deliberate choice as an unexplained distortion.

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