Tree testing is incredibly useful as a follow-up to card sorting because it: Evaluates a hierarchy according to how it performs in a real-world scenario, using tasks similar to a usability test; and.7 May 2017
When should you do tree testing?
When to use tree testing: test big, test small, test often You can get valuable insights at all stages in the design process, whether you're starting from scratch or making a few tweaks to a website you already have in place. You can test large website structures (with 10+ levels and 1000s of labels, for example).
How many tree test users are there?
We recommend getting at least 30 participants to complete your tree tests, and ideally around 50, so that you can see trends clearly and account for variations and outliers. In Treejack, the more participants you get, the more confident you can be in the accuracy of your quantitative data.
How do you write tree testing tasks?
- how many people actually found Form X.
- how long it took them to find it.
- the path they took, and whether or not they had to click back up the tree.
How does a tree test work?
In tree testing, a text-only version of the site's hierarchy is laid out in front of test participants, who are asked to highlight a category or page within that structure where they would expect to find a particular item or piece of content.
What are the steps in conducting the test?
- Preparation.
- Conducting the assessment.
- Reporting the assessment outputs.
- Analyzing the assessment report.
- Action planning.
- Implementing improvement.
- Follow-up.
What is tree testing used for?
Tree testing is used to assess the findability, labeling, and information architecture of a website or app. With tree testing, you can identify navigation issues early on and make improvements to ensure your users can quickly find the information they need.
What is tree Jack testing?
Tree testing helps you evaluate the findability of topics on your website. Whether you're starting fresh or improving your existing website, Treejack is the perfect tool to get the insights you need to build an intuitive information architecture.
How do you analyze tree testing?
- The percentage of testers who successfully completed each task ("success rate")
- The percentage of testers who successfully completed each task without making wrong guesses first ("directness")
- The average time needed for each task ("time)