Protocol

Test the navigation before polishing the page

A beautiful menu can still send people to the wrong shelf.

About 1 min read

Before you use it

Use when
  • A growing content library has plausible categories but uncertain findability.

Keep this limit in mind

  • Tree testing deliberately removes visual context. A good result still needs validation in the built interface.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Represent the navigation as a simple text hierarchy. Give participants realistic information needs and let them choose a destination. Record routes, backtracking and final choices before changing the labels or structure.

Steps

  1. Choose important retrieval tasks, including items that could plausibly belong in two places.
  2. Keep task wording independent of the category labels.
  3. Review mistaken routes, revise one suspected grouping or label, and test fresh tasks or participants.

An example

For a corpus library, ask where to find help checking an AI-generated answer, not where to find AI assurance.

Check your result

Can people reach a useful destination without relying on images or moderator hints?

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingTest the navigation before polishing the page

Evidence and sources
Supports

Tree testing evaluates whether people can locate destinations in a hierarchy without the visual interface.

Visual cues and interaction behavior remain outside this test.

Tree Testing: Fast, Iterative Evaluation of Menu Labels and Categories · Text-only tree and task procedure.

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details