Tree test is the perfect method to get the insights you need to build an intuitive information architecture. For best results, a card sort should be followed up by a tree test to evaluate the proposed menu structure. A tree test evaluates a hierarchical category structure by having users find the locations in the tree where specific tasks can be completed.
How it works?
To conduct a tree test, you don’t need to sketch any wireframes or write any content. You only need to prepare two things: the tree, or hierarchical menu, and the tasks, or instructions which explain to study participants what they should attempt to find.
When to use?
Although the information that emerges after card grouping is sufficient to create a new information architecture, we need to verify this information with a tree test. While creating the test, it is necessary to create questions for the users in line with the objectives of the project or by addressing the problem areas that arise in the card grouping study.
A Tree Test of 110 people in total was conducted and deficiencies and good points in 3 different information architectures were determined.
By testing these 3 information architectures, availability comparison with the old tree was made.
Lower Observed time: 1.88
Lower Quartile: 2.50
Upper Quartile: 8.92
Highest observed time: 32.27
Shows the rate of users marking the correct answer.
It shows the rate at which users turn to the direct answer or hovering over the answer.
Task 1: You need a new credit card and you want to do this through the application without going to the branch, how do you follow this process?
Task 2: You want to make a change in your address defined on your credit card, how would you do it?
As shown in the graph, the tree test gives us information about what information users are looking for. In this example, users expect to be able to change their credit card addresses on their credit card settings and the settings page. In information architecture, an action can be located in different areas.