Information architecture is the practice of organizing, structuring, and labeling content so that people can find what they need and understand what they find. In writing, information architecture is the structural layer between individual sentences and the full document — the headings, sections, cross-references, and navigation that determine whether a reader can locate and use the information a document contains.
Peter Morville and Louis Rosenfeld defined information architecture through four components: organization systems (how content is grouped), labeling systems (what things are called), navigation systems (how users move through content), and search systems (how users look for specific items). These components apply to websites, documentation sets, and individual documents alike.
Jorge Arango extended this framework by arguing that digital information systems are environments people inhabit — not tools they pick up and put down — which means their structure carries ethical responsibility [@arango2018].
In technical writing, information architecture governs decisions like:
- Heading hierarchy — the plain language specification requires headings that are specific and useful on their own (section 5.4), functioning as a table of contents. This is an IA decision.
- Progressive disclosure — showing the most important information first and letting the reader drill down for detail. Index pages that orient before linking, and lessons that build from concrete to abstract, both use progressive disclosure.
- Cross-referencing — deciding what links to what. In this vault, internal links create a navigational structure that’s as much an IA decision as a writing decision.
- Content types as structure — the vault’s genres (term definitions, lessons, specifications, index pages) are IA structures: each type has a predictable organization that helps the reader know where to find what.
Information architecture connects to cognitive load theory: well-organized content reduces the extraneous load of searching and orienting, leaving more working memory for understanding the material itself [@sweller1988]. Poorly organized content — scattered information, vague headings, missing navigation — increases load regardless of prose quality.
The design module’s information architecture discipline develops these principles in detail, covering controlled vocabularies, faceted classification, and wayfinding. The writing module’s concern with IA is narrower: how to structure a document or document set so that readers with specific needs can find and use the content.
Related terms
- document design — document design includes IA but extends to visual presentation
- progressive disclosure — an IA strategy for managing complexity
- task analysis — task analysis determines what information readers need; IA determines where to put it
- genre — genres are IA structures that encode reader expectations
- cognitive load — good IA reduces extraneous cognitive load
- audience — IA decisions depend on what the audience needs and how they look for it