Tree testing allows you to show a menu structure to users in its most basic form without worrying about the layout and design. Users are asked to complete a series of tasks looking for items using the site structure. Typically, tree testing sessions are quite short so only last about 15-20 minutes. On average you would have about 15-20 tasks per session as users tend to lose concentration if the tasks go on for too long. By using this method to evaluate your site structure you have a way to measure how easy it is for users to find items.
Tree testing is normally conducted early on in the design process using online tools like Treejack. This part of your research could be after a card sorting session to confirm that your findings from the card sorting are correct.

Original Content
"Talk data to me!" It's really fun to try to read and understand all the data from the quantitative test results. After card sorting section for the project, it was time to test our assumptions. In that way, finally, I was able to choose one of the information architecture concepts. 
Card sorting results lead me to create three different navigation bar concepts on the project. So I made three different app structure and a test which occurs 14 tasks list. Tasks were exactly the same for three different tests. The challenge of making the task list was not to give hint while asking action from users. It was important to know how users search and think about what they need to do. 
We made an online test with 110 users for three different tests and examine every tasks result. It helped us to understand even the headlines are really important to guide users. There was not such a big difference between two concepts, but for the last one, there was almost %15 improvement about the tasks.  There were the same conclusions as users always thinking the simplest way to achieve their goal, so content and names should not be so complicated.

Back to Top