Letting one brush flip a dozen linked views at once overwhelms users who can't track what changed

What it is

Always-on linking works while view count is small and becomes a disaster when it grows: one brush flips a dozen views simultaneously, and users can neither absorb nor attribute the changes. Linkage scope needs control — users must be able to exclude a view from linking (freeze it) and see which linkages are currently active. Control turns linkage from an unrefusable global behaviour back into a configurable tool.

Why it happens

Controllability is necessary because analysis tasks are heterogeneous: most tasks want linking (finding relations across views), a few want isolation (close reading of one view, demos where stray clicks must not ripple, comparing before and after a filter). Without an isolation mechanism, those minority scenarios get worked around with screenshots and separate windows — the tool sabotages the workflow. Control also serves as error recovery: when a linkage is wrong (a view connected that should not be), the user can at least switch off the affected linkage on the spot instead of waiting for an administrator to fix configuration.

Where it stops holding

Control granularity is the key design trade-off: per-view on/off covers most needs and is easy to understand; per-field or per-pair fine control earns its place in heavy analysis products but is configuration burden in general ones. Control must not mean default-off — linkage should default to "same data source, linked," with controls reserved for exceptions; a product that ships linkage off and demands pairwise manual wiring has forfeited linking's main value. Control state itself must stay visible: which views are frozen, what the active linkage chains are — both answerable at a glance.

Applying it

• Give every view a "participates in linking" switch, on by default, with the state persistently visible as a view badge.
• Offer a temporary "link only to the focused view" mode (hold a modifier key so the brush propagates only there).
• Verification: have users configure "freeze the map; link only the scatter and the histogram"; a successful configuration within a minute with legible state means controllability holds.

Related

• Same group: U6.02.1 A selection in one view should sync to related views · U6.02.2 Linkage relations must be understandable to users
• Nearby: U6.10.3 Bookmarks must record filters and view configuration, not just page position · U5.02.5 Interactive legends double as filters, but clickability must be signalled
• Search terms: linkage control · view freezing · coordination scope