Encoding that jumps between charts forces readers to relearn the legend

What it is

Cross-chart legend relearning cost is the extra work of establishing which visual value denotes which object after the same encoding role is reassigned. It can appear as legend returns, label rescanning, delay, or mistakes, but does not accumulate at a fixed linear rate per switch. Detectability, co-presence, direct labels, familiarity, and task all matter. When charts encode genuinely different fields, a new legend may be necessary semantics rather than an arbitrary jump.

Why it happens

A binding learned in an earlier view creates an expectation for the next. Silently reusing the same colour for a different object pits that expectation against the new legend. A clearly distinct new channel may cause less erroneous transfer but still requires lookup. Legend distance, category similarity, scrolling, and pagination shape the cost, while direct labels and linked highlighting reduce memory demand. The failure is a broken cross-view correspondence contract, not one fixed working-memory capacity.

Studying it

Compare stable mappings, permutations, explicit change notices, repeated legends, and direct labels on lookup, cross-chart matching, and change judgments. Measure accuracy, time, first-switch errors, legend visits, correction, and confidence while varying legend visibility, view delay, category count, and reader experience. Eye tracking can show return paths, but looking at a legend is not proof of understanding; combine gaze with answers and reported strategy.

Where it stops holding

The same colour may have local meanings for distinct, clearly separated fields if it does not imply cross-chart identity. Forcing one palette across every field can create a semantic conflict. Changes for focus, background adaptation, or accessibility can preserve a base identity cue, animate the transition, or explain the change. A standalone chart, a reader without an old mapping, or directly labeled marks may produce little relearning cost.

Applying it

• Mark entities and encoding roles that need cross-chart tracking. Reuse mappings within a role; make reassignment trigger review and a change notice.
• Keep the current legend or direct labels visible in long pages, pagination, and presentations. Preserve identity cues in linked selections.
• Do not use a fixed legend-view count as a failure threshold. Establish a project baseline from errors, time, repeated returns, and task consequence.
• State the reason, scope, and effective version of intentional remapping so old and new charts do not coexist unlabeled; test the first switch for transfer from the old binding.

Related

• Same group: U1.11.1 The same entity keeps the same colour and position across a chart series · 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: U1.10.5 Redundant channels that disagree semantically give contradictory cues · U2.15.1 Small multiples replace overlay with repeated like-for-like panels
• Search terms: legend relearning · mapping interference · cross-view correspondence