A metric needs a baseline to compare against and a direction of change before it means anything

What it is

The previous card's fix lands as two mandatory parts: a comparison baseline (against what — target, same period last year, previous cycle) and a direction of change (up or down, by how much). The baseline anchors the absolute value into a judgement; the direction turns a static value into a narrative. The minimal complete metric card is therefore a trio: current value + baseline + direction and magnitude (with sign and colour coding).

Why it happens

Baseline and direction supply the two legs of judgement: the baseline answers "what is the reference frame" — the same value reads differently against target, history, or competitors, and labelling the baseline labels the scope of the conclusion; the direction answers "is it moving" — a static value cannot distinguish "stable" from "stalled," and direction with magnitude ("+8% versus last month") carries the change. Presentation adds one critical discipline: the visual encoding of direction must agree with the semantics — sign, arrow, and colour must align; an encoding mismatch ("+8% in green, where green means falling in this product") manufactures reverse misreads directly. The baseline and direction's scope (against whom, over how long) must also be visible on the card, or the judgement's range stays unknown.

Where it stops holding

Direction encoding has a context trap: different metrics have different "good" directions (revenue rising is good, complaints rising is bad), so the red-green mapping must bind to metric semantics rather than numeric sign — the general rule is "good = green," not "up = green," with rise-fall colour reserved for direction-neutral metrics. When baseline data is missing (a new metric with no last-year figure), the honest move is to display "no comparison baseline" rather than silently hiding the direction component — readers will read the absent state as flat.

Applying it

• Fix the metric-card trio: current value, baseline with scope, and direction-magnitude (sign + arrow + colour triple-encoded).
• Bind the red-green mapping to metric semantics (good = green) and keep it consistent product-wide.
• Verification: sample ten metric cards and ask readers to state each judgement and its basis without documentation; incomplete answers mean missing baselines or scope labels.

Related

• Same group: U7.03.1 A single number lacks context · U7.03.3 A sparkline can add the time dimension
• Nearby: U7.05.2 Period-over-period suffers cyclic interference; year-over-year removes cycles but reacts late · U7.06.4 When the time range changes, comparison baselines must update in sync
• Search terms: KPI comparison baseline · trend indicator · delta display