U2.02.1Bar chart for comparisondesignresearch

Bar charts suit magnitude comparison across categories

Aliases: bar chart use case · column comparison

What it is

Bar charts for categorical magnitude comparison encode each category's value as a length extending from a common baseline, directly supporting which is larger, by how much, and in what order. They often suit one categorical field paired with one nonnegative measure, but are not a default for every “category plus number.” Task, scale semantics, category count, labels, and uncertainty can change the choice.

Why it happens

A common baseline makes endpoint position and length difference available together, reducing conversion across references. Sorting can also turn rank into spatial structure. Color may encode identity or state, but an independent quantitative meaning adds interpretation cost. Relative to angle, area, or nonaligned segments, bars often support easier comparison in classic magnitude-judgment tasks. That is a task- and stimulus-bounded empirical pattern, not a law across charts.

Studying it

Compare bars, dot plots, numeric tables, and candidate alternatives on the same data. Test maximum, ordering, difference, ratio, exact lookup, and confidence separately. Control sorting, labels, category count, range, mark size, and device, and report error distributions and time. For intervals or distributions, also test whether viewers mistake one bar for the full evidence.

Where it stops holding

When the task concerns continuous temporal trend, distribution shape, association between two measures, or part-to-whole, another form may fit better. Negative values may extend from zero in the opposite direction. Intervals, deltas, and floating ranges need explicit endpoint semantics and cannot inherit the “accumulation from zero” interpretation. With many categories, scroll, filter, facet, or use dots, but do not aggregate away high-consequence categories.

Applying it

  • Choose bars after establishing a categorical magnitude-comparison task, and preserve a common baseline, unit, and legible labels.
  • Horizontal layout often helps long labels; preserve temporal or natural order when it carries meaning rather than reordering for layout convenience.
  • Show uncertainty, sample size, and missingness, and provide structured values or a table for exact and nonvisual access.
  • Compare candidates on real questions using accuracy, time, and error types rather than a fixed three-second rule.

Related

  • Same group: U2.02.2 The baseline must start at zero · U2.02.3 Order categories by value, not alphabet
  • Nearby: U2.07.3 Stacked bars are usually the better substitute · U2.03.1 Line charts suit trends over ordered variables
  • Search terms: bar chart · categorical comparison · common baseline · length encoding

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/U2.02.1