Information Architecture Process: Six Stages from Scoping to Maintenance
By UXbeam · Information architecture tools since 2021
A strong information architecture process answers a practical question: how do you move from a collection of content and competing opinions to a structure people can navigate? Start with the tasks that matter, investigate the grouping and labels, test candidate routes, then carry those decisions into design and maintenance.
These six stages cover organizing, labeling, navigation and search for a new product or an existing one. Follow the complete process, or use the smaller version when the decision calls for a lighter effort.
The process in brief
Agree the decision the structure must settle, who makes it and how results will be judged.
- Needs
- Business goals or the symptoms you already see; what the platform can change.
- Produces
- One-sentence decisionPriority tasksEvaluation criteria
Find out what people need, what content exists and where the current structure fails.
- Needs
- Analytics, site-search logs and support themes; the pages, screens or features in scope.
- Produces
- Research inputsContent inventory and auditBaseline tree test
Group the content, name the groups in people's words and draft the structure.
- Needs
- The priority tasks and the inventory; a card sort when grouping or terms are uncertain.
- Produces
- Card-sort findingsCandidate sitemapTaxonomy termsDecision log
Check whether people can find the priority items in the draft structure, then revise it.
- Needs
- The candidate structure; tasks written around real goals, not the labels.
- Produces
- Tree-test findingsRevised structure
Turn the tested structure into navigation, search behaviour and screens.
- Needs
- The tested structure with its open questions; the words people used in research.
- Produces
- Navigation specificationSearch synonymsUser flowsWireframes
Move the content, redirect changed addresses, measure again and keep the structure governed.
- Needs
- Every affected URL; an owner for each part of the structure.
- Produces
- Migration map and redirectsGovernance rulesPost-launch measurements
Produces links point to the matching entry in information architecture deliverables.
Explore the six stages
Choose whether you're building something new or improving an existing structure. The guidance changes with your choice, but all six stages remain available.
- Decide and scopeIs the work needed, and what is it for?
- Discover and assessWhat do people need, and what exists?
- Organize and labelHow should content be grouped and labeled?
- Test and refineCan people find things through the structure?
- Translate into designHow does the structure become screens?
- Launch, measure and maintainHow will the structure stay useful?
- From stage 4 back to stage 3: test paths suggest a grouping or labeling problem that needs investigation.
- From 6 back to 2: after launch, new content, searches or support questions show gaps the structure does not cover.
Select a stage to see what it decides and produces, or read all six stages below.
Decide and scope
Is structural work needed, and what is it for?
- Decides
- Whether IA work is needed, which parts can change, who has the final say and what evidence would settle the decision.
- Produces
- A written decision, clear boundaries, a named decision-maker and, when testing, criteria for keeping or changing the structure.
- Building something new
- List what the product must contain or let people do, and the decision the structure must settle, such as which main sections to have and what to call them.
- Improving something that exists
- Start from symptoms you already see, such as support questions, search terms and complaints, and check whether the structure is the problem at all.
- Complete when
- The decision-maker has agreed the question and scope, and any planned evaluation criteria are recorded.
Name the decision before picking the method. 'Make things easier to find' gives you little to evaluate; 'help visitors locate branch opening hours' gives you a task, a destination and a question you can test. Agree what can change and what evidence would justify keeping or revising the structure. For an existing product, the IA assessment's triage helps separate structural issues from content, interface and search issues.
What to prepare before you start
- Analytics, site-search logs and support or enquiry data, if available.
- A list of the pages or screens you have, or of the features you plan.
- What the platform or content management system can and cannot change.
- People who can take part in studies, from each audience the decision affects.
- The person who can resolve disputed placements.
Agree how you will judge the results
Before testing a candidate, agree what would make you keep it, change it or test another version. Otherwise it's easy to explain away results that challenge a preferred structure. Exploratory research starts with an open question; it doesn't need a pass mark. See “Deciding when you have enough evidence” for the stopping rule.
Library example (illustrative)
The example follows the fictional city library site from information architecture deliverables, using the same item IDs: INV- for inventory rows, N- for structure nodes, T- for taxonomy terms and D- for decisions. The decision: how to organize the top level of the site and where each existing page goes. New top-level sections need the web steering group's approval, as the governance rules in that example record.
Discover and assess
What do people need, what exists, and what is missing?
- Decides
- Which tasks matter most, which content and features the structure must hold, where the current structure fails, and what is still unknown.
- Produces
- Research inputs with sources and dates, a priority-task list, a content inventory and audit where coverage is in question, a baseline for an existing structure, and a list of open questions.
- Building something new
- Start with business goals, user needs, and the content and features planned. Inventory anything already drafted.
- Improving something that exists
- Measure the current structure before changing it, with tasks you can reuse later, and inventory what exists when coverage or duplication is in question. To inspect the current navigation against priority tasks, use the navigation audit worksheet.
- Complete when
- The team agrees on priority tasks, identifies the content each requires and assigns owners to any gaps. The questions still needing research are recorded.
Evidence and methods
| Evidence | What it shows | What to investigate next |
|---|---|---|
| Analytics and site-search logs | Entry pages and navigation paths where tracked, common search terms, and searches that return no results. | What people were trying to do, and whether they tried browsing before searching. |
| Support tickets and enquiries | Recurring problems, described in people's own words. | How widely the problem occurs among people who never contact support. |
| Top-tasks research | Which small set of tasks matters most to the people you serve. | How to group and label content so people can complete those tasks. |
| Content inventory and audit | What exists, and what should happen to each item. | Where people expect to find those items in the navigation. |
| Baseline tree test (existing structure) | How findable priority items are in the current structure, task by task. | What explains a missed route and whether live-interface cues affect it. |
Map priority tasks to the content that serves them. Missing information becomes a content action; duplicate or outdated pages become inventory decisions; disputed routes become research questions. For migrations, list affected URLs early so moves, merges and redirects are part of the plan from the start.
Move on when
- Each priority task maps to content, or its gap is recorded with an owner or a decision.
- Each open question names a user need, disputed item or label that a study could investigate.
Go back to stage 1 if
- The evidence points to a content, interface or search problem rather than a structural one.
Library example (illustrative)
The inventory shows two pages answering the same question: INV-001 "Opening hours" and INV-002 "Hours and locations", with summer hours out of date on the second. INV-004, a 2019 renovation update, serves no current task. Site search shows people typing "story hour" for events the library calls "Storytime".
Organize and label
How should content be grouped, and what should the groups be called?
- Decides
- The organizing principle, the groups, the labels people understand, and which candidate structures to test.
- Produces
- A candidate structure, with alternatives where a choice is unresolved, preferred terms with the variants people use, and the reasons behind each decision in a decision log.
- Building something new
- When grouping or terminology is uncertain, an open card sort can help show how participants group items and name those groups.
- Improving something that exists
- A closed sort tests placement into categories you provide. A hybrid sort also lets participants introduce categories that are missing.
- Complete when
- You have at least one candidate structure backed by evidence and labeled with words people use, plus alternatives where a real choice is still open.
Evidence and methods
| Method | What it contributes | What to validate next |
|---|---|---|
| Open card sorting | How participants group items, and the names they give the groups. | Test whether people can find priority items in the candidate navigation built from the groups. |
| Closed card sorting | Where people place items among categories you supply, and how strongly they agree. | Check whether the supplied categories cover users' needs and support navigation tasks. |
| Hybrid card sorting | Where participants use supplied categories and where they propose new ones. | Resolve the proposed alternatives in a candidate structure, then test findability. |
Card sorting gives you evidence for a choice that usually creates disagreement: should people find things by topic, by task, by audience or by another organizing principle? Examine the groupings and the language participants used. Turn the strongest plausible patterns into candidate hierarchies, then test them against the same important tasks.
Participants sometimes organize the same content in distinct, coherent ways: one group may use topics, while another organizes around the action they came to take. UXbeam's Mental Model Detection reports the patterns separately, with their category names and the cards placed differently. Either can be opened as an editable sitemap and evaluated through tree testing.
For products serving several roles or audiences, one option is a structure built around shared tasks with a separate section only where an audience's needs differ; another is separate entry points per audience. Sketch both options and test them. Use the language people used in research for label candidates, and keep internal terms as search synonyms where useful.
Move on when
- The candidate, and any alternative, is complete enough to test the priority tasks.
- Every disputed placement is written down as a question the test can answer.
Go back to stage 2 if
- Items keep landing nowhere because the content behind them is unclear or missing.
Library example (illustrative)
Decision D-01: organize the top level primarily by task, with one audience-specific section, Kids and teens, for services that do not fit the shared tasks. The preferred term is "Storytime" (T-11), with "story hour" kept as a variant for search. One placement stays open: decision D-03, where help for e-books belongs (N-1.3), because the owners disagree.
Test and refine
Can people find things through the structure?
- Decides
- Whether a candidate works for the priority tasks, which candidate to keep, what to change, and whether another round is needed.
- Produces
- Findings for each task, a revised structure, and decision-log entries that close the open questions or record why they stay open.
- Building something new
- Test the candidate hierarchy before designing its screens. Participants navigate a text-only tree to find destinations for realistic tasks, revealing first choices, backtracking, wrong destinations and routes to success.
- Improving something that exists
- Test the current and proposed hierarchies against equivalent tasks when you need a meaningful comparison. The paths show what changed and where a stubborn problem remains.
- Complete when
- The evidence supports a decision to keep or revise the structure, or the decision-maker accepts what is still uncertain.
Evidence and methods
| Method | What it contributes | What to check in the interface |
|---|---|---|
| Tree testing | Where participants go in a text-only hierarchy, whether they reach the intended destination, and the paths they take for the tested tasks. | How layout, visual cues, search or links in the actual interface influence the same tasks. |
A tree test shows which routes participants chose and where they finished for the tasks tested. Use consistent tasks, wording and scoring when you want to compare the effect of a hierarchy change. If those conditions change, identify which task results can still be compared.
Write tasks around what participants want to accomplish, not around the menu label you hope they choose. A good task gives them a reason to navigate; the paths and final destinations reveal where the structure supports that goal and where it sends them elsewhere. See the task-writing and leading-task examples before testing a candidate.
Move on when
- The results meet the criteria agreed before testing.
- What remains uncertain is recorded, with what it would take to settle it.
Go back to an earlier stage if
- Stage 3: wrong destinations or repeated detours may suggest a grouping or label problem; investigate that explanation before revising the structure.
- Stage 2: the findings reveal missing content.
Library example (illustrative)
The open placement D-03, help for e-books (INV-006, node N-1.3), becomes a task that avoids the words in the labels:
You want to read a library title on your tablet tonight. Where would you find out how to set that up?
Test the same goal against the alternative placements. First clicks, routes and final destinations can help the team decide whether e-book help belongs under Borrow or a Help section, closing decision D-03 with test evidence.
Translate into design
How does the structure become navigation and screens?
- Decides
- Which parts of the structure appear in which navigation, what each screen must hold, and what search returns for the words people use.
- Produces
- A sitemap or structure specification, a navigation specification, search synonyms and low-fidelity wireframes.
- Building something new
- Hand the tested structure to design with the decisions and open questions attached.
- Improving something that exists
- For affected content, record what moves, merges, remains or retires, with redirect mappings where URLs change.
- Complete when
- Design accepts the handoff: the structure, its labels, the navigation rules and the open questions.
Carry the tested hierarchy into the actual interface. Specify which nodes appear in global and local navigation, how search handles alternate terms, and what each key page needs to accomplish. From sitemap to wireframe shows how those decisions become layouts and task paths.
A first-click test adds another perspective: what people select when the hierarchy appears inside an interface. Read it alongside tree-test paths to decide whether the next change belongs in the structure, its labels or its presentation.
Move on when
- The handoff checklist is complete and design has accepted it.
Go back to stage 4 if
- A design constraint forces a structural change: test the changed part again.
Library example (illustrative)
The global navigation shows the six top-level sections, N-1 to N-6. Search maps "story hour" to Storytime (T-11). The migration map merges INV-001 and INV-002 into "Hours and locations" (N-2.1) and retires INV-004.
Launch, measure and maintain
How will the structure stay useful?
- Decides
- How content and links move to the new structure, what to watch after launch, who may change the structure, and when to revisit decisions.
- Produces
- An implementation or handoff plan, redirects where addresses move, an owner for each part of the structure, governance rules, a decision log kept up to date, and a plan for measuring again.
- Building something new
- Set owners and rules for adding sections and terms before content starts to grow.
- Improving something that exists
- Record what happens to each affected page or screen, redirect changed URLs where needed, and compare post-launch findings with any available baseline.
- Complete when
- The next review is scheduled and the events that would trigger an earlier one are recorded.
Launch and migration
Record what happens to affected content: what remains, moves, merges or retires. Redirect changed URLs where needed, keep important old terms findable through search, and brief support teams before consequential changes go live.
Measure after launch
The first release gives you a new baseline for the next decision. Revisit the priority tasks, watch site-search terms and support requests, and investigate new trouble spots as content grows. When comparing study rounds, keep scoring and test format consistent and describe what each revised round achieved.
Maintain the structure
New pages, services and labels keep arriving after launch. Without clear ownership, teams start adding sections or renaming categories case by case. Your decision log and governance rules should record why changes were made, who can approve them and when a wider review is needed.
Signs the structure is holding
- Re-measured tasks hold or improve, and new content finds a home under the rules.
Go back to stage 2 if
- New content, searches or support questions show gaps the structure does not cover.
Library example (illustrative)
Any team may propose a new top-level section; the web steering group approves it, records it in the decision log and reviews it before the section launches. Decision D-01 is to be revisited if a new audience-only service area is added.
Deciding when you have enough evidence
More research is valuable only when it could change what you do next. Decide which tasks matter, whether competing structures perform differently on those tasks and what an additional round would resolve. When the evidence already supports the next choice, make it.
- For evaluations, use the decision rule agreed at the outset. Identify the tasks or outcomes that matter and which structures, if any, are being compared.
- Read mixed results by task. One candidate can be better for some tasks and worse for others. Decide task by task, and test a combined structure if the strengths sit in different places.
- When another round would not change the decision, stop. Record the remaining question and what new evidence would justify reopening it.
For participant and task-count guidance, see the information architecture assessment.
A smaller version of the process
A smaller team can preserve the key decisions and keep the working documents lean. Use this table to prioritize what is essential now and what to revisit as the project grows.
| Stage | Essential | Can shrink | When to expand |
|---|---|---|---|
| 1 Decide and scope | The one-sentence decision, a named decision-maker, and an evaluation rule when needed | Formal success measures | Add a clear success measure before comparing results or justifying a high-risk change. |
| 2 Discover and assess | Priority tasks and existing evidence; for a migration, all affected URLs | A full inventory beyond the tasks and affected URLs | Expand the inventory when coverage gaps, duplicates or additional sections enter scope. |
| 3 Organize and label | At least one written candidate structure, labeled with people's words | Card sorting, if the groups are not in dispute | Run a card sort when multiple plausible groupings emerge or audience expectations are uncertain. |
| 4 Test and refine | Evidence on the structural question, from a method that fits it: a tree test when the question is whether people can find things in the hierarchy | Extra rounds and second candidates | Test another candidate or iteration when the next decision requires a meaningful comparison. |
| 5 Translate into design | The structure and labels handed to design with open questions | A separate navigation specification | Document navigation rules when several people need to implement the experience consistently. |
| 6 Launch, measure and maintain | A planned implementation or handoff, a named owner, and redirects or a migration when addresses move | A full governance document | Formalize governance rules as publishing volume, ownership or the number of editors grows. |
What makes the work take longer
- The size of the content or feature set, and how many teams own parts of it.
- How many audiences or roles need separate evidence.
- How long reviews and approvals take, and how many decision-makers there are.
- How hard it is to recruit participants from each audience.
- How many rounds of testing the decision rule requires.
Doing it yourself or bringing in help
Focused card sorts and tree tests are workable for small teams. For consequential or ambiguous findings, an experienced researcher's second interpretation can help settle task-wording issues, mixed results or a high-risk decision. The core workflow remains the same: define the question, inspect the evidence and make the next decision.
Where to go next
- Information architecture assessmentEvaluate an existing structure using the evidence you have, and decide what to test next.
- Information architecture deliverablesSee the artifacts an IA project needs, with examples and reusable templates.
- Card Sorting GuideDiscover how people group and name your content. Explore open, closed and hybrid card sorting, analyze the results, and use the findings to inform a sitemap.
- Tree Testing GuideCheck whether people can find things in a structure, using text-only labels and realistic tasks, before any design exists.
- From sitemap to wireframeTurn a tested sitemap into navigation, screen priorities and task paths.
- Organizing principlesWhen the rule itself is in question: should this be organized by topic, by task, by audience or by life event?
- From card sorting to sitemap to tree testingUse card sorting to explore groups and labels, then tree testing to check whether people can find things.
Sources
- Kaley, A. "Content Inventory and Auditing 101." Nielsen Norman Group, 2020.
- Farrell, S. "Site-Search Log Analysis." Nielsen Norman Group, 2017.
- Wiggins, R. and Rosenfeld, L. "Using Search Analytics to Diagnose What's Ailing Your Information Architecture." IA Summit, 2007.
- Canada.ca Experience Office. "How we're optimizing Canada.ca top tasks." 2017.
- Wake, L. "Top task performance indicators." University of St Andrews Digital Communications, 2017 (reporting Gerry McGovern's method).
- Tankala, S. and Sherwin, K. "Card Sorting: Uncover Users' Mental Models for Better Information Architecture." Nielsen Norman Group, 2024.
- Spencer, D. and Warfel, T. "Card Sorting: A Definitive Guide." Boxes and Arrows, 2004.
- Laubheimer, P. "Tree Testing: Fast, Iterative Evaluation of Menu Labels and Categories." Nielsen Norman Group, 2023.
- O'Brien, D. "Tree Testing." Boxes and Arrows, 2009.
- Kuric, E., Demcak, P. and Krajcovic, M. "Validation of information architecture: cross-methodological comparison of tree testing variants and prototype user testing." Information and Software Technology.
- Sauro, J., Schiavone, W., Du, D. and Lewis, J. "Do Click Tests Predict Live-Site Clicks?" MeasuringU, 2023.
- Mann, D. "The art of redirection." Inside GOV.UK, 2014.
- Nygard, M. "Documenting Architecture Decisions." 2011.