Theory
The library with no sections
Imagine a library where books are simply piled by arrival date: no fiction section, no subject shelves, no labels. Every book is THERE, but finding one is hopeless.
FestConnect can be exactly this: events, schedule, rules, my-registrations, contact, all present but organised badly, so Rahul cannot find where to register. No amount of beautiful buttons fixes it, because the problem is deeper than the surface: it is the STRUCTURE.
That structure has a name: information architecture: the invisible skeleton that decides whether users can find anything at all.
Theory
Information architecture, formally
Information architecture (IA) is the practice of organising, structuring and labelling content so that users can find information and complete tasks.
It is the product's SKELETON: invisible when good, crippling when bad. Its main components:
- organization: how content is grouped and categorised (by topic, task, or audience)
- labeling: naming things in the USER's language, not internal jargon
- navigation: how users move through the structure (next lesson)
- search: finding content directly
Good IA means Rahul thinks 'registration must be under Events' and it IS: the structure matches his expectation.
Theory
Card sorting: let users organise it
How do you discover the RIGHT structure? Not by guessing: with card sorting. You write each piece of content on a card (Events, Schedule, My Registrations, Rules, Contact) and ask REAL users to GROUP and LABEL them the way THEY expect.
The result reveals the users' mental model: maybe first-years expect 'Register' as its own top item, not buried under 'Events'. You then build the IA around what they showed you, not what seemed logical to you.
The output is often a sitemap: a map of the content hierarchy, broad categories branching to specific pages. Card sorting discovers the structure; the sitemap documents it: both are core IA tools.
Quiz
FestConnect's screens are beautifully designed, but users still cannot find where to register. What is most likely the real problem?
- The colours are wrong
- The information architecture: content is organised or labelled so users cannot find what they need
- The app needs more animations
- The font size is too large
- Nothing: if it looks good, it works
Show the answer
The information architecture: content is organised or labelled so users cannot find what they need
When users cannot FIND things despite attractive screens, the failure is structural, not visual: the information architecture (how content is organised and labelled) does not match how users look for things. This is IA's defining lesson: no amount of visual polish rescues a broken structure, because finding-ability lives beneath the surface. Options A, C and D are all VISUAL tweaks that cannot fix a findability problem. Option E is the pretty-equals-usable myth the whole subject refutes. IA is invisible when it works and fatal when it fails: register-not-findable is an IA problem.
Think first
Why let users sort the cards?
You already know FestConnect's content perfectly. Why bother asking students to card-sort it instead of just organising it yourself? Then tap.
Show the answer
Because YOU organise it by how the SYSTEM (or your own expert knowledge) thinks: you know 'registration' is technically part of 'event management', so you nest it there. But Rahul does not think like the system: to him, REGISTER is the main thing he came to do, and he expects it front and centre, not buried. Card sorting surfaces the users' mental model, which is usually DIFFERENT from the expert's: the you-are-not-your-user principle applied to structure. You design IA around how users EXPECT to find things, discovered through card sorting, not around your own internal logic.
Watch out
IA slips
Internal-jargon labels: naming a section by your database table or org chart ('User Records') instead of the user's word ('My Registrations') buries content in plain sight.
Organising by YOUR logic: structure by the USER's mental model (card sorting), not the system's.
Too deep: burying key content 5 taps down; keep hierarchies shallow enough to reach quickly.
Confusing IA with visual design: IA is STRUCTURE (findability); prettiness cannot fix bad structure.
Theory
From structure to the visible path
Information architecture is the invisible skeleton; users experience it through the VISIBLE thing built on top: navigation: menus, tabs, links, breadcrumbs. Before designing the navigation and the screens, though, designers sketch the structure cheaply as WIREFRAMES: the blueprint. The next lesson covers low-fidelity wireframes and prototypes (design cheaply before committing), and then navigation systems (the visible expression of this IA).
Summary
Key takeaways
- Information architecture (IA) organises, structures and labels content so users can find things and complete tasks.
- It is the invisible skeleton: unnoticed when good, crippling when bad; visual polish cannot fix bad IA.
- Components: organization (grouping), labeling (user's language), navigation, search.
- Card sorting has real users group and label content to reveal their mental model.
- A sitemap documents the content hierarchy (broad categories to specific pages).
- Organise around the USER's expectations, not the system's or your own internal logic.
- Memory hook: IA is the library's sections and labels; without it, everything is a pile.