Some people mistakenly use the terms user experience and usability almost interchangeably. However, usability is increasingly being used to refer specifically to the ease with which users can complete their intended tasks, and is closely associated with usability testing. Therefore, many perceive usability to be a rather tactical aspect of product design. In contrast, UX professionals use the term user experience much more broadly, to cover everything ranging from ease of use to user engagement to visual appeal. User experience better captures all of the psychological and behavioral aspects of users’ interactions with products.
To help define the objectives and scope of user experience efforts, as well as enable their meaningful measurement, I would like to propose a conceptual framework that describes four distinct elements of user experience, as shown in Figure 1, and how they interact with one another in driving better product designs. Read More
Recently, Office Depot redesigned their search user interface, adding attribute-based filtering and creating a more dynamic, interactive user experience. Unfortunately, Office Depot’s interaction design misses some key points, making their new search user interface less usable and, therefore, less effective. That’s the bad news. The good news is that the Office Depot site presents us with an excellent case study for demonstrating some of the important best practices for designing filters for faceted search results, as follows:
Decide on your filter value-selection paradigm—either drill-down or parallel selection.
Provide an obvious and consistent way to undo filter selection.
Always make all filters easily available.
At every step in the search workflow, display only filter values that correspond to the available items, or inventory.
Provide filter values that encompass all items, or the complete inventory.
By following the attribute-based filtering design best practices this article describes, you can ensure your customers can take care of business without having to spend time struggling with your search user interface. Read More
What is the difference between filtering and sorting for a search query? Any SQL developer would be happy to tell you that a sort translates to a SQL ORDER BY statement, while a SQL WHERE clause performs a filter. However, for most users of consumer-facing ecommerce applications, the difference between a sort and a filter presents a mystery they understand dimly, if at all. The distinction between sorting and filtering blurs, because of a phenomenon I’ve called filtering by sorting, which leads to all sorts of interesting search user interface implications. Read More