U7.03.1A single number lacks contextdesign

A big bold number on a metric card can't tell anyone whether it's good, bad, or ordinary

Aliases: big number card · bare value

What it is

A metric card's big number ("today's GMV: 34.8M") cannot be judged alone: good or bad, up or down, anomalous or ordinary — the number carries none of these answers. A bare value borrows the salience of "large and bold" and the trust of "numbers are objective," yet delivers near-zero information, leaving readers to improvise a baseline from memory or hunch.

Why it happens

The root is that a value's meaning comes from comparison, not from the value itself: the same 34.8M is good news above target, bad news below last year, and "no news" inside the normal band. The reading process runs "take the value, recall a reference, compare, judge" — a bare number completes only the first step and hands the rest to the reader's improvisation, which usually picks the wrong reference (comparing to yesterday, to an impression). That is why a contextualised metric card (baseline value, delta, status colour) multiplies the information in the same footprint: it finishes the reader's mental process for them.

Where it stops holding

Bare values are not always wrong: when the number already embeds the judgement (a 97% completion rate against a 100% target, a ratio with a tight interval), or when the context is carried by a neighbouring element (the sparkline beside it is its context), a bare value is acceptable — but that is a design decision, not a default. Another exception is the total-fact metric (registered users all-time), which bears no good-or-bad judgement and has weak context needs. The test: will the reader ask "and then?" after seeing this number — if yes, it needs context.

Applying it

  • Ban bare values on metric cards: every card carries at least one reference (period-over-period, target attainment) or a status colour.
  • Choose the reference by the metric's semantics (target metrics take attainment, traffic takes period-over-period) and label the reference's scope.
  • Verification: cover the card except the big number and ask readers "is this good?"; inability to judge confirms the need for context — add the reference.

Related

  • Same group: U7.03.2 Comparison baseline and direction of change are required · U7.03.3 A sparkline can add the time dimension
  • Nearby: U7.05.1 A single value means something only against a baseline · U7.04.1 Thresholds convert a continuous metric into two discrete states
  • Search terms: KPI card design · metric tile · big number context

Cards in the same group

Quick Actions

Share

Share this page

ios_share

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