The current location needs to remain visible
Aliases: location awareness · navigation state · wayfinding
What it is
A current-location indicator is a persistent cue to the place a person is viewing, editing, or controlling: an active navigation item, expanded section heading, workspace name, or map position. It answers “where am I now?”, rather than “where can I go next?” Persistence means that after scrolling, returning, switching panels, or shifting attention, the person can recover that location without reconstructing it from memory. A one-off title or transient notice cannot do that work.
Why it happens
Hierarchical interfaces expose only a local portion of an information space. People must connect the visible object to that larger structure, yet paths are fragile in working memory—particularly after notifications, interruptions, and repeated jumps. A stable location cue externalizes part of the navigation state, reducing needless backtracking, scope guessing, and confusion between adjacent contexts. If it disappears with scroll, is hidden by a collapsed panel, or moves arbitrarily across views, users must reconstruct the location again.
Studying it
Compare persistent cues with first-screen titles only and no cue; measure reorientation time, mistaken backtracking, and correct reports of current location after interruption, deep navigation, or search entry. Hierarchy depth, page length, collapsed navigation, and cross-section comparison tasks are relevant factors. Do not limit evaluation to first arrival: the benefit often appears after a delay, a remote link, or extensive scrolling. Separate recognition of a content topic from knowledge of its structural location.
Where it stops holding
A short, flat, single-purpose page may not warrant an emphatic marker, and excessive location chrome can compete with work. A current-location cue also does not provide a complete path or viable next destinations. Shared links, temporary filters, and personalized views can make “location” a non-tree state; in those cases show the effective view scope instead of pretending it is a stable folder.
Applying it
- Reserve a fixed area that retains the current workspace, section, or view name through scrolling and panel collapse.
- Establish the cue on first render for search, notification, and deep-link entry; do not assume an upstream navigation journey.
- Interrupt realistic long tasks, then ask participants to identify their current scope and return route; erroneous backtracking and re-searching are acceptance failures.
- Attach filters, draft mode, read-only access, and shared-view conditions when they change the scope behind a familiar location label.