Do your users need filters?
Filters add some visual clutter and complexity to the user interface, so think carefully before including them in your service. It may be that modifications to existing navigation, search or sort functionality can meet the user need.
These tools can be layered on top of one another: services where finding is a core user task may include them all in combination. For example, filters and sort are often used to refine and organise a list of search results.
Questions to ask
What evidence is there that you need to introduce filters? For example, have users suggested filtering would be a way to find things faster?
What does the user journey look like without filters? Filters are an optional tool not a step – users should be able to complete their task without using filters.
How much precision does the user need to continue on their journey?
- Would a dedicated search be a better solution than having to use a combination of filters to narrow down to a single result?
- How many filters does the user need to get results that are easy to scan?
Would introducing filters help or hinder the user journey?
- Does the introduction of filters add to time, cognitive load, and interaction cost?
- Is the overall journey just as efficient without them? Filters should not make the task harder to complete.
How will you measure success?
- What metric are you hoping to improve by introducing filters?
- How will you measure and monitor it?
Do users actually need better navigation?
- If people consistently apply the same filters to their results, there may be a case for changing your service’s navigation to include these views as standard.
Could we improve this page?
Send questions, comments or suggestions to the DWP Design System team.
Last updated: