Proximity Compatibility Principle
Information that must be mentally integrated often benefits from perceptual proximity, while information needing separate treatment may benefit from separation.
Direct explanation
What it means
Putting related values together reduces eye movement and memory, but too much visual integration can obscure distinct variables. Display proximity should match processing proximity.
Dashboards frequently separate values that must be compared or combine signals that require independent action.
Research anchor: Christopher D. Wickens, C. Melody Carswell, 1995
Research and interpretation
What the research found
The review related display proximity effects to whether a task required information integration or focused attention.
The principle remains useful in human factors and display design, with tradeoffs supported across integrated and separated displays.
Popular advice versus careful use
Common shorthand: Related information should always be physically combined.
Co-locate what users must integrate and preserve separability where source or independent action matters.
How designers apply it
- 01
Place actual, target, and variance in one aligned view.
- 02
Keep independent safety channels visually separable.
- 03
Show a field rule beside the value it constrains.
Original UI examples
desktop finance
Budget review
Planned, actual, and variance values share a row.
Comparison is direct instead of requiring memory across panels.
safety display
Aircraft alerts
Independent systems retain separate identities despite a shared overview.
Operators can integrate status without confusing source and action.
KPI dashboard
Less effective
Put target on one tab and actual on another.
Better fit
Co-locate aligned values and preserve their distinct labels.
Integration should not collapse uncertainty or provenance.
Limits and failure modes
Optimal proximity depends on task, modality, clutter, expertise, and whether variables need joint or independent processing.
Common mistakes
- Using proximity as a rule to combine all dashboard data.
- Separating related values for aesthetic symmetry.
When it should not dominate
- When independent diagnosis requires clear source separation.
- When integration produces visual masking or clutter.
Responsible use
Accessibility
Use table semantics, headings, and reading order to reproduce visual integration, and ensure zoom does not separate labels from values.
On mobile: Prefer focused comparisons and preserve labels when rows stack.
Ethics and context
Use the principle to reduce unnecessary effort and improve comprehension. Validate the result with representative users rather than treating a general tendency as a universal instruction.
On desktop: Use aligned tables and coordinated views while supporting focus and filtering.
Designer checklist
- Describe the mental integration task.
- Match visual distance to that relation.
- Test comparison time and source-confusion errors.
Check your understanding
Which statement applies Proximity Compatibility Principle most carefully?
Practice and continue learning
See ideas in real interfaces
These external interfaces are editorial references, not examples created to demonstrate this principle.
Sources and further reading
- 01Open source
The Proximity Compatibility Principle: Its Psychological Foundation and Relevance to Display Design
Christopher D. Wickens, C. Melody Carswell · 1995 · Human Factors
Peer reviewed review · primary or original source
Continue the graph
Related principles
principle
Law of Proximity
Elements placed nearer one another tend to be perceived as related, especially when the spacing pattern is consistent and other cues do not override it.
principle
Stimulus-Response Compatibility
Responses are generally faster and less error-prone when the relationship between a signal and its control matches learned or spatial expectations.
theory
Cognitive Load
Cognitive load describes demands placed on limited working-memory resources while a person learns or performs a task.