Purpose
When a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination.
UX Research Research method
Tree Testing
Checks whether people can find content in a navigation hierarchy.
Tree testing evaluates search tasks in a labeled, clickable hierarchy without a visual interface. Destination, first click, and path show information-architecture findability; finished-page appearance and interaction are outside the test scope.
Can relevant users find the required content in the proposed hierarchy?
- Participants
- Based on research question
- Time
- Study dependent
The phase bar connects hierarchy, tasks, paths, and revision.
Tree
Bound the hierarchy
Set the tree structure and content area to test.
Tasks
Write tasks
Write realistic search tasks with a clearly defined destination.
Paths
Collect paths
Let participants search the tree and capture first choice, path, and final destination.
Interpret
Interpret findability
Connect destination success to first click, path directness, and task wording.
Revise problem nodes and labels from task paths; test a changed structure with comparable participants who have not been primed by the prior version when possible.
A good fit when
Use tree testing when a hierarchy and its labels exist and you want to evaluate paths before UI design or independently of it. Card sorting is more suitable for discovering new groupings.
Ideal for
- IA validation
- Navigation comparison
- Findability benchmarking
Not good for
- Visual hierarchy feedback
- Open discovery
Outputs
Findability paths
First clicks, selected destinations, and detours by task.
Hierarchy findings
Traceable label or node issues linked to a test task.
Tree-test task paths
Fictional teaching example
Keep expected destination, selected path, and interpretation traceable by task.
| Task path | Search task | Expected destination | First click and path | Finding or follow-up |
|---|---|---|---|---|
| Wrong pathA path ending at the wrong destination. | Fictional T1: Find a suitable tool available for Saturday. | Lending > Reserve | P1: Tools > Availability > Cordless drills | Possible confusion between stock and reservation; check against more paths. |
| Direct pathA path with the expected destination and no detour. | Fictional T1: Find a suitable tool available for Saturday. | Lending > Reserve | P2: Lending > Reserve | Directness is a clue, not proof that every label is clear. |
1. Search task
- Wrong path
- Fictional T1: Find a suitable tool available for Saturday.
- Direct path
- Fictional T1: Find a suitable tool available for Saturday.
2. Expected destination
- Wrong path
- Lending > Reserve
- Direct path
- Lending > Reserve
3. First click and path
- Wrong path
- P1: Tools > Availability > Cordless drills
- Direct path
- P2: Lending > Reserve
4. Finding or follow-up
- Wrong path
- Possible confusion between stock and reservation; check against more paths.
- Direct path
- Directness is a clue, not proof that every label is clear.
Keep path data linked to task and tree version.
First step
Name the content people must find and the hierarchy, labels, and levels to evaluate.
Deep dive
How it works
Participants solve search tasks using only the structure, revealing where they branch off, get stuck, or jump back. The paths show which terms hold up and which structural edges weaken orientation.
In detail
Tree testing helps because it checks findability without visual distraction, making the pure structural performance of a navigation visible. The method becomes especially useful when search tasks reflect real goals and paths, backtracks, and wrong turns are read closely. Patterns matter more than single errors, so labels and levels get improved exactly where orientation actually breaks.
Facilitation
Formulate tasks from the perspective of real usage needs and keep the tree structure current enough that results stay meaningful. It matters most on paths that look plausible but regularly lead nowhere; naming or grouping is usually unclear there. In the end, a few prioritized structural problems are enough, so decide what changes before the next test.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Sources
Tree Testing: Evaluate Menu Labels and Categories - NN/Gnngroup.comA task-based evaluation of a proposed hierarchy, conducted without visual design or page content.Tree Testing Part 2: Interpreting the Results - NN/Gnngroup.comInterpret destination, first click, path, and directness together; task success alone can hide ambiguous labels.
Artifact templates
Tree Testing: WorksheetPlan the tree version, search tasks, participant study, and analyzable path data.markdown
Tree Testing: WorksheetPlan the tree version, search tasks, participant study, and analyzable path data.
markdowntree-testing-working-template.md
Plan the tree version, search tasks, participant study, and analyzable path data.
Tree Testing: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Evaluate one navigation hierarchy Time: Multi-session study; duration depends on recruitment, format, tasks, and analysis.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Versioned navigation tree, search tasks with expected destinations, participant profile, test tool, and capture grid for first clicks and paths.
- Roles: Research lead prepares the tree and tasks. Participants search individually; moderation stays neutral. For remote studies, document sample quality and source.
- Advance information: Gather critical content, current hierarchy, audiences, known findability issues, and the pending structural decision.
- Overall time needed: Unmoderated studies may run over several days depending on recruitment; individual tasks often take only minutes. Plan setup, participant time, and analysis separately.
- Setup: Version tree labels and destinations, pilot tasks, and confirm the test surface shows only hierarchy navigation.
Prepare for the work steps
Tree: Bound the hierarchy
- Name the content people must find and the hierarchy, labels, and levels to evaluate.
Tasks: Write tasks
- Versioned navigation tree with traceable destination nodes.
Paths: Collect paths
- Versioned task set with expected destinations and rationale.
Interpret: Interpret findability
- Task-level paths and final selections by participant.
Tree-test task paths
| Task path | Search task | Expected destination | First click and path | Finding or follow-up |
|---|---|---|---|---|
| Wrong path | ||||
| Direct path |
- Wrong path: A path ending at the wrong destination.
- Direct path: A path with the expected destination and no detour.
Blank template: capture your task, target, path, and finding.
Tree: Bound the hierarchy
Expected artifact: Versioned navigation tree with traceable destination nodes.
Versioned navigation tree with traceable destination nodes.
Entry:
...
- The tree is complete enough for tasks and is not mixed with visual cues.
Tasks: Write tasks
Expected artifact: Versioned task set with expected destinations and rationale.
Versioned task set with expected destinations and rationale.
Entry:
...
- Each task has a justified target; multiple plausible destinations are noted in advance.
Paths: Collect paths
Expected artifact: Task-level paths and final selections by participant.
Task-level paths and final selections by participant.
Entry:
...
- Tasks, tree version, and participant code stay linked.
Interpret: Interpret findability
Expected artifact: Findings about nodes, labels, and tasks with next structural tests.
Findings about nodes, labels, and tasks with next structural tests.
Entry:
...
- Success, directness, and uncertainty use a suitable sample and stated denominator.
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/tree-testing/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.
UX Research
Card Sorting
Instead of Tree Testing, when you want to use Card Sorting to group terms openly and find fitting categories from the users' perspective.
UX Research
Surveys
Collects answers in a scalable format and condenses them into results, charts, and segment insights.
UX Research
Contextual Inquiry
Observes real work in context and pairs it with follow-up questions to capture workflow insights precisely.
UX Research
Customer Journey Mapping
Bundles phases, emotions, and pain points along a journey to prioritize opportunities and critical moments.
UX Research
Diary Study
Captures experiences over time in diary entries and reveals longitudinal patterns that a single session would miss.
UX Research
HEART Framework
Moves observations, needs, and patterns toward a concrete result through "define a goal for each HEART dimension", "identify signals for each goal", and "agree on a review cadence".
Constraints and origin
MediumAsync1-2 Tage
Profile
- Method form
- Research method
- Participants
- Based on research question
- Time
- 1-2 Tage
- Maturity
- Canonical
- Origin
- UX Research Community
Next up: Usability Testing