Skip to main content

Closeness of Mapping

Adapted from the Cognitive Dimensions of Notations framework (Green & Petre, 1996; Blackwell & Green, 2003). See About the Dimensions for framework references.

Closeness of Mapping describes how closely the interface representation corresponds to the problem domain — how well the notation matches the way users think about their work. When the mapping is close, users can work directly with familiar domain concepts. When it is distant, they must mentally translate between what they want to do and how the software requires them to express it.

Edwin Hutchins identified two independent distances that determine closeness of mapping: semantic distance (the gulf between the user's intent and the system's meaning) and articulatory distance (the gulf between the system's meaning and the physical form of the interface).1 Both must be small for the mapping to feel close. A 3D modelling tool that represents objects spatially in a viewport has close articulatory distance — the representation looks like the domain. A colour picker that uses HSB (Hue, Saturation, Brightness) rather than RGB has close semantic distance — it matches how artists think about colour, not how computers store it.

Domain Vocabulary vs. Software Vocabulary​

One of the most common mapping failures is forcing users to think in the software's vocabulary rather than their own. Barbara Mirel documents a striking example: a hospital root cause analysis team using software with a JCAHO-standard controlled vocabulary that did not match their working analytical categories. The team generated their own terms through expert domain analysis, then had to laboriously translate them into the software's vocabulary afterwards. Some contributing factors had no software equivalent at all. The cost was enormous friction and reduced analytical depth.2

The principle is clear: encode professional patterns, vocabulary, and conventions into the interface so users can think like themselves, not like the application. If category managers talk about "working the funnel" and "winners and losers," those spatial and competitive metaphors should shape the workspace design. If animators think in terms of "ease in" and "ease out," the curve editor should use those terms, not mathematical function names.

Analysis in a Keystroke​

Close mapping extends to operations, not just representations. Mirel advocates for "analysis in a keystroke"2 — domain-conventional calculations and operations built directly into the interface. If analysts routinely need to compute a year-over-year percentage change, that should be a single operation, not a manual formula construction. The interface should offer the operations that the domain demands at the level of abstraction the domain uses.

When Mapping is Necessarily Distant​

Not all mapping can be close. Regular expressions, for instance, use a notation that is semantically distant from the text patterns they describe. Complex database queries require abstract set-theoretic thinking. In these cases, the design challenge shifts to providing bridges: visual feedback, previews, and intermediate representations that help users verify that their abstract notation is producing the intended concrete results.

Testing​

  1. Does the notation reflect how domain experts think about their work? Ask an expert to describe their workflow in their own words, then compare that language to what the interface presents.
  2. Can domain operations map naturally to interface actions, or must users translate between "what I want to do" and "how the software requires me to do it"?
  3. Does the interface use domain vocabulary or generic software vocabulary? Look for places where labels, menu items, and terminology diverge from how practitioners talk about their work.
  4. Where the mapping is necessarily distant, are there visual bridges (previews, feedback, intermediate representations) that help users verify their intent?
  5. Are domain-conventional operations available directly, or must users construct them from lower-level primitives?

Conclusion​

Close mapping reduces the mental translation overhead that accumulates across every interaction in a complex workflow. The ideal is an interface where domain expertise is the primary skill needed to use the software effectively — where a skilled practitioner can approach the tool with their professional knowledge and find it speaks their language.

Check After Improvement​

  • Hard Mental Operations
  • Consistency
  • Role Expressiveness

Footnotes​

  1. Hutchins, E. L., Hollan, J. D., & Norman, D. A. (1985). Direct manipulation interfaces. Human–Computer Interaction, 1(4), 311–338. ↩

  2. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. ↩ ↩2