Wayfinding
Mirel argues that wayfinding receives too little design attention in complex problem-solving software, despite its importance to completing the work.1
Wayfinding is how users maintain their orientation, track progress and navigate complex problem spaces. The Context chapter examines how software responds to the user’s situation and intent. Wayfinding makes the work legible, helping users answer four questions at the heart of productive non-linear work:1
- "What have I done up to this point?" — Investigation history, prior decisions, accumulated evidence
- "What did I just do?" — Immediate feedback, confirmation, state change indicators
- "What's the current state?" — Status clarity, active filters, mode indicators, what's included and excluded
- "What can be done next?" — Affordances, available actions, feed-forward cues
When wayfinding support is strong, users can concentrate on their domain. When it is weak, they must spend mental effort finding their way through the software, leaving less for the investigation itself.
Supporting Orientation and Progress
Investigation History
Users need to see where they have been, with a visible trail of the investigation itself as well as an undo history.2 What queries have been run? What views examined? What filters applied and removed? Users should be able to navigate this investigation history, returning to any previous state and branching from it.
In data analysis tools, this means a query history with the ability to replay and modify past analyses. In 3D tools, it means returning to a saved camera position and working state. In video editing, it means markers and annotations on the timeline that record editorial decisions and reasoning.
Immediate Feedback
After an action, make its outcome clear: what changed, whether it succeeded, and whether anything remains pending. If a filter is applied, show its effect on the visible results. If an operation fails, explain the failure and leave the user able to understand the resulting state.
Feedback confirms the action and its consequences. The Context chapter covers interpreting intent and reporting actual state honestly, including the distinction between submitting a job and processing it.
Bookmarkable States
Users should be able to mark significant points in their work for later return, like physical bookmarks in a reference book.3 A bookmarkable state captures not just the current view but the full working context: what's selected, what's filtered, what panels are open, what parameters are set. Returning to a bookmark restores all of it.
Workspace Seeding
Mirel describes how expert users "seed" their workspaces by arranging elements, hiding irrelevant items, highlighting important ones and leaving visual cues for themselves.4 This is wayfinding through environmental design: the user creates landmarks and trails that help them navigate future work sessions.
Software should support this by allowing users to:
- Arrange, pin, and hide elements freely
- Apply colour tags, labels, and markers
- Save and name workspace configurations
- Preserve these arrangements across sessions
Entry Points
Non-linear software has no single "starting screen." Users approach their work from different angles depending on the goal at hand, and the same user may need different entry points on different days. Professional software should offer multiple domain-meaningful entry points: ways to begin work that correspond to the user's professional vantage point.5
A 3D artist might enter through the asset browser (starting with content), the scene hierarchy (starting with structure), or the viewport (starting with visual composition). Each is a legitimate way into the same workspace.
Orientation Cues
Persistent, ambient orientation cues should allow users to see where they are without having to stop and check:
- Breadcrumb trails showing location within nested structures
- Mode indicators showing the active tool, selection mode, or editing context
- Filter badges showing what data is currently included or excluded
- Progress indicators for multi-step operations
- Visual differentiation between regions of the workspace
A breadcrumb shows where the user is within a structure; an investigation history records the route taken through the work. Both can help orientation, but a breadcrumb alone does not preserve previous queries, decisions or evidence.
Position indicators should remain available when they carry information needed for the task. A scrollbar can show both a location in a document and markers for errors elsewhere in it. Hiding it until the user scrolls can also hide those cues, requiring an unrelated action before the user can assess their position or find a problem.
Available Routes and Actions
Users need to see plausible ways forward from their current position. Empty content areas can explain how to begin, while nearby actions can show what is available for the selected material. If a route is unavailable, make the restriction understandable.
These cues should help users choose a next step without requiring them to memorise the application’s capabilities. Context-sensitive controls and previews supply behaviour appropriate to the current situation. Multiple Representations can expose relationships and possibilities that are difficult to see in the current view.
Wayfinding Across Sessions
Complex professional work spans days, weeks, or months. Wayfinding must support users both within and across sessions. When a user returns to a project after a week away, the workspace should provide enough context to answer: "Where did I leave off? What was I working on? What's left to do?"
This means:
- Automatic workspace state preservation (no "save your workspace" decision)
- Visible indicators of recent changes and last-edited areas
- Persistent notes and annotations that serve as reminders
- Bookmarks and markers from previous sessions still accessible
Restoring a workspace helps users recover their place. It does not necessarily restore their proficiency after a long absence; see Returning Users for support with skill decay and re-engagement.
The Cost of Poor Wayfinding
When wayfinding is inadequate, the symptoms are unmistakable. Users pause frequently to orient themselves. They repeat work they have already done because they cannot find it, and maintain external notes and documents to track their progress. They also become reluctant to explore, keeping to familiar paths because they judge the cost of getting lost to be too high.
Every one of these behaviours requires mental effort that would otherwise be available for the work itself. The cost extends beyond frustration: users have less capacity to think about the problem they are trying to solve.
Check Resumption
| Check | Practical question or example |
|---|---|
| Design decision | What does the user need to recognise before continuing? |
| Failure to look for | A project reopens, but the selection, frame and unresolved question have disappeared. |
| Verification task | Ask someone to resume an interrupted task after a gap. Record orientation and useful action separately; deliberate review may be part of the work. |