Feature Findability

Why should you use this template?

Feature findability is intrinsically linked to the overall usability of any digital experience. But why should you focus on improving findability specifically?

Well, findability quickly goes from a usability concern to a profitability concern. If your users can’t find the information they need to make a purchasing decision, or perhaps they are unable to complete a critical task for their job, then your product will be dropped before you know it.

This test is designed to measure findability in two main ways: Information Architecture (IA) and User Interface (UI) comprehension.

 

Testing Outcomes

• Validate and refine existing IA structure
• Identify UI that goes unnoticed, avoided, or underutilized
• Achieve an understanding of how users seek out information

 

Organization Benefits

• Improved findability is highly correlated with improved overall usability
• Understanding how users search will inform future design decisions

 

Test Questions

1. Click where you would go in the menu to see an overview of your campaigns’ stats and performance.
   Tree Test
   The tree test is specialized to evaluate comprehension of your IA, a building block of findability. All you need to do is set up your IA and identify the key features that you want to evaluate.
2. Sort the cards on the left into the categories on the right that make most sense.
   Card Sort
   Another great way to evaluate IA while also further engaging your customers is with a closed card sort. Similar to tree tests, you’ll need to create a card for each item and category of your IA, only this time, it will be up to your users to organize the information.
3. Click on where you would look for the analytics dashboard.
   Click Test
   Next, use click questions to check for UI comprehension, which is the other aspect of findability, alongside IA comprehension.

 

Additional Questions

• How do users find information?
• Which navigation components are utilized?
• Which navigation components go unnoticed?
• Which navigation components are avoided?
• How do users find information?
• Which navigation components are utilized?
• Which navigation components go unnoticed?
• Which navigation components are avoided?
• Did they find the intended item? (Y/N)