We’re excited to announce the latest updates to our platform to help teams test, validate and gain insights early in the design process. Looking ahead to the rest of 2024, stay tuned as we expand Optimal’s research capabilities with new tools and features, including Prototype Testing, Qualitative Insights, and upgraded Surveys along with enhanced admin management and user roles!

‍

‍

What’s new at Optimal? 🤩

‍

‍

Managed Recruitment 🙋🙋🏾

‍
We’re thrilled to share the launch of our new Managed Recruitment offering with high quality and expanded profiling capabilities for hard-to-reach audiences. Managed Recruitment leverages our in-house recruitment team and a new powerful, award-winning panel — PureSpectrum — to give you access to millions of participants across 100+ countries. Optimal handles recruitment logistics from start to finish, guaranteeing quality responses and replacing low-quality participants at no extra cost.

‍

Early access is now available. To get started, submit your criteria via the request form. Starting in early August, you’ll be able to access Managed Recruitment via the Optimal Recruit tab. Recruitment is available for all Optimal tools except for Qualitative Insights (Reframer).

‍

‍

What’s coming next? 🔮🧙

‍

‍

Test your designs early and often with our latest tool:  Prototype Testing ⚙️
‍

The newest edition to the Optimal toolkit is just around the corner.  Prototype testing will allow you to quickly  test designs with users throughout the design process, to help inform decisions so you can build on with confidence.

You’ll have the option to easily import low or high-fidelity prototypes directly from Figma or build your own prototypes from scratch  by uploading images or screenshots and creating clickable areas. Prototype testing allows you to Identify usability issues and areas for improvement throughout the design process to iterate and improve your designs quickly with your users.

‍

‍

Video Recording 🎬📽️🎞️
‍

After we launch Prototype testing, we’ll be adding Video Recording to allow you to record a participant completing a prototype test. You can capture nonverbal cues like eye rolls and frustration, screens and voices to better understand user experiences, and gain deeper insights for Prototype Testing. Video recording is browser-based, with no plug in required eliminating setup complexities. Consent to record is captured upfront in the testing process and can be tailored to meet your organization’s policies.

‍

‍

Qualitative Insights & AI 🤖✨‍

‍

You’ll be able to capture meaningful insights faster and more efficiently with the new Insights feature under our Qualitative Insights (Reframer) tool. Create Insights — takeaways or key findings from a study — and keep them organized under the new Insights tab. Create a new Insight from observations or use AI to generate Insights. Each Insight will contain a title, description, and associated observations.

‍

Note that you and your organization will always maintain complete control over any AI engagement. All AI-generated results are editable. Leverage AI as needed for your studies or decide to turn off access completely for your organization.

‍

Surveys Upgrade 📋
‍

We’ll be transforming surveys with enhanced usability, advanced survey logic, and AI integration, empowering you to create, launch, and analyze surveys with ease. Our focus on improving usability will make creating, editing, and launching surveys easier than ever, including new question types, question cloning, question grouping, and AI assistance to streamline survey creation.

‍

‍

Help us build a better Optimal Workshop 🧰

‍

We’re looking for customers to join our research and beta panel to help influence product development. From time to time, you’ll be invited to join us for interviews or surveys, and you’ll be rewarded for your time with a thank-you gift.  

If you’d like to join the team, email product@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.

Are your visitors really getting the most out of your website? Tree testing (or sometimes referred to as reverse card sorting) takes away the guesswork by telling you how easily, or not, people can find information on your website. Discover why Treejack is the tool of choice for website architects.

‍

What’s tree testing and why does it matter? 🌲 👀

‍

Whether you’re building a website from scratch or improving an existing website, tree testing helps you design your website architecture with confidence. How? Tools like Treejack use analysis to help assess how findable your content is for people visiting your website. 

‍

It helps answer burning questions  like:

• Do my labels make sense?
• Is my content grouped logically?
• Can people find what they want easily and quickly?  If not, why not?

‍

Treejack provides invaluable intel for any Information Architect. Why? Knowing where and why people get lost trying to find your content, gives you a much better chance of fixing the actual problem. And the more easily people can find what they’re looking for, the better their experience which is ultimately better for everyone.

‍

How’s tree testing work? 🌲🌳🌿

‍

Tree testing can be broken down into two main parts: 

‍

• The Tree - Your tree is essentially your site map – a text-only version of your website structure.
• The Task - Your task is the activity you ask participants to complete by clicking through your tree and choosing the information they think is right. Tools like Treejack analyse the data generated from doing the task to build a picture of how people actually navigated your content in order to try and achieve your task.  It tells you if they got it right or wrong, the path they took and the time it took them.

‍

Whether you’re new to tree testing or already a convert, effective tree testing using Treejack has some key steps.

‍

Step 1.  The ‘ Why’:  Purpose and goals of tree testing

‍

Ask yourself what part of your information architecture needs improvement – is it your whole website or just parts of it? Also think about your audience, they’re the ones you’re trying to improve the website for so the more you know about their needs the better. 

‍

Tip:  Make the most of what tree testing offers to improve your website by building it into your overall design project plan

‍

Step 2.  The ‘How’:   Build your tree

‍

You can build your tree using two main approaches: 

‍

• Create your tree in spreadsheet and import it into Treejack or
• Build your tree in Treejack itself, using the labels and structure of your website.

‍

Tip:  Your category labels are known as ‘parent nodes’. Your information labels are known as ‘child nodes’.

‍

Step 3. The ‘What’: Write your tasks

‍

The quality of your tasks will be reflected in the usefulness of your data so it’s worth making sure you create tasks that really test what you want to improve.

‍

Tip:  Use plain language that feels natural and try to write your tasks in a way that reflects the way people who visit your website might actually think when they are trying to find information on your site.

‍

Step 4.  The ‘Who’:  Recruit participants

‍

The quality of your data will largely depend on the quality of your participants. You want people who are as close to your target audience as possible and with the right attitude - willing and committed to being involved.

‍

Tip:  Consider offering some kind of incentive to participants – it shows you value their involvement.

‍

Step 5.  The ‘insights’: Interpret your results

‍

Now for the fun part – making sense of the results. Treejack presents the data from your tree testing as a series of tables and visualizations. You can download them in a spreadsheet in their raw format or customized to your needs.

‍

Tip:  Use the results to gain quick, practical insights you can act on right away or as a starter to dive deeper into the data.

‍

When should I use tree testing? ⌛

‍

Tree testing is useful whenever you want to find out if your website content is labelled and organised in a way that’s easy to understand.  What’s more it can be applied for any website, big (10+ levels with 10000s of labels) or small (3 levels and 22 labels) and any size in between.  Our advice for using Treejack is simply this: test big, test small, test often.