Method guideUX Research

Tree Testing

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityMedium

Time1-2 Tage

ParticipantsBased on research question

FormatAsync

MaturityCanonical

Prepare a tree test

Prerequisite

What needs to be finished first

Complete firstTestable hierarchy

A bounded tree with stable nodes and labels is available.

Without a complete hierarchy, findability cannot be evaluated meaningfully.

Complete firstClear search tasks

The task and destination represent a plausible use situation.

If the scenario reveals the target label, the test overstates findability.

Complete firstAnalysis frame

Tasks, relevant groups, success criteria, and metrics are set.

A rate without denominator or path context can lead to overclaiming.

Preparation

What needs to be ready before start

Materials

Versioned navigation tree, search tasks with expected destinations, participant profile, test tool, and capture grid for first clicks and paths.

People / roles

Research lead prepares the tree and tasks. Participants search individually; moderation stays neutral. For remote studies, document sample quality and source.

Pre-read

Gather critical content, current hierarchy, audiences, known findability issues, and the pending structural decision.

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.

Core question

The one question this method answers

Can relevant users find the required content in the proposed hierarchy?

Flow

Phases with goal, actions, output and pitfall

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.

Tree-test task paths

Fictional teaching example

Keep expected destination, selected path, and interpretation traceable by task.

Tree-test task paths
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.

NN/G

1
Tree
Bound the hierarchy
Goal
Set the tree structure and content area to test.
Inputs for this step
- Name the content people must find and the hierarchy, labels, and levels to evaluate.
Actions
- Remove design, page copy, and irrelevant content; keep the tested version stable and traceable.
Output
Versioned navigation tree with traceable destination nodes.
Versioned navigation tree with traceable destination nodes.
Quality check
The tree is complete enough for tasks and is not mixed with visual cues.
Pitfall
An incomplete or already designed navigation is presented. Complete the destinations and separate the tree test from the UI.
Timing: 30–60 minutes for tree scope and version
2
Tasks
Write tasks
Goal
Write realistic search tasks with a clearly defined destination.
Inputs for this step
- Versioned navigation tree with traceable destination nodes.
Actions
- State the use context without naming the expected category or path; pilot the wording and correct destination.
Output
Versioned task set with expected destinations and rationale.
Versioned task set with expected destinations and rationale.
Quality check
Each task has a justified target; multiple plausible destinations are noted in advance.
Pitfall
A task repeats the navigation label or asks for several things. Write from the user situation and need; split multi-destination tasks.
Timing: 30–60 minutes to write and pilot tasks
3
Paths
Collect paths
Goal
Let participants search the tree and capture first choice, path, and final destination.
Inputs for this step
- Versioned task set with expected destinations and rationale.
Actions
- Show only the tree and task; capture first clicks, final choice, detours, backtracking, and optional confidence or rationale.
Output
Task-level paths and final selections by participant.
Task-level paths and final selections by participant.
Quality check
Tasks, tree version, and participant code stay linked.
Pitfall
Only the final click is recorded. Capture the click path and first click so wrong turns can be explained.
Timing: Unmoderated participation varies; plan moderated sessions separately
4
Interpret
Interpret findability
Goal
Connect destination success to first click, path directness, and task wording.
Inputs for this step
- Task-level paths and final selections by participant.
Actions
- Compare wrong and correct destinations, first divergences, and alternate paths; report by task and relevant user groups.
Output
Findings about nodes, labels, and tasks with next structural tests.
Findings about nodes, labels, and tasks with next structural tests.
Quality check
Success, directness, and uncertainty use a suitable sample and stated denominator.
Pitfall
A success rate is interpreted without sample, task basis, or path context. Report metrics with denominator, task wording, and tree version; separate qualitative clues.
Timing: Analysis depends on tasks, participants, and iterations

Artifact

What comes out at the end

Sketch: what the artifact looks like

Tree Testing · Informationsarchitektur prüfenAufgaben gegen eine nackte Navigationshierarchie testen und Suchpfade, Treffer und Fehlwege sichtbar machen

Form

Study plan with tree version, tasks and expected destinations, path data, task-level analysis, and justified hierarchy changes.

Versioning / ownership

Date the tree, tasks, target mapping, and analysis version. Preserve raw paths and report results by task and sample.

Tool alternatives

Interactive navigation tree without page layout
Task sheet with independently justified destinations
Analysis of first choice, final choice, path, and optional confidence

tree-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.

NN/G

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

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

tree-testing-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: neighborhood tool-lending navigation

All tasks, paths, and metrics are fictional. No tree test was conducted.

Test question: Can people find the tool-reservation path and lending conditions?

Fictional tree: Tools > Availability > Cordless drills; Lending > Reserve; Help > Rules and dates.

Task T1: “You want to repair a shelf on Saturday and need a suitable tool. Find out how to make sure one will be available.” Expected destination: Lending > Reserve.

Path P1: Tools > Availability > Cordless drills. Final choice: wrong destination.

Path P2: Lending > Reserve. Final choice: expected destination; direct path.

Fictional finding: Two invented paths cannot support a reliable success rate. They suggest a possible confusion between availability and the reservation process.

Next step: Check task comprehension and the “Availability” versus “Reserve” nodes in a planned study. Compare a revised tree with a new sample.

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

Bound the hierarchyAn incomplete or already designed navigation is presented.View in phase
Write tasksA task repeats the navigation label or asks for several things.View in phase
Collect pathsOnly the final click is recorded.View in phase
Interpret findabilityA success rate is interpreted without sample, task basis, or path context.View in phase

Stop criteria

When to pause, resolve prerequisites, or choose another approach

The tree does not include target content: complete the hierarchy first.

A task has several plausible targets: clarify task and success criterion.

The question concerns grouping, not findability: consider card sorting.

Where to go next?

Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.

UX Research

Usability Testing

Tests the hierarchy confirmed as findable within the full interface.

UX Research

First-click Testing

Deepens a conspicuous node with a focused first-click test.

View in playbookValidate Information ArchitectureMove from unclear navigation to tested structure, labels, and findability signals.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profile More methods

Tree-test task paths

1. Search task

2. Expected destination

3. First click and path

4. Finding or follow-up

Bound the hierarchy

Write tasks

Collect paths

Interpret findability

tree-testing-working-template.md

Tree Testing: Worksheet

Question

Desired outcome

Scope

Preparation for this scope

Method setup

Prepare for the work steps

Tree: Bound the hierarchy

Tasks: Write tasks

Paths: Collect paths

Interpret: Interpret findability

Tree-test task paths

Tree: Bound the hierarchy

Tasks: Write tasks

Paths: Collect paths

Interpret: Interpret findability

Open questions and next steps

tree-testing-beispiel.md

Fictional teaching example: neighborhood tool-lending navigation

Bound the hierarchy

Write tasks

Collect paths

Interpret findability

Where to go next?

Finished the method guide?