Filtering: Scope & Logic

Question 1

How can Filtering Logic & Scope enhance the ROI of existing investments in product tagging and data collection?

Answer 1

By streamlining and optimizing the filtering process, Filtering Logic & Scope can significantly improve the returns on investments made in product tagging and data collection efforts.

Question 2

What are some key issues surrounding filtering?

Answer 2

Many filtering problems stem from the challenge of aligning user expectations with how filtering features are implemented on websites.

Question 3

Why is the performance of filtering logic often deemed more crucial than the number of available filters to users?

Answer 3

The efficacy of filtering logic largely overshadows the quantity of available filters for users, as sub-par performance can render the filtering process ineffective regardless of the number of options provided.

Question 4

What is the main challenge users face when they can’t select multiple filtering options within a single filter type?

Answer 4

Users encounter inconvenience as they must repeat their filtering process for each desired value, disrupting their workflow.

Question 5

What was a common behavior observed among participants when attempting to use filters?

Answer 5

Many participants attempted to select more than one filter option within a single filter type.

Question 6

What happened when participants were unable to select multiple filter options within a single filter type?

Answer 6

Their ability to gain a complete overview of products matching their specific needs was compromised. As a result, some participants were forced to abandon their search for a suitable product altogether.

Question 7

What is the end result when filtering options are implemented as mutually exclusive?

Answer 7

Users have to complete a much more complicated filtering process to see products of interest

Question 8

What is the primary problem associated with filter types and options containing industry jargon?

Answer 8

The use of industry-specific terminology in filter types and options can pose challenges for users, potentially causing them to overlook relevant items.

Question 9

How can the issue of industry-specific filters be addressed?

Answer 9

To mitigate this issue, it’s advisable to either avoid using industry jargon in filters or provide explanations, such as tooltips, to clarify their meaning. Additionally, for visual filters, offering visual examples can enhance user understanding and selection accuracy.

Question 10

What’s the primary concern regarding ambiguous or unfamiliar filtering terms?

Answer 10

1. The main issue is that if users don’t grasp these terms, they might miss out on relevant filters that could refine their search effectively.
2. Failing to understand filters correctly could also mean that users could apply filters that they thought meant something else, resulting in product lists that show too many unsuitable items or too few suitable ones.

Question 11

What are the three approaches that proved to be effective in reducing filter ambiguity?

Answer 11

1. Avoid industry jargon
2. Offer explanations for industry-specific or ambiguous filters
3. Provide visual examples for visual filters

Question 12

What’s the recommended approach to handling industry jargon in filter types and options?

Answer 12

The best solution is to steer clear of industry-specific jargon whenever possible. Instead, opt for terms that align closely with what users are accustomed to and likely to search for. This ensures that the majority of users will comprehend all filtering options, streamlining the product selection process without unnecessary confusion.

Question 13

What’s the main problem when users can’t readily identify and remove applied filters?

Answer 13

The core issue arises when users struggle to identify applied filters and can’t swiftly deselect them. This inefficiency prolongs the process of narrowing down the product list to find suitable options.

Question 14

when users can’t readily identify and remove applied filters?How can this issue be addressed effectively?

Answer 14

To tackle this challenge, it’s recommended to present an “Applied Filters Overview” either above the product list or within the filtering sidebar. For products with detailed specifications, both the filter type and option should be displayed. On the other hand, for visually oriented products, showcasing only the filter option suffices. This approach enhances user efficiency by facilitating easy identification and removal of applied filters.

To help users in the process of applying and removing filters, display an “Applied Filters Overview” above the product list. Doing so will allow users to confirm what filters they have already applied as well as giving them an overview of what’s defining the scope of the list.

Question 15

What are the two ux issues when users don’t an an applied filters overview?

Answer 15

1. It’s unclear which filters have been applied
2. Removing filters can be cumbersome

Question 16

What is the most appropriate way to display applied filters on a desktop site?

Answer 16

Displaying applied filters above the product list and in their original position

Question 17

What’s a common challenge users face regarding product technical details?

Answer 17

Users frequently encounter difficulty due to a lack of knowledge or uncertainty regarding the technical specifications of their products.

Question 18

How can this challenge be addressed effectively?

Answer 18

To make compatibility filters more accessible to novice users, consider transforming spec-based filters into terms that are easier to understand and recognize. Typically, this involves using the name of the product they already own, streamlining the filtering process and improving user comprehension.

Question 19

What’s a common difficulty users face when dealing with technical compatibility specifications for products?

Answer 19

Users often struggle with understanding, recalling, or finding technical compatibility specifications for products they own or plan to purchase, such as camera lens mounts, laptop charging voltages, or printer ink cartridge numbers.

Question 20

What problem arises due to users’ unfamiliarity with technical specifications?

Answer 20

The lack of familiarity with technical specifications frequently results in challenges when navigating compatibility filters on websites.

Question 21

How can usability and abandonment rates be improved in compatibility filters?

Answer 21

By translating compatibility filters into terms that users are more familiar with, such as product names or models, usability can be enhanced and abandonment rates reduced. Prioritizing user familiarity and understanding during the design of compatibility filters can significantly improve the overall user experience.

Question 22

How can compatibility filters be made more user-friendly and accessible?

Answer 22

Instead of requiring users to apply filters based on technical compatibility specifications, consider converting these specs into terms that are more relatable or accessible to the user, such as the model name or number of the product they already own. For instance, users searching for camera lenses could find compatible options by entering their current camera model, eliminating the need to specify technical details like lens mount type, frame size, or autofocus features. This approach involves reprocessing the lens attributes to generate a comprehensive list of cameras compatible with each lens, ultimately simplifying the filtering process for users.

Question 23

What factors influence the implementation of “translated” compatibility filters?

Answer 23

The resources needed for implementing “translated” compatibility filters depend significantly on the industry and the specific product type. For industries where manufacturers list all compatible products, creating a filter based on product name is relatively straightforward. However, if only compatible product series are provided, it requires cross-referencing them with a list of all product models within each series to compile filters based on product models.

Question 24

What challenges arise when implementing “translated” compatibility filters for certain product types and industries?

Answer 24

In industries where providing compatible products or product series isn’t standard practice, implementing “translated” compatibility filters poses challenges. In such cases, it’s necessary to reprocess the actual product specifications to compile a list of compatible products. Sometimes, sourcing additional data is also required to ensure the accuracy and completeness of the filter options.

Question 25

What are the three significant usability benefits gained by allowing users to filter by their product name when assessing the resources needed for ‘translated’ compatibility filters?

Answer 25

1. Users are more likely to remember the model name of a product they own or plan to purchase, which offers a tangible option for lookup if needed. Conversely, finding specifications for a product they already own can be challenging, as they are not always readily available and may require extensive research, especially for discontinued versions.
2. For users who lack expertise in the product domain, uncertainty often arises regarding whether a given item will fit their existing product, even after verifying compatibility specifications. This uncertainty is especially pronounced when users struggle to understand or relate to technical specifications, such as voltage and watt ratings. Translating these specs into a compatibility relationship based on model names serves as a reassuring factor, providing users with confidence that the product will indeed fit.
3. Users only have to apply a single filter. For some product types, multiple attributes need to fit in order to determine compatibility. For example, for an adapter it would be both charging voltage, charging capacity and the shape of the charger tip. For a camera lens it would be mount type, image frame size, and built-in auto-focus. A translated filter saves the user the hassle of applying multiple filters and avoids the risk of the user not understanding or applying all of them.

Question 26

How can the benefits of translated compatibility filters be fully utilized after users apply them?

Answer 26

After users apply translated compatibility filters, one should capitalize on the advantages by displaying a dynamic verification on all relevant product pages. This feature can significantly alleviate users’ anxiety about purchasing compatibility-dependent products, particularly when the compatibility aspects involve technical specifications.

Question 27

Is it advisable to retain “untranslated” compatibility filters alongside translated ones?

Answer 27

Depending on the audience, maintaining “untranslated” compatibility filters can be beneficial, especially for power users. Additionally, if the specification serves as both a compatibility factor and a performance attribute, keeping the “untranslated” filters is essential to ensure comprehensive filtering options.

Question 28

What method of implementing compatibility filters can make them easier for novice users to understand?

Answer 28

Allowing users to filter for compatibility products based on the product name

Question 29

How do users typically perceive changes to a product list when filters are applied or the sort order is modified?

Answer 29

When users apply filters or change the sort order of a product list, they often view the updated list as a “New” page.

Question 30

What do users expect when they navigate from a product page back to the product list using the “Back” button?

Answer 30

Users typically anticipate that the “Back” button will undo the most recent change and revert the product list back to its previous state, mirroring their expectations when navigating web pages.

Question 31

What do users typically expect when using the “Back” button on a website?

Answer 31

As a general principle, users anticipate that the “Back” button will return them to what they perceive as their previous page. The key factor here is perception, as there can be a distinction between what is technically a new page and what users perceive to be a new page. This perception gap may lead to discrepancies between where users expect the “Back” button to take them and its actual behavior.

Question 32

What is the purpose of the history.pushState() function in the HTML5 History API?

Answer 32

The history.pushState() function enables a website to create a new history entry and rewrite the URL without reloading the page.

Question 33

Why is it important to use history.pushState() when implementing live-updating product lists with applied filters or changed sorting directions?

Answer 33

When a product list live-updates as filters are applied or sorting directions change without a page reload, the list technically remains the same page. Utilizing history.pushState() ensures that the URL is rewritten for each filter applied or sorting direction changed, maintaining a more accurate browsing history for users and aligning with their expectations when using the back button.

Question 34

What should happen when users tap the “Back” button while in a separate filtering or sorting interface, especially on mobile sites?

Answer 34

When users tap “Back” within a separate filtering or sorting interface, particularly on mobile sites, it’s crucial that this action functions similar to an “Exit” link. Users should be seamlessly returned to the view they were previously looking at, mimicking the experience of closing an overlay.

Question 35

How do users typically respond to the process of customizing product lists?

Answer 35

Users are willing to invest time and effort into tailoring product lists if they believe the list contains suitable items, underscoring the importance of personalized product discovery experiences.

Question 36

What are the potential consequences of “forgetting” users’ selected filter options and sorting preferences?

Answer 36

Neglecting to retain users’ selected filter options and sorting preferences not only slows down their browsing experience unexpectedly but also has the potential to diminish their motivation to continue searching for suitable products.

Question 37

What are the potential consequences of resetting filtering and sorting choices, especially if users don’t notice the change?

Answer 37

Resetting filtering and sorting choices without users’ awareness can be particularly harmful. Unnoticed changes in these settings may lead users to draw inaccurate conclusions about the current product list and the overall suitability of products in the catalog, undermining their browsing experience and potentially affecting their purchasing decisions.

Question 38

When should applied filtering values and sorting choices be persisted?

Answer 38

1. Apply another filtering option of the same type or of another type
2. Go back and forth between the product list and individual product pages using either a “Back to results” link on the product page or by clicking the browser “Back” button
3. Refresh or reload the page

Question 39

When shouldn’t filters and sorting be persisted?

Answer 39

1. actively remove the filter or change the sorting direction (either by directly clicking to remove the filter option or change the sort direction or by clicking the “Back” button
2. navigate to an entirely new category scope and then return to the same category (users who get “stuck” are often observed to reenter the same category in an attempt to “reset” it), or
3. resubmit the exact same search query (this is often done with the intent of “resetting” the results as well

Question 40

What challenges do users face when the entire product list page reloads after selecting or deselecting a filter option?

Answer 40

When the entire product list page reloads upon selecting or deselecting a filter option, users needing to choose multiple filter options encounter delays. They must wait for each reload to complete before selecting the next option, resulting in a tedious process, especially when exploring product variations. Moreover, if filter types are not initially visible and require scrolling to locate, users face additional inconvenience.

Question 41

How can friction in the filtering experience be minimized?

Answer 41

Implementing live updates to the product list as filters are selected and deselected can significantly reduce friction. With live updates, typically achieved through JavaScript, users can explore filtering more efficiently by quickly seeing the impact of their choices on the product list. This encourages users to experiment with different filter options, as the process of selecting and deselecting filters is much faster compared to a full page reload.

Question 42

What are the 4 implementation details for live updating product lists?

Answer 42

1. Display load indicators or screen skeleton layouts while the product list is updating
2. Undo the last filter change when the browser “Back” button is clicked
3. Ensure filters are selectable when the product list is updating
4. Generally avoid “Apply” buttons

Question 43

What difficulties did participants encounter with “Apply” buttons during filtering in earlier rounds of testing?

Answer 43

Participants often struggled to understand the purpose of “Apply” buttons when filtering. They questioned why they had to click twice – once to select the filter option and then again to apply it. Some participants either overlooked the buttons or didn’t grasp the concept of applying an option they had just chosen. Additionally, if users needed to apply multiple filter options while viewing their effect on the product list, they would have to click the “Apply” button multiple times.

Question 44

What recommendation is proposed regarding the use of “Apply” buttons for desktop filtering, and why?

Answer 44

“Apply” buttons should generally be avoided for desktop filtering, except in specific cases. This recommendation is made to streamline the filtering experience and address users’ confusion and frustration with the double-click requirement.