The same entity keeps the same colour and position across a chart series

What it is

Cross-chart identity consistency reuses identity cues—such as colour, symbol, or small-multiple slot—for the same stable entity across views meant to be read together. “Same position” in the title applies when position carries identity or correspondence; it does not freeze every entity at one coordinate. Value sorting, temporal movement, geography, and layout optimization can legitimately move it. Colour that carries state or magnitude likewise cannot be forced to double as a fixed entity colour.

Why it happens

A legend, label, or initial view establishes a binding between an entity ID and a visual value. Reuse lets readers track the object; an unannounced colour or slot change conflicts with that binding and adds correspondence, legend lookup, and misidentification cost. Consistency applies only to the same semantic role. Blue for product identity in one chart and low temperature in another is not consistent encoding, and a row changing from fixed entity order to value rank changes what position means.

Studying it

Compare stable mappings, random remapping, signaled intentional remapping, and direct labels on cross-view lookup, correspondence, change detection, and comparison. Measure accuracy, time, legend visits, first-switch errors, and individual strategy while varying delay, juxtaposed versus sequential viewing, category count, and colour discriminability. Qu and Hullman's multi-view consistency study found both validations and exceptions based on cardinality, available channels, and layout, so record what objective consistency yields to rather than asking only whether it exists.

Where it stops holding

Identity should not override more consequential conventions such as warning state, political affiliation, or domain-standard colour. Resolve a semantic conflict with another channel, direct labeling, or an explicit migration. Value sorting can make extrema easier to find, so fixed rows may hurt that task; map and network positions follow spatial or topological meaning. Theme, background, greyscale output, and colour vision can also make identical RGB values unequally discriminable, making perceptual and accessible outcomes more important than literal codes.

Applying it

• Declare every visual role as identity, status, magnitude, order, or highlight, and reuse mappings only within the same role and reading scope.
• Keep category slots and identity colours stable in directly compared small multiples. When sorting by value, retain labels and identity cues and state that position now means rank.
• Resolve mappings by stable entity ID rather than display name so renaming, translation, and filtering do not remap an object. Reinforce colour with labels, symbols, or accessible names.
• Test correspondence across juxtaposition, pagination, mobile layouts, themes, and greyscale. Allow a documented exception when the task shifts from tracking to ranking.

Related

• Same group: U1.11.2 Encoding that jumps between charts forces readers to relearn the legend · U1.11.3 Only charts sharing a scale can be compared on magnitude · U1.11.4 Pin the mapping in the data layer; never configure it chart by chart · U1.11.5 Extend category sets by appending, never by reassigning
• Adjacent: U2.15.1 Small multiples replace overlay with repeated like-for-like panels · U1.05.5 Culturally loaded hues override the assigned mapping
• Search terms: identity consistency · object correspondence · multiple views