Information architecture / Assessment

Information architecture assessment

An information architecture assessment tells you where navigation trouble starts and what to investigate next. Examine the content, grouping, labels and hierarchy; combine existing evidence with focused participant research; then decide whether the next move is to rename, restructure, retest or fix something outside the navigation.

An information architecture audit checks an existing structure for coverage, grouping, labels and navigation. An IA assessment brings those findings together with research evidence to decide what to improve and test next.

Methods for assessing information architecture

A structural review identifies potential problems in the hierarchy and content coverage. Card sorting investigates how people group and name the content; tree testing shows the paths they take through a proposed hierarchy. When the problem may depend on what appears on screen, first-click or usability testing examines the interface itself.

Review the existing site

Test with participants

  • Tree testing

    Can people find important destinations using the hierarchy alone?

  • Card sorting

    How do people group and label content? Do the proposed categories make sense?

  • First-click and usability testing

    Where do people click on actual screens, and what prevents them from completing tasks?

How much assessment do you need?

Match the effort to the decision. Existing analytics and support evidence may already identify a narrow problem. A focused card sort or tree test can investigate an unresolved grouping or navigation question. Compare structures or test actual screens when that is what the decision requires.

ApproachWhat it involvesWhat it helps you decide
Review existing evidenceExamine the current structure, content, analytics, search logs and support feedback.Where the likely IA problems are and what needs further investigation.
Run a focused studyUse tree testing for findability or card sorting to investigate grouping and labels.Whether a specific part of the IA needs to change.
Compare alternatives or test the interfaceCompare candidate structures using equivalent tasks, or test navigation on actual screens.Which structure works better, or whether the interface contributes to navigation difficulties.

Example: comparing two structures
An open card sort for a connected-car interface suggested two ways to organize the same features. The team built a navigation structure for each and tested both. Read the example.

Is it an IA problem, and which part?

A failed search, a wrong click or an abandoned task can arise from different parts of the experience. The table pairs each symptom with the first area to investigate and the evidence that helps distinguish labeling, missing content, search behavior and interface problems.

Inside the structureCoverageGroupingLabelsHierarchy and depth

Outside itInterface and navigation designThe search systemContent qualityGovernance

What you seeLikely partFirst checkWhere evidence may already exist
Frequent searches for content already in navigationLabels, or hierarchy and depthCompare query terms with route labelsSite-search logs
Findability complaints about content that existsLabels, or hierarchy and depthEntry pages and required navigation pathSupport contacts; analytics entry pages
Zero-result searches for content you do not offerCoverageConfirm the content is really absent, not just named differentlySite-search logs; the content owner
The same content exists in several placesCoverageWhich version receives traffic, and which one is currentContent inventory; analytics
Teams disagree about where something belongsGroupingExpected placement in one or multiple categoriesEarlier card sorts; support vocabulary
Correct section, wrong final destinationLabelsWhich neighbouring item they pick instead, and how its label comparesEarlier tree tests; analytics paths
Some content is reachable only through search or a direct linkHierarchy and depthWhether those tasks require a browse path to the contentInventory (pages with no links to them); analytics referrers
Users miss an item that is present in the live navigationOutside the structure: interface and navigation designFindability without interface cuesA tree test of the same task; compare with usability sessions on the live interface
Search finds the page but ranks it low, or returns irrelevant resultsOutside the structure: the search systemWhat the top queries actually returnSite-search logs
Users reach the page, but the content does not resolve the taskOutside the structure: content qualityTask-content fitSupport contacts; page feedback
Labels and placement drift as different teams add pagesOutside the structure: governanceWho decides where new content goesPublishing records

Four parts of the IA to inspect

Organize findings into four areas: coverage, grouping, labels, and hierarchy and depth.

PartIts questionTypical evidence
CoverageDoes the structure cover content required for priority tasks?Zero-result searches, support themes, an inventory where warranted 56
GroupingDo groupings match user expectations?Card sorts; incorrect tree-test destinations 47
LabelsDo labels support correct first clicks and destinations?Search vocabulary; first clicks 16
Hierarchy and depthAre target destinations findable through the hierarchy alone?Tree tests 128
  • Card sorting helps investigate how participants group content; tree testing evaluates whether people can navigate a proposed hierarchy. 14
  • A tree test examines the navigation structure without the surrounding interface. Usability testing shows how navigation works with the interface and page content. 3

A tree test measures findability: success in locating an expected destination through the structure 3.

Run the assessment in five steps

Work from the decision outward. Collect what you already know, locate the unresolved question and test only when the next decision needs more evidence. You can finish an assessment without commissioning a new participant study.

Copied

1. Define the decision and what can change

Write the decision in one sentence, for example "keep or replace the top-level menu before the spring release". Then list what is fixed (platform limits, legal names, deadlines), what can change, and who decides. That sets the scope, while evidence may still be needed to distinguish an IA problem from another cause.

Questions to answer before going further:

  • Which audiences matter most?
  • What would make the decision obvious?

Name the decision-maker and the changes they can act on before you commission further research. That makes every result easier to turn into a concrete next step.

2. Gather what you already have

Start with the evidence your organization has already collected: top tasks, search terms, support questions, analytics, previous studies and the current structure. The table shows who usually owns each source and what it can contribute, so you can assemble a useful assessment without duplicating research.

MaterialStatusWho usually has itMinimum useful amountUse it toInterpretation / next step
The decision and what can changeRequiredSponsor or product ownerOne sentence plus constraintsSet the scopeDefines the decision; findings must come from evidence
The structure: the current tree, the draft if you are comparing, tags if you use themRequiredCMS or product ownerEvery level you will testSee shape, labels and depthUse participant testing to assess findability 1
Top tasks and who does themRequired for any test with participantsProduct, support, analyticsThe tasks that matter most, by audienceChoose tasks and participantsResults apply to the tasks selected
Site-search logsUseful; start here if the site has searchSearch or analytics ownerThe top 1,000 queries over 3 to 6 months; work through the first 300 or so 6Identify search vocabulary and possible content gapsCheck whose searches are represented before generalizing 10
Support and contact themesUsefulSupport leadRecent contacts, tagged by themeCapture support language and reported problemsCheck broader evidence before estimating prevalence
AnalyticsUsefulAnalytics ownerTop entry pages and most-used pagesIdentify high-use content and entry pagesInvestigate motivations separately when they matter 9
Earlier research, including any baselineUseful; required to claim improvementResearch repositoryDate, tasks, number of participants, test formatReuse tasks and starting questionsUse as a comparison baseline when study conditions are comparable
Content inventoryConditionalCMS ownerA sample, or one section, within a fixed timeCheck coverage, duplication, outdated content, and pages with no inbound linksUse a tree test to assess navigation findability 5

Start with the pages and sections implicated by the decision. Expand to a fuller content inventory when coverage, duplication, ownership or missing navigation paths require it. 5

Reuse earlier tree-test tasks when they still describe the job well. Improve the ones that were leading, compound or vague. Tasks you write now become the baseline for the next round.

Participants, if you will need them

  • Who: participants from each audience the decision affects. Results from one audience do not generalize to another.
  • Where from: recruit participants who represent the target audience for the decision. Colleagues can help pilot the tasks; include their results in the study only when they genuinely fit that audience and familiarity does not bias the task.
  • How many depends on the purpose. A qualitative pilot needs a few participants 1. For quantitative tree testing, about 30 participants seeing each task can start to show patterns within an audience, and about 50 seeing each task is a common target 11. If each participant sees only part of the task bank, recruit proportionately more participants so each task still gets that coverage. Comparing two structures typically needs about 50 or more observations per task, per structure for reasonably narrow confidence intervals 2. Each step up adds recruitment cost and time.

Review the structure itself

Trace the routes people would use for priority tasks and look for structural features that deserve investigation: ambiguous siblings, content without a browse route, unexpected depth and items with several plausible homes. The same pattern can be useful in one context and troublesome in another, so use it to form questions rather than assign automatic penalties. 12

ConditionWhy lookWhen it can work well
The same page reachable by several routesMultiple routes split behavior and make measurement ambiguous unless the route is knownOften intentional and helpful, especially where audiences differ
Content reachable only by search or a direct linkNo browse path reaches the contentSometimes correct by design: deep reference material, archives, or content reached from external links
A branch with a single childA level that offers no choice costs a stepIt can give useful context or a stable address, or leave room to grow
Siblings of different kinds at one levelThe grouping principle may be inconsistent at this levelA prominent task next to topic sections can be deliberate
One section holds a large share of the itemsThe grouping may have become too broadUneven section sizes may reflect the domain
Items with more than one plausible homeA good source of tasks to testTwo plausible homes are normal; test expected placement
Important content placed deeplyDeep placement adds navigation effort to important contentDepth alone does not decide findability

To inspect one navigation against your priority tasks and record what you find, use the navigation audit worksheet.

Rules that mislead when applied everywhere

  • Three clicks. What matters is whether each choice is predictable. A clear five-step path can work better than an ambiguous two-step one.
  • Seven plus or minus two per level. This comes from working-memory research, not studies of menu scanning.
  • No more than N levels. There is no universal correct depth.
  • A structure health score. Tree depth and shape do not establish findability.

3. Read the evidence and identify the likely part

Bring complaints, search behavior, prior studies and structural inspection into one view. Sort the findings by coverage, grouping, labels, and hierarchy and depth. Where sources disagree, look at which tasks and audiences each one represents. That often reveals the next specific question to test.

Contradictions to look for

  • Search logs show frequent queries for content already in navigation. The label may not match search vocabulary, the route may be hard to follow, or search may simply be preferred.
  • Support reports findability failures while analytics shows high usage. The support audience may differ or arrive by a different route.
  • An earlier study found no problem, but complaints continue. Check whether it covered the complaint themes with the same audience.
  • The team agrees on placement, but search vocabulary differs from the label. The grouping may be sound while the label is not.

Compare query terms used for the same need and audience. Search logs often use specific-item names rather than category labels: they can reveal vocabulary gaps, but query frequency by itself does not measure browse findability.

What counts as a complaint. Classify a support request as a findability complaint only when it describes a failed attempt to locate content or complete a task.

Coverage gaps in existing evidence. Analytics, search logs and support records cover only observed visits, searches and submitted contacts. If a target audience is absent from those sources, you still lack findability evidence for that audience.

If the existing evidence resolves the decision for the affected audience, record the basis and move to Step 5. For critical or hard-to-reverse changes, confirm that the evidence is strong enough before ending the assessment.

4. Test only what remains open

The table connects each unresolved question to a suitable study, typical sample sizes and the evidence it can produce.

MethodWhat it answersFollow-up evidenceBest next method whenTypical sizeUXbeam
Desk or expert reviewStructural and labeling issues identified by expert reviewTree or usability test for observed task performance 12Observed task performance is needed for the decisionThree or more independent reviewers if you rate severity 13
Open card sortParticipant-generated groupings and category labelsTree-test a candidate navigation 14Placement within fixed categories is the question; use a closed sortAt least 15 participants for a qualitative sort; 30 to 50 or more for a quantitative one; 30 to 50 cards 4✓
Closed or hybrid card sortFit of items within supplied categoriesTree-test routes through the proposed hierarchy 314You need to measure destination findability 4Use the open-sort guidance above 4✓
Tree testFindability, first clicks and navigation paths; comparison between structuresUsability test of interface, search, links and content 2The suspected issue is how the interface presents navigationA few participants for a qualitative pilot 1; about 30 participants seeing each task for early patterns, about 50 as a common target 11; recruit proportionately more if participants see only part of the task bank; comparisons about 50 or more observations per task, per structure 2; 8 to 10 tasks per participant 15✓
First-click testFirst-click choice on a screen or mockupTask-based usability testing for subsequent behavior 3Interactive behaviors such as hover menus need a representative prototype 16
Usability test (prototype or live)Task performance with structure, interface and content combinedTree testing can help isolate hierarchy effects 14The decision requires a structure-only result

For a live hierarchy, start with the evidence you already have and add a baseline tree test when you need to evaluate its routes 1817. If the open question is how people would group the content, a card sort can explore it, and plausible groupings can become candidate structures. Alternatives are compared by tree-testing them on equivalent tasks, and a problem that appears only with the interface calls for testing the screen itself.

Tasks

Take tasks from the top-task list, search logs and support themes. Give each participant 8 to 10 tasks; more can create learning effects 15. Write tasks in user language and avoid tree-label wording; otherwise the task becomes a word-matching exercise 9.

Look for semantic cues as well as exact words. "Your green bin wasn't emptied" can cue the Environment section without sharing its label. When a frequent query matches the label, write the task around the underlying need ("you want to know what a mortgage would cost you each month"), not the query.

More on task design: writing tree test tasks and avoiding leading tasks.

Comparing a current and a proposed structure

Test the current structure as a baseline and the proposed structure with comparable participant groups, the same scoring and the same test format. Carry tasks forward where they still describe the job, and improve the ones that were leading or vague for both structures. See Reading results for how to read the comparison.

What drives effort: the number of audiences, whether you compare structures, task allocation per participant, the size of the tree you test (not the size of the site), and where participants come from.

When the remaining question concerns a different part of the experience, name the evidence you need and send the issue to the right method or owner.

Test a proposed navigation: see which routes participants choose and where they finish.

Start a tree test

Explore content grouping: learn which labels and organizing patterns participants use.

Start a card sort

5. Read the results and decide

Read tree-test results as routes, not just scores. Direct finishes reached the intended destination without backtracking; indirect finishes reached it after backtracking; elsewhere finishes ended at a different destination. Combine those outcomes with first clicks and final destinations to see where the navigation needs attention. 2

When a task's first clicks form a recognizable pattern, UXbeam names it on the task: most participants making the same wrong first choice, two competing first choices, a correct first choice followed by a lost path, or scattered first choices. UXbeam also flags a destination where many attempts ended without being accepted, so the team can review whether it should count.

Patterns to notice

What you seeWhat it might suggestWhat to inspect next
On a low-scoring task, wrong first clicks cluster on one other sectionThat section may match the expected location, or task wording may cue itFinal destinations within that section; task-label word or semantic overlap 2
First clicks are right, but most finish at one or two wrong items in the sectionThe labels at that level may overlap or be near-twinsThe list of final destinations, and how the attracting item's label compares with the correct one 2
First clicks scatter across several sectionsFor one or two tasks, the item may have several plausible homes. For many tasks, the top level may be unclearNumber of tasks affected. For one or two, use moderated think-aloud sessions 8. For many, run an open card sort 2.
Tree-test tasks score well, but findability complaints continueThe test may not have covered the reported problems, or the cause may sit outside the structureEach complaint theme against the tasks you tested; write and test tasks for the themes you missed 23
Repeated zero-result searches for content you do not offerA content-coverage issue, not a structural oneGroup the missing requests by theme and volume, then take them to the content owner 6
Strong card-sort agreement is cited as proof that the menu worksGrouping agreement does not establish findabilityCheck whether shared wording or a leftovers group explains the apparent agreement; then tree-test the proposed structure 1418
The tree test and a test of the live site or prototype disagreeThe two settings expose different routes and cuesObserved routes in each setting, and whether the live route exists in the tested tree 2319
Earlier research used different tasks, wording, scoring, test format or audienceUse it to generate questions and tasks, not as a baselineUnchanged tasks and branches; then apply the comparison conditions below 219

Possible changes, once an inspection supports them: move an item, list it in a second place, rename a section, make two neighbouring labels distinct, fix the content, or hand the problem to the interface or search owner. List an item in a second place only when a substantial share of participants choose that location; doing it everywhere dilutes the structure 2.

How to interpret comparisons and retests

  • Keep scoring, test format and participant audiences consistent between rounds, and report what each revised round achieved, tasks included. A 2025 peer-reviewed study found that different tree-test formats produced significantly different results 19.
  • With modest samples, moderate differences in success, first clicks or final destinations can be uncertain. Assess the uncertainty of the difference between two results, rather than comparing either result against its own margin of error.
  • If a lower score on a critical task would change the decision, plan the study to detect a meaningful difference. Around 50 observations per task and structure is a common starting point for comparisons 2, but a moderate task-level difference may require a larger sample.
  • After each iteration, examine first clicks, paths and destinations to understand what improved and where further changes would help.
  • If a destination originally marked wrong would genuinely satisfy the task, review the accepted-answer key on content grounds. Show both the original and revised scoring. Use the original scoring for a like-for-like comparison and present rescoring as a separate analysis.
  • Set decision thresholds by task importance, audience and the consequences of failure. No single pass mark suits every structure.

When the evidence points elsewhere

  • Content: required content is missing, inaccurate, or duplicated. It goes to the content owner.
  • Interface and navigation design: the item is findable in the tree but not on the live site. Test the interface 3.
  • Search: relevant content exists, but site search returns poor results. Route it to the search owner 6.
  • Grouping: first clicks scatter across many tasks, or placement remains disputed. Run a card sort (card sorting, reading card sort results, organizing principles).

Prioritize findings by task importance and frequency. If you assign severity ratings, use at least three independent raters 13. For content, record whether the next action is to keep, update or remove it 5.

Worked example

Two ways to organize a connected-car app

In five manufacturer apps audited by UXbeam, features were organized by vehicle system, such as climate, security and charging. The Connected Car card sort also revealed a proximity-based grouping: in a 60-participant analysis snapshot, about a quarter organized features by whether the driver was near the car or away from it. The team investigated both organizing principles through tree testing.

Evidence already available. An audit of existing companion apps gave a list of 24 features. None of the audited apps organised features by whether you are near the car.

Card sort. In an open card sort of the 24 features, early results revealed different ways to group them, including by vehicle system and by proximity to the car. In a later snapshot covering the first 60 US adult participants, roughly a quarter had grouped features around whether they were near or away from the vehicle.

Two candidate structures. From the early results, the team developed a candidate navigation structure for each: A followed the vehicle-system convention, B the near-or-away principle. Both held all 24 features.

Tree test. Each structure was tested with a separate group of participants on eight tasks with the same intent, such as starting the car remotely or finding where it is parked. After excluding internal sessions, one outlier, and one participant who completed both tests, 18 participants per structure remained, with 144 attempts each.

Result. Overall success was 60% for A (87 of 144 attempts) and 70% for B (101 of 144). Direct success was identical: 63 of 144 for each.

The near-or-away tree recorded 101 successful attempts to 87 overall. Its lead came from the three tasks that were reworded for it along with the structure (44 to 26); on the five tasks worded the same for both, the vehicle-system tree recorded 61 successes to 57.

On the five identically worded tasks, Direct success was identical: 42 of 90 attempts for each structure.

Where the near-or-away structure's lead came from

Same wording: A 61/90 · B 57/90. Different wording: A 26/54 · B 44/54. All tasks: A 87/144 · B 101/144

Where the near-or-away structure's lead came from
TasksA · Vehicle systemB · Near or away
5 tasks worded the same for both61/9057/90
3 tasks worded differently26/5444/54
All tasks87/144101/144
Successful attempts per structure, with 18 participants each. Five identically worded tasks slightly favored the vehicle-system structure (61/90 versus 57/90); the near-or-away structure led on the three differently worded tasks (44/54 versus 26/54). The overall totals combine both groups.

Remote unlocking gives the team a specific question for the next round: 11 of 18 participants reached the right destination directly in the near-or-away structure, compared with 3 of 18 in the vehicle-system structure.

The next round can carry the near-or-away structure forward with its revised tasks, recruit enough participants for the importance of the decision, and compare paths and destinations task by task before choosing or combining elements from the structures.

A second case: an e-commerce admin, three rounds

Another UXbeam study tested an e-commerce admin navigation in three versions. Between the first two, the overall average barely moved despite marked changes on particular tasks, and the clearest next move came from a cluster of wrong destinations attracted by nearly identical labels.

  • Between the first two rounds, on the same nine tasks (three lightly edited), overall direct success moved 3 points (30% to 33%). Underneath, two tasks gained 17 to 19 points and another lost 12.
  • In one menu, 26 of 54 participants (48%) chose "Auto send review request" instead of the correct near-twin label, "Auto Sent review requests".
  • The third tested version recorded 48% Direct across the study. Between Initial and Iteration 1, the notifications task kept the same wording, while the menu label changed to “Customer Notifications.” Direct success was 27% and 46% respectively; first clicks into the intended category were 34% and 57%.

The e-commerce case study

In a published government project, a revised structure scored 67% success compared with 31% for the original structure, using the same tasks 8.

What you hand over

Give stakeholders the decision first: keep the structure, revise particular routes or collect a specific missing piece of evidence. Show the two or three observations that justify it, including the tasks and audiences examined. The findings table and task results supply the detail; an inventory 5, revised hierarchy 9 or re-test plan belongs alongside them when it matters to the next step.

One finding, end to end

An e-commerce admin tree test revealed confusion between two near-identical menu labels.

  1. Observation

    26 of 54 participants finished at "Auto send review request". The correct item, "Auto Sent review requests", sat in the same menu.

  2. Interpretation

    Two near-identical labels obscure the distinction between destinations.

  3. Decision

    Rename one label. Owner: the product team for that menu.

  4. Next check

    Both destinations in the next tree-test round.

Findings table

Part of the structureData / observationInterpretationConfidence / evidence basisSeverity (if rated)OwnerNext step
Labels26 of 54 finished at "Auto send review request"; the correct item was "Auto Sent review requests", in the same menuThe two labels are near-twins26 of 54 chose the same wrong destination; one clear competing labelNot ratedProduct team for that menuRename one label; check both destinations in the next round

Keep data/observations and interpretations in separate columns.

Keeping an IA useful over time

  • Keep the structure useful as new pages, tasks and vocabulary emerge. Give someone ownership of labels and placement, then revisit priority routes when search logs, support contacts or task research show a meaningful change.

Teams that track top tasks over time re-measure them every 6 to 12 months; this is top-task measurement, a separate practice from tree testing 20.

Turn the next IA question into evidence

Have a hierarchy to test? See which destinations participants reach and where they go instead.

Start a tree test

Still deciding how to group the content? Explore the organizing patterns and labels participants use.

Start a card sort

Sources

  1. [1] Laubheimer, P. "Tree Testing: Fast, Iterative Evaluation of Menu Labels and Categories." Nielsen Norman Group, 2023.
  2. [2] Laubheimer, P. "Tree Testing Part 2: Interpreting the Results." Nielsen Norman Group, 2024.
  3. [3] Cardello, J. "Low Findability and Discoverability: Four Testing Methods to Identify the Causes." Nielsen Norman Group, 2014.
  4. [4] Tankala, S. and Sherwin, K. "Card Sorting: Uncover Users' Mental Models for Better Information Architecture." Nielsen Norman Group, 2024.
  5. [5] Kaley, A. "Content Inventory and Auditing 101." Nielsen Norman Group, 2020.
  6. [6] Farrell, S. "Site-Search Log Analysis." Nielsen Norman Group, 2017.
  7. [7] Spencer, D. and Warfel, T. "Card Sorting: A Definitive Guide." Boxes and Arrows, 2004.
  8. [8] O'Brien, D. "Tree Testing." Boxes and Arrows, 2009.
  9. [9] Spencer, D. A Practical Guide to Information Architecture, 2nd ed. UX Mastery, 2014.
  10. [10] Wiggins, R. and Rosenfeld, L. "Using Search Analytics to Diagnose What's Ailing Your Information Architecture." IA Summit, 2007.
  11. [11] O'Brien, D. "How many participants?" In Tree Testing for Websites.
  12. [12] Arango, J. "Mastering the Muddle: The Power of Heuristic Evaluations." 2023.
  13. [13] Nielsen, J. "Severity Ratings for Usability Problems." Nielsen Norman Group, 1994.
  14. [14] O'Brien, D. "Comparing to other IA methods." In Tree Testing for Websites.
  15. [15] O'Brien, D. "How many tasks?" In Tree Testing for Websites.
  16. [16] Sauro, J., Schiavone, W., Du, D. and Lewis, J. "Do Click Tests Predict Live-Site Clicks?" MeasuringU, 2023.
  17. [17] Canada.ca Experience Office. "How we're optimizing Canada.ca top tasks." 2017.
  18. [18] Nielsen, J. "Card Sorting: How Many Users to Test." Nielsen Norman Group, 2004.
  19. [19] 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 183, 2025. The authors work for a tree-testing vendor.
  20. [20] Wake, L. "Top task performance indicators." University of St Andrews Digital Communications, 2017 (reporting Gerry McGovern's method).

Study data: UXbeam card sorting and tree testing studies shown in the worked examples.