Aglet

Triage Chart Axis Scale and Labels

Axis triage starts with the data range and the question a reader is meant to answer. Inspect ordinary values, outliers, negatives, zero, tick spacing, and label formatting together. Preserve a chart fixture where two scale choices make the same values appear materially different, because a visual reading can diverge before the query does.

Establish what is happening

  1. Name the visual contract

    Write the measure, unit, expected domain, scale type, zero treatment, tick rule, and label format. Record whether the chart compares magnitude, change, rank, or distribution. Keep raw values beside rendered ticks so a reviewer can distinguish data from geometry.

  2. Trace values to marks

    Follow filtered rows through aggregation, domain calculation, scale mapping, tick generation, axis labels, marks, and tooltips. Compare the numeric range and visible positions. Mark where a missing zero, clipped outlier, or rounded tick first changes the implied comparison.

  3. Bound the affected charts

    List charts, cards, tables, exports, and dashboards sharing the measure or scale configuration. Separate intentional log or truncated views from unexplained choices. Ask the metric owner and chart designer to resolve a conflict between units, domain, and comparison purpose.

What to carry forward

Triage is complete when measure, unit, domain, scale, first visual divergence, affected charts, and responsible owners are explicit before any visual conclusion is accepted. Keep the result provisional when the comparison purpose or outlier policy has not been defined.

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