Skip to main content

Wayfinding

"If data ordeals are the most designed-for activity in software for complex problem solving, wayfinding is the least — despite the fact that without adequate wayfinding support, problem solvers often cannot complete their tasks."

— Barbara Mirel, Interaction Design for Complex Problem Solving, 2004

Wayfinding is how users stay oriented, track progress, and navigate through complex problem spaces. It answers the four micro contextual questions at the heart of productive non-linear work:1

  1. "What have I done up to this point?" — History, breadcrumbs, accumulated evidence
  2. "What did I just do?" — Immediate feedback, confirmation, state change indicators
  3. "What's the current state?" — Status clarity, active filters, mode indicators, what's included and excluded
  4. "What can be done next?" — Affordances, available actions, feed-forward cues

When wayfinding support is strong, users think about their domain. When it's weak, they think about the software — burning cognitive resources on orientation instead of investigation.

Concrete Feature Patterns​

Investigation History​

Users need to see where they've been. Not just undo history — a visible trail of the investigation itself.2 What queries have been run? What views examined? What filters applied and removed? Investigation history should be navigable; users should be able to return to any previous state and branch 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.

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 — arranging elements, hiding irrelevant items, highlighting important ones, 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. Rather than a fixed workflow start, 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 cues that answer "where am I?" without requiring the user to actively query for it:

  • 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

Wayfinding Across Sessions​

Complex professional work spans days, weeks, or months. Wayfinding must survive across sessions, not just within them. 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

The Cost of Poor Wayfinding​

When wayfinding is inadequate, the symptoms are unmistakable: users pause frequently to orient themselves; they repeat work they've already done because they can't find it; they maintain external notes and documents to track their own progress; and they become conservative — sticking to familiar paths rather than exploring, because getting lost feels too expensive.

Every one of these behaviours represents cognitive resources spent on navigation rather than on the work itself. That's the real cost: not frustration, but diminished thinking.

Footnotes​

  1. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. This four-question framing is the author's synthesis of Mirel's wayfinding research, not a direct quotation. ↩

  2. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. The investigation-history pattern described here is the author's elaboration on Mirel's account of wayfinding support in professional problem-solving software. ↩

  3. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. Bookmarkable states, as described here, are the author's elaboration on Mirel's wayfinding framework. ↩

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

  5. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. Multiple entry points, as articulated here, extend Mirel's account of non-linear navigation in professional software. ↩