Which views are linked and why one chart changed and another didn't needs to be visible, not just coded

What it is

Linkage is an invisible state relation: which view connects to which, how selections propagate, why this chart changed and that one did not — all in the code, none on the canvas. Users must hold an accurate mental model of the linkage, or every linked update lands as "an inexplicable change," backfiring completely: users stop trusting the surface and start suspecting the data.

Why it happens

Comprehension comes from the isomorphism between linkage and its visual feedback: when users see "points selected in the scatter, the corresponding histogram bar lights up," they induce "these views show the same data"; that induction only holds when the visual expression matches the data relation — the same entities highlighted, identical highlight styling everywhere, unlinked views staying silent. Three failure classes break the induction: inconsistent linkage scope (linked sometimes, not others), non-uniform highlight styling (different colours for one selection in different views), and unclear direction of propagation (was my selection sent over, or is that view moving on its own?). Once the mental model forms wrongly, users develop avoidance — they stop clicking, and the entire linking investment is wasted.

Where it stops holding

Comprehension has a cost ceiling: interface elements that explain linkage (legend notes, connector lines, tips) consume attention themselves, and explaining everything turns the explanation into the new noise. The practical balance is to make consistency do the work — with uniform styling and consistent behaviour, one induction lasts forever and needs no repeated explanation; only counter-intuitive linkages (aggregate mappings, inverse filtering) merit explicit notes. Comprehension cost rises with relation count, and linkage chains beyond two or three hops should be redesigned rather than documented.

Applying it

• Standardise one highlight colour and style product-wide so "selected" looks identical in every view.
• Give first occurrence of a counter-intuitive linkage (clicking a bar highlights detail rows) a one-line explanation.
• Verification: ask new users to explain "I clicked here — why did that change?"; a correct restatement in their own words means comprehension holds — "no idea / probably a bug" means consistency or explanation needs work.

Related

• Same group: U6.02.1 A selection in one view should sync to related views · U6.02.3 The scope of linkage needs to be controllable
• Nearby: U5.02.5 Interactive legends double as filters, but clickability must be signalled · U6.03.1 Applied filters must all be visible
• Search terms: linked view comprehension · coordination transparency · interaction provenance