Problem #1 - Filter Speed

The previous state of Apollo’s on-the-fly filtering system did not allow for the rapid selection of multiple filters within each category.

The lack of rapid selection of filter for in category used caused two usability issues:  

1) It increased the time needed for users to locate relevant articles;  

2) It reduced the ability for user customization. 

Result: Quicker filtering for users, increasing the effectiveness of the app and ease of use.

Problem #2 - Filtering Status and ‘or’ function

While the addition of filtering boxes will improve the UX of Apollo’s filtering, the logic behind Apollo’s filtering system had room for improvement. Apollo lacked an ‘or’ function for its filtering and defaulted to ‘and' logic function. Depending on the user, this exclusionary method of filtering limits the effectiveness of results as more terms are added and unnecessarily limited search results for every term added while also adding to complexity. (Users do not want to figure out how Boolean logic when they’re simply trying to filter news results!)

Solution #2

I identified 3 ways to remedy this UX issue. 

1. Changing the logic of the filter system and treating each filter as an ‘or’ rather than an ‘and’ and adding a ‘Results must include’ box to each filter

2. Adding an AND/OR logic toggle

3. Adding an ‘Advanced Filtering’ setting where the user would customize how they would search

Ultimately, option 1 presented the easiest path forward as it took the cognitive load off the user, while preserving the main use of the product. Since users are likely seeking out news based on a few keywords rather than exclusions, the filtering system was reworked to default to an ‘or’ function (inclusionary) and the ‘and’ function was reworked into a ‘results must include’ option for those who wanted to add exclusions and limits on filtering results. The logic is done in the background of the app, making it easier for the user.

As it stood before, the filtering system unnecessarily limited results exponentially as more filters were added because it defaulted to an ‘and’ function (any result would only populate if all filtering terms were included), but the choice for exclusion should be given to the user as it is an exception more than a rule for news monitoring.

Result: By changing the logic and adding a ‘Results Must Include’ function, customization and prioritization for the user was preserved, and cognitive load on user was reduced, all while maintaining the desired news/legal results. The product was made easier to use and made more effective without any negative effects.

Pain-point specific recommendations (as pointed out in red above) included :

1) Incorporating action buttons properly into the filter’s visual hierarchy so it is clear those buttons relate to filters and not the channel 

2) Create one bar for New/Channel and Channel Name and simplify language to reduce redundancy

3) The select all function under each column should be removed as it does not add value to the user experience and is counterintuitive to setting a priority for a specific filter

4) The search bar should be moved to the top and be more visually emphasized, as it is a user red route

5) The browse function should be merged with the search function to limit unnecessary user choice and streamline the application

6) The low, medium and high columns should be made into a dropdown menu for each specific term to increase simplicity and ease of use

7) The new channel button should be shortened to reflect the likely length of user channel names and reduce clutter

8) A ‘save channel’ button should be added to give the user a sense of control and confidence the application is working as intended

Overall Result

A streamlined channel creation function, utilizing new filtering logic, and allowing users to customize and set their search terms in an easier, intuitive way.