Information Architecture

Information Architecture (IA) is the practice of organising, structuring, and labelling content so that users can find what they need and complete their tasks efficiently. It is the invisible foundation that determines whether a product feels intuitive or confusing.

---

Why Information Architecture Matters

Even the most beautiful interface fails if users cannot find what they are looking for:

• Findability — users can locate the content or feature they need
• Understandability — users comprehend the structure and labels without explanation
• Scalability — the structure accommodates growth without becoming unwieldy
• Efficiency — common tasks require fewer clicks and less cognitive effort
• Reduced support costs — clear IA reduces confusion and support requests

Key Insight: If users cannot find it, it does not exist — regardless of how well it is designed.

---

Core Components of IA

Information Architecture has four key components, as defined by the "polar bear book" (Rosenfeld, Morville, and Arango):

Component	Description	Example
Organisation systems	How content is categorised and grouped	Alphabetical, chronological, by topic, by audience
Labelling systems	How content is named and described	Navigation labels, headings, link text
Navigation systems	How users move through the structure	Main nav, breadcrumbs, footer links, search
Search systems	How users query and filter content	Search bar, filters, faceted search, autocomplete

---

Organisation Schemes

Exact Schemes

Content is organised by an objective, unambiguous criterion:

Scheme	Description	Example
Alphabetical	Sorted A-Z	Dictionary, contact list
Chronological	Sorted by date	Blog posts, news feed
Geographical	Sorted by location	Store locator, weather app
Numerical	Sorted by number	Leaderboard, price list

Ambiguous Schemes

Content is organised by subjective grouping — harder to create but often more useful:

Scheme	Description	Example
By topic	Grouped by subject matter	Wikipedia categories, course catalogue
By task	Grouped by what the user wants to do	Online banking (Pay, Transfer, Invest)
By audience	Grouped by user type	"For Students", "For Teachers", "For Parents"
By metaphor	Grouped using a familiar concept	Desktop (files, folders, recycle bin)

---

Navigation Patterns

Types of Navigation

Pattern	Description	When to Use
Global navigation	Persistent nav bar visible on every page	Primary sections of a website or app
Local navigation	Navigation within a section	Sub-pages within a category
Breadcrumbs	Shows the user's path from the homepage	Deep hierarchies with many levels
Contextual links	In-content links to related pages	Blog posts, documentation
Faceted navigation	Filters that narrow results by attributes	E-commerce product listings
Search	Free-text query to find content directly	Large content libraries
Footer navigation	Links at the bottom of every page	Secondary pages (legal, about, contact)

Navigation Best Practices

• Limit top-level navigation to 5-7 items (Miller's Law)
• Use clear, descriptive labels — avoid jargon and clever names
• Show the user's current location (highlight active nav item)
• Provide multiple paths to important content
• Ensure navigation is consistent across the entire product

---

Card Sorting

Card sorting is a research technique for discovering how users naturally group and label content.