What it is
A findability test where participants locate items in a text-only version of your site structure, measuring whether the information architecture works independent of visual design.
When to use it
During Synthesize or Prototype, to validate a proposed IA before investing in visual design.
Why (value)
Isolates the structure from the interface, showing whether labels and hierarchy actually lead users to the right place.
How to run it
- Build the hierarchy as a clickable text tree.
- Write realistic find-it tasks.
- Have participants navigate the tree to complete tasks.
- Record success, directness, and where they go wrong.
- Revise labels and structure, then retest.
Inputs and outputs
- Inputs: A candidate IA, tasks, participants, a tree-testing tool.
- Outputs: Success rates, path data, problem labels.
Time and effort
Medium. Mostly setup; the test runs quickly and unmoderated.
Evidence and limitations
Gives quantitative direct-user findability evidence, but tests structure and labels only, not visual or interaction design. See Evidence and limitations.
Tips and pitfalls
- Phrase tasks without using the exact label words.
- Test a reasonable number of tasks to avoid fatigue.
- Pair with card sorting to generate the structure first.
Variations
Moderated or unmoderated; single-tree or comparative.
Related methods
Need help planning research or facilitating this method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- NN/g, “Tree Testing for Information Architecture.”
Explore related methods
- Card sorting — Have users group and label content so your structure matches their mental model.
- Sitemapping — Map the hierarchy and structure of a site or app's pages and sections.
- First-click testing — Measure where people click first on a task, since that first move strongly predicts success.
