IA
Tree Testing
A practical information architecture method for validating hierarchy and labels without visual design getting in the way.
How to use tree testing to validate navigation, improve findability, and check whether users can move through your structure quickly and accurately.
What it is
Tree testing is a UX serviceUser ResearchUnderstand user behaviour, validate ideas, and make clearer product decisions with evidence you can act on.Open service method used to evaluate how easily users can find information within a structured glossaryHierarchyHierarchy is the organisation of elements to show importance and guide user attention.Open glossary term.
Participants are given a simplified glossaryVersionA version is a specific iteration of software or a product at a point in time.Open glossary term of a site’s structure, often just text-based categories, and asked to complete tasks by navigating through it.
There is no visual design, no glossaryLayoutLayout is the arrangement of elements on a page or screen, determining how content is organised and presented. It influences readability, usability, and overall experience.Open glossary term, and no glossaryInteractionInteraction refers to any action a user takes within a product and how the system responds. It includes clicks, taps, gestures, and inputs that drive the user experience.Open glossary term beyond selecting categories. This isolates the serviceInformation ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service so you can test structure and labelling on their own.
Tree testing is often referred to as reverse guideCard SortingOpen, closed and hybrid card sorting compared: how to learn the way users group and label content, and when each variant is the right one.Open guide because it tests how users move through a predefined structure.
The goal is to identify whether users can find what they need quickly and accurately.
Tree testing is most useful when you need to know whether the structure itself works before design and interface detail enter the picture.
When to use it
Use this method when validating glossaryNavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.Open glossary term and structure.
It is most useful when:
It is less useful when:
Tree testing is often used after card sorting and before usability testing.
Key takeaway
Use tree testing when the main question is whether users can successfully navigate the hierarchy you have defined.
How to run it
Set up properly
Be clear on three things before you start: the structure you are testing, the tasks people will attempt, and what counts as the correct path for each. Without the third, you cannot score the result.
Strip out visual design, page content and glossarySearchSearch is the functionality that allows users to find content or information by entering queries. It relies on indexing, metadata, and relevance algorithms to return useful results.Open glossary term. What is left should be labels and glossaryHierarchyHierarchy is the organisation of elements to show importance and guide user attention.Open glossary term, nothing else.
Run the method
Tree testing is deliberately narrow. It answers one question (can people find things in this structure) and it answers it before anything is designed.
- Present the structure as text only. No glossaryLayoutLayout is the arrangement of elements on a page or screen, determining how content is organised and presented. It influences readability, usability, and overall experience.Open glossary term, no content, no glossarySearchSearch is the functionality that allows users to find content or information by entering queries. It relies on indexing, metadata, and relevance algorithms to return useful results.Open glossary term, or you are testing the page rather than the glossaryHierarchyHierarchy is the organisation of elements to show importance and guide user attention.Open glossary term.
- Give realistic tasks. Phrase each as the user's problem ("you have been charged twice"), not "find the billing disputes page", which only tests whether they can match your wording.
- Ask them to navigate to where they would expect the answer to sit. Let them commit to a branch and be wrong; that is the finding, not a failure of the glossarySessionA session is a single period of user interaction with a product, from entry to exit within a defined timeframe.Open glossary term.
- Record the path, not just the outcome. Whether someone arrived matters far less than whether they went straight there.
- Capture hesitation and changes of direction. The moment someone pauses or reverses is the moment a label stopped carrying its meaning.
Focus on glossaryNavigationNavigation is the system of menus, links, and cues that lets people move through a product and reach what they need. It exposes the underlying structure, and is how most users experience that structure.Open glossary term glossaryBehaviourBehaviour refers to how users interact with a system, including actions, patterns, and responses.Open glossary term, not aesthetics. Nobody is judging the design, because there is no design in front of them.
Capture and make sense of it
The value comes from identifying breakdowns in structure. Look across results to identify:
- glossarySuccess RateSuccess rate is the proportion of users who complete a given task successfully. It depends on defining what counts as success before testing begins, otherwise the threshold moves to fit the result.Open glossary term for each task, read individually rather than averaged
- Common incorrect paths, especially ones several people share
- Labels and categories that were understood differently from how you meant them
- Points where people got lost, and what they were looking for when it happened
Use this to refine your serviceInformation ArchitectureImprove navigation, content structure, and findability so users can understand where things are and how to move through them.Open service, then test the revised tree the same way. One round tells you where it fails; two tell you whether the fix worked.
What to look for
Focus on:
Where it goes wrong
Most issues come from:
If users cannot find things here, they will not find them in the real product.
What you get from it
Done properly, this method gives you:
Key takeaway
It helps you make sure your structure works before design gets involved.
Get in touch
If this sounds like something you need, we can help you test and refine your structure so users can navigate with confidence.
No guesswork. No assumptions. Just structure that works.
FAQ
Common questions
A few practical answers to the questions that usually come up around this method.
What is tree testing in UX?
It is a method used to test how easily users can find information within a structured hierarchy.
Is tree testing the same as reverse card sorting?
They are the same method, and tree testing is now the more common name. It is also the clearer one, since what participants navigate is a stripped-back tree of labels with no visual design, no search and no page content to help them.
When should you use tree testing?
Use it when validating navigation and information architecture.
What does tree testing measure?
It measures findability, navigation paths, and label clarity.
Does tree testing improve UX?
Yes. It ensures users can find what they need quickly.
Quick take
If you want to know whether your structure actually works, use tree testing.
Related Services
