The Tree Test block helps you evaluate information architecture by testing how easily participants can find specific items within your tree structure. This powerful testing method reveals whether your navigation and labelling make intuitive sense to users, helping you validate or improve your structure.
Setting up your tree test
Build your navigation hierarchy by adding nodes and child nodes that represent your content structure. This should mirror your actual or proposed information architecture.
Adding nodes to your tree structure
Click "Add node" to create a new parent node
Type your label
Hover on any existing node and click “+” to add a child underneath it
Drag nodes up or down to reorder them
Dragging a node to an indented position will make it a child of the node above
Dragging a parent node will also move its child nodes with it
Success destination setup
Define which locations in your tree represent successful task completion. Click "Manage" to open the success destinations panel, where your entire tree will appear with checkboxes next to child nodes. You can select one or multiple correct destinations from your tree structure.
Note: You can only set end-point child nodes as success destinations (nodes without children beneath them). This is to ensure the full path can be displayed in results. If you want a ‘parent node’ to be the success point we recommend applying every child node within it to be a success destination.
Why set success destinations
Automatically calculate success metrics in your results
Identify which paths led to direct success, indirect success or failures
You can define multiple success destinations if there are several equally valid locations where participants might reasonably complete the task.
Best practices
Task instructions
Use natural language that matches how real users think about their goals
Avoid using terminology that appears in your tree structure
Include enough context for participants to make informed decisions
Tree structure
Mirror your actual or proposed navigation structure as closely as possible
Keep node labels concise and clear
Ensure there's a logical path to each destination
Limit tree depth to 3-5 levels with no more than 10 items per level to avoid overwhelming participants and maintain effective navigation
Success destinations
Consider whether multiple paths should be considered successful
Set destinations that genuinely represent task completion