Live training: How to benchmark an existing site structure using Treejack

“Dear Optimal Workshop,I want to test the structure of a university website (well certain sections anyway). My gut instinct is that it's pretty 'broken'. Lots of sections feel like they're in the wrong place. I want to test my hypotheses before proposing a new structure. I'm definitely going to do some card sorting, and was planning a mixture of online and offline. My question is about when to bring in tree testing. Should I do this first to test the existing IA? Or is card sorting sufficient? I do intend to tree test my new proposed IA in order to validate it, but is it worth doing it upfront too?" — Matt

‍

Dear Matt,

Ah, the classic chicken or the egg scenario: Which should come first — tree testing or card sorting?
‍
It’s a question that many researchers often ask themselves, but I’m here to help clear the air!You should always use both methods when changing up your information architecture (IA) in order to capture the most information.

Tree testing and card sorting, when used together, can give you fantastic insight into the way your users interact with your site. First of all, I’ll run through some of the benefits of each testing method.

‍

What is card sorting and why should I use it?

‍

Card sorting is a great method to gauge the way in which your users organize the content on your site. It helps you figure out which things go together and which things don’t. There are two main types of card sorting: open and closed.

Closed card sorting involves providing participants with pre-defined categories into which they sort their cards. For example, you might be reorganizing the categories for your online clothing store for women. Your cards would have all the names of your products (e.g., “socks”, “skirts” and “singlets”) and you also provide the categories (e.g.,“outerwear”, “tops” and “bottoms”).

‍Open card sorting involves providing participants with cards and leaving them to organize the content in a way that makes sense to them. It’s the opposite to closed card sorting, in that participants dictate the categories themselves and also label them. This means you’d provide them with the cards only — no categories.

‍Card sorting, whether open or closed, is very user focused. It involves a lot of thought, input, and evaluation from each participant, helping you to form the structure of your new IA.

‍

What is tree testing and why should I use it?

‍

Tree testing is a fantastic way to determine how your users are navigating your site and how they’re finding information. Your site is organised into a tree structure, sorted into topics and subtopics, and participants are provided with some tasks that they need to perform. The results will show you how your participants performed those tasks, if they were successful or unsuccessful, and which route they took to complete the tasks. This data is extremely useful for creating a new and improved IA.

‍Tree testing is an activity that requires participants to seek information, which is quite the contrast to card sorting — an activity that requires participants to sort and organize information. Each activity requires users to behave in different ways, so each method will give its own valuable results.

‍

Should you run a card or tree test first?

‍

In this scenario, I’d recommend running a tree test first in order to find out how your existing IA currently performs. You said your gut instinct is telling you that your existing IA is pretty “broken”, but it’s good to have the data that proves this and shows you where your users get lost.

An initial tree test will give you a benchmark to work with — after all, how will you know your shiny, new IA is performing better if you don’t have any stats to compare it with? Your results from your first tree test will also show you which parts of your current IA are the biggest pain points and from there you can work on fixing them. Make sure you keep these tasks on hand — you’ll need them later!

Once your initial tree test is done, you can start your card sort, based on the results from your tree test. Here, I recommend conducting an open card sort so you can understand how your users organize the content in a way that makes sense to them. This will also show you the language your participants use to name categories, which will help you when you’re creating your new IA.

Finally, once your card sort is done you can conduct another tree test on your new, proposed IA. By using the same (or very similar) tasks from your initial tree test, you will be able to see that any changes in the results can be directly attributed to your new and improved IA.

Once your test has concluded, you can use this data to compare the performance from the tree test for your original information architecture — hopefully it is much better now!

‍

‍

We’re excited to announce our first six project templates are now available in Optimal Workshop! We understand that not everyone knows where to start with customer research, so these ready-made templates have been created with UX industry experts to give you the confidence to quickly launch studies and get the results you need to make data-driven decisions.  

‍

Templates aren’t only a great solution for people who need guidance with which study type to use and when; our detailed templates also give you the tools to develop your IA thinking, compare the performance of studies over time, and get detailed project plans to guide you through your information architecture. 

‍

‍

How do templates work?

‍

On the dashboard, you’ll see a new button called Browse Templates. From the templates menu, you can select a template that matches your use case, e.g. ‘I need to organise content into categories’. The templates are a helpful starting point, for you to adapt to suit your research goals. 

‍

Let’s take a look at some of our favourite project templates. 

‍

‍

Organize content into categories

‍

‍

This template helps you design the best categories to organize your information based on how your  users think. It's useful for designing your product, website, or knowledge base experience, as well as re-evaluating any part of it. In this template, we will first conduct an open card sort, and then use that information to design a navigation structure that will be tested on end users.

‍

‍

1. First up run a card sort with OptimalSort

‍

During this study, users will organise all information presented to them into categories they create themselves using an open card sort. This method is great for generating category ideas based on how users process this information allowing you to better design an experience in a more user-focused way. To find out more on how to set up your card sort, refer to our card sorting 101 guide.

‍

‍

2. Test your navigation structure with a Treejack

‍

Based on the groupings that were produced from the card sort, you can now generate a hierarchy for your users to test using Treejack. Users search for the information you’ve categorised and represented as a hierarchy, which is valuable because it helps to confirm whether information placed within your hierarchy is findable and understandable.  
‍

To learn more about tree testing, refer to our tree testing 101 guide.

‍

Evaluate an existing navigation experience 

‍

‍

Regularly evaluating an existing navigation experience is a good way to monitor the health and performance of your website and product. This template is useful for both redesigning your experience and for re-evaluating part of it by helping you design ideal categories to organize your information based on how your target users think and improve findability and task completion. 

‍

‍

1. Start by identifying your top tasks using Reframer

‍

Using Reframer, conduct interviews with various stakeholders in your business to evaluate and theme which tasks your organization believes are the most important within your existing environment. This is a solid first step towards building a list of top tasks for testing. Reframer allows you to easily visualize and group your observations by proximity using the affinity map.  

‍

‍

2. Survey users to understand their top tasks

‍

Next, survey users to confirm their top tasks and identify any existing issues with our survey tool Questions. This will provide insight into what users believe are their top tasks and whether anything is getting in their way to achieve them. This step helps to ensure all design work is informed by up-to-date user tasks.

‍

‍

3. Design and test your current experience in Treejack  

‍

Using the prioritised top tasks create a tree test using Treejack to test your navigation experience with your users. For example “How would you open a home loan” or “How would you upgrade your broadband plan” This will enable you to see how your users navigate your website in order to achieve the most business critical tasks in your organization. This is a valuable step that helps to identify information and design problems to solve early in the design process. 

‍

‍

More templates from our community

‍

This is just the beginning of templates in Optimal Workshop and while we continue to add value and build up our collection, we’d love your input! If there are templates that you regularly use and think the community could benefit from, let us know at hello@optimalworkshop.com.

A great information architecture (IA) is essential for a great user experience (UX). And testing your website or app’s information architecture is necessary to get it right.

‍

Card sorting and tree testing are the very best UX research methods for exactly this. But the big question is always: which one should you use, and when? Very possibly you need both. Let’s find out with this quick summary.

‍

What is card sorting and tree testing? 🧐

‍

Card sorting is used to test the information architecture of a website or app. Participants group individual labels (cards) into different categories according to  criteria that makes best sense to them. Each label represents an item that needs to be categorized. The results provide deep insights to guide decisions needed to create an intuitive navigation, comprehensive labeling and content that is organized in a user-friendly way.

‍

Tree testing is also used to test the information architecture of a website or app. When using tree testing participants are presented with a site structure and a set of tasks they need to complete. The goal for participants is to find their way through the site and complete their task. The test shows whether the structure of your website corresponds to what users expect and how easily (or not) they can navigate and complete their tasks.

‍

What are the differences? 🂱 👉🌴

‍

Card sorting is a UX research method which helps to gather insights about your content categorization. It focuses on creating an information architecture that responds intuitively to the users’ expectations. Things like which items go best together, the best options for labeling, what categories users expect to find on each menu.

‍

Doing a simple card sort can give you all those pieces of information and so much more. You start understanding your user’s thoughts and expectations. Gathering enough insights and information to enable you to develop several information architecture options.

‍

Tree testing is a UX research method that is almost a card sort in reverse. Tree testing is used to evaluate an information architecture structure and simply allows you to see what works and what doesn’t. 

‍

Using tree testing will provide insights around whether your information architecture is intuitive to navigate, the labels easy to follow and ultimately if your items are categorized in a place that makes sense. Conversely it will also show where your users get lost and how.

‍

What method should you use? 🤷

‍

You’ve got this far and fine-tuning your information architecture should be a priority. An intuitive IA is an integral component of a user-friendly product. Creating a product that is usable and an experience users will come back for.

‍

If you are still wondering which method you should use - tree testing or card sorting. The answer is pretty simple - use both.

‍

Just like many great things, these methods work best together. They complement each other, allowing you to get much deeper insights and a rounded view of how your IA performs and where to make improvements than when used separately. We cover more reasons why card sorting loves tree testing in our article which dives deeper into why to use both.

‍

Ok, I'm using both, but which comes first? 🐓🥚

‍

Wanting full, rounded insights into your information architecture is great. And we know that tree testing and card sorting work well together. But is there an order you should do the testing in? It really depends on the particular context of your research - what you’re trying to achieve and your situation. 

‍

Tree testing is a great tool to use when you have a product that is already up and running. By running a tree test first you can quickly establish where there may be issues, or snags. Places where users get caught and need help. From there you can try and solve potential issues by moving on to a card sort. 

‍

Card sorting is a super useful method that can be instigated at any stage of the design process, from planning to development and beyond.  As long as there is an IA structure that can be tested again. Testing against an already existing website navigation can be informative. Or testing a reorganization of items (new or existing) can ensure the organization can align with what users expect.

‍

However, when you decide to implement both of the methods in your research, where possible, tree testing should come before card sorting. If you want a little more on the issue have a read of our article here.

‍

Check out our OptimalSort and Treejack tools - we can help you with your research and the best way forward. Wherever you might be in the process.