📄️ Introduction
Information Architecture in complex professional software has almost nothing in common with IA on the web. Web IA organises content so people can find it — navigation hierarchies, taxonomies, search. Complex software IA organises the working environment so people can do their work: maintaining orientation across multi-session investigations, supporting non-linear exploration, and managing multiple simultaneous representations of the same data.
📄️ Task Landscapes
Traditional software design decomposes work into task hierarchies — goals into sub-goals, sub-goals into steps, steps into actions. Neat, logical, and perfectly suited to linear, well-structured tasks. For complex professional work, it's a fantasy.
📄️ 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."
📄️ Multiple Representations
Professional software shows the same data through multiple lenses at once, echoing Mirel's observation that expert problem solvers hold structural, functional, and organisational representations of their work and need to move between them fluidly. A 3D application might present a viewport (spatial), a properties panel (parametric), a timeline (temporal), a node graph (procedural), a scene hierarchy (structural), and a render preview (output) — all facets of one scene. A video editor does something similar with its timeline, source monitor, program monitor, effects panel, and audio mixer. This is the norm, not the exception.