Source: ViewEdit

Location overloading

Location overloading is reusing the same screen location, menu slot, or navigation item for different functions, where the function depends on context the user cannot see at the point of action (which team, project, scope, or filter is active).

In plain language: the button did not move, but what it means did.

Example

Vercel’s dashboard navigation, the default since 26 February 2026, puts team-level and project-level navigation in one sidebar. Its changelog lists "consistent tabs for unified navigations across both team and project levels" and "projects as filters so you can switch between team and project versions of the same page in one click" (Vercel changelog). The same sidebar item can therefore open a team-wide page or a project-scoped page, depending on a filter state set elsewhere.

Why it is a problem

It is a mode

Raskin defines an interface as modal for a gesture when the current state is not the user’s locus of attention and the interface gives one of several responses depending on that state (Raskin 2000, ch. 3). A sidebar item whose target depends on an out-of-view scope filter fits that definition. Tesler spent his career removing modes from text editing (Tesler 2012). Norman’s taxonomy of action slips puts mode errors under errors in forming the intention: the user’s action is right for one state and the system is in another (Norman 1981).

It spends spatial memory

Expert users stop reading labels and go by place. Scarr, Cockburn, Gutwin and Bunt showed that a flat, spatially stable command layout (CommandMaps) beats menus and the Ribbon for experienced users (Scarr et al. 2012). Scarr, Cockburn, Gutwin and Malacria found spatial-memory gains survive translation and scaling of a layout but are hurt when it reflows (Scarr et al. 2013). Robertson et al.'s Data Mountain showed people retrieve documents better when they place them in space themselves (Robertson et al. 1998). Cockburn, Gutwin and Greenberg model the shift from visual search to decision by location as users learn a stable menu (Cockburn et al. 2007). Overloading keeps the place stable but changes the meaning, so the memory still fires and lands on the wrong thing.

Adaptive layouts carry a known cost

Findlater and McGrenere found a static split menu significantly faster than an adaptive one, and most users preferred the adaptable (user-controlled) version (Findlater & McGrenere 2004). Gajos et al. map when adaptation helps and when it hurts; predictability is a large part of the answer (Gajos et al. 2006).

It breaks consistency and recognition

Nielsen’s heuristics #4 (Consistency and standards: users should not wonder whether different situations or actions mean the same thing) and #6 (Recognition rather than recall: users should not have to remember information from one part of the interface to another) both apply (Nielsen 1994/2024). Norman separates affordances (what you can do) from signifiers (what tells you how and where) (Norman 2013). An overloaded slot has one signifier for two affordances.

It costs working memory

Cognitive load theory holds that working memory is limited and that load spent on things other than the task gets in the way of learning (Sweller 1988). Tracking a hidden scope is that kind of load.

Stable targets get faster

Fitts’s law ties pointing time to target distance and size (Fitts 1954). Practiced users aim before they look; a stable target keeps that aim valid, an overloaded one makes the aim land on a different function.

Background: place in memory

O’Keefe and Dostrovsky’s place-cell recordings in rat hippocampus started the "hippocampus as a spatial map" line of research (O’Keefe & Dostrovsky 1971). Maguire et al. found that most superior memorizers used the method of loci and showed more activity in brain regions tied to spatial memory and navigation (Maguire et al. 2003). This is background, not proof about UIs: it explains why people lean on place, and the HCI studies above measure what happens on screens.

Counterarguments

  • Screen real estate. One sidebar for two scopes saves space, and the space limit is real. Scarr et al. (2012) open by saying hierarchy exists because of screen space limits.

  • Progressive disclosure. Showing only what the current context needs cuts clutter and errors for novices (Nielsen 2006). The fix is to make context visible, not to bring back every control.

  • Consistency of structure. Vercel’s stated goal is consistent tabs across levels. Same structure in two scopes is fine when the scope is visible where the user acts; Raskin’s definition turns on locus of attention.

Design guidance

  • Put the active scope in the slot itself (label, color, or breadcrumb inside the item), not only in a distant switcher.

  • Give each scope its own stable location rather than one location with a filter.

  • Make scope changes user-initiated and reversible; avoid automatic reflow.

  • Concept note on a layout that avoids it: Black-box service map.

  • Related: Context-bound settings, Scoped UX architecture.

References

Every entry below was checked against the publisher or DOI record on 2026-10-23.