Skip to main content

Information Architecture for Complex Software

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, using navigation hierarchies, taxonomies and 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.

The shift is from content organisation to work organisation.1 Your users are investigating, creating, analysing and iterating. Their IA needs to support the way professional work unfolds: with backtracking, parallel exploration, provisional judgements, and goals that emerge only as the work progresses.

Three Architectures Working Together​

Complex software requires three types of architecture to work together:2

Data Architecture​

How data is structured, connected, and accessed across the application. Professional tools draw data from multiple sources, in multiple formats, with complex interdependencies. Your data architecture determines whether users can cross-reference information directly or must manually export, transform and reimport it between disconnected views. The latter is all too common.

How users move through the application's capabilities and their own work, using entry points, wayfinding cues and movement patterns. In non-linear software, navigation must support configurable traversal of a problem space. Users need to go where the work takes them, which a fixed sitemap cannot predict.

Representational Architecture​

How the same underlying data appears through multiple views. Professional software typically maintains 4–6 simultaneous representations: a spatial view, a properties panel, a timeline, a node graph, a data table, an output preview. The representational architecture determines how these stay synchronised, how changes propagate, and how users move between them without losing context.

Applying Context to Information Architecture​

The Context chapter explains Mirel’s ICV model: Interactivity, Contexts and Variability.1 For information architecture, the practical consequence is that the workspace must support changing goals and conditions. Users need routes suited to the work currently possible, views that preserve relevant context, and structures that accommodate both established conventions and emerging needs.

What This Section Covers​

The following pages explore the key concepts for designing IA in complex professional software:

  • Task Landscapes — The unit of design for non-linear workflows, replacing traditional task hierarchies
  • Wayfinding — How users maintain orientation and navigate complex problem spaces
  • Multiple Representations — Managing simultaneous views of the same data

Footnotes​

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

  2. Mirel, B. (2004). Interaction Design for Complex Problem Solving: Developing Useful and Usable Software. Morgan Kaufmann. The three-architecture split (data, navigational, representational) is the author's synthesis, built on Mirel's account of complex problem solving rather than terminology drawn directly from her text. ↩