U7.05.1A single value means something only against a baselinedesign

120,000 daily actives means nothing on its own until it's compared against some baseline of usual

Aliases: comparison baseline · reference frame

What it is

"120K daily actives" carries no judgement by itself: above the usual is good, below the usual is bad, matching the usual is business as usual — and that "usual" is the baseline. The baseline may be a target, the same period last year, the previous cycle, a competitor, or an average; choosing which one decides the story the same value tells. Every number in a metric card, alert, or report implicitly stands on some baseline, and implicit-but-unstated is where misreading breeds.

Why it happens

The baseline is the precondition of meaning because business values are almost all relative quantities: absolute values are set by scale (a big platform's and a small platform's daily actives are not comparable), and what compares is relative position — against its own past, against its target. The comparison step in reading is unavoidable: seeing a number, readers automatically summon a reference (usually the most recent memory or an expectation), a wrong reference means a wrong judgement, and when the interface offers no baseline the reader's reference is necessarily imagined. Drawing the baseline explicitly (a reference line, a comparison value, a delta annotation) moves control of "which reference gets summoned" from chance to design — both a readability investment and narrative discipline: choosing which baseline to show is choosing which comparison the reader performs.

Where it stops holding

More baselines is not better: a card carrying target line, year-over-year, period-over-period, and industry average at once leaves the reader unsure which one the conclusion answers to — one primary baseline, explicit, with the rest demoted to secondary information. A baseline is legitimate only when comparable: mismatched scopes (the fifth card in this group), misaligned periods, or different samples make pseudo-baselines. There is also a semantic edge: some metrics have no meaningful baseline yet (a brand-new metric in week one), and honesty there means showing "no baseline" rather than manufacturing a reference.

Applying it

  • Label the primary baseline for every presented value: target attainment, year-over-year, or period-over-period — one primary, visible.
  • Draw the baseline into the graphic (target line, last-year dashed line), not only the percentage.
  • Verification: ask readers "what is this number compared against?"; inability to answer means the baseline display is insufficient.

Related

  • Same group: U7.05.2 Period-over-period suffers cyclic interference; year-over-year removes cycles but reacts late · U7.05.3 The baseline choice can flip the same metric into a rise or a fall · U7.05.4 With a tiny base, percentage change inflates into distortion · U7.05.5 The baseline period's statistical scope must match the current period's
  • Nearby: U7.03.1 A single number lacks context · U4.03.2 Midpoint placement changes the conclusion
  • Search terms: baseline comparison · reference value · benchmark choice

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/U7.05.1