I am in a situation where we have been told our users do not understand the word 'filter' and we have to use the word 'search' instead.
The functions, though, literally are filters by definition: dropdowns that filter out an already populated table, and not searches. We also have things that are searches that are also labelled 'searches'
I am having a lot of internal resistance to, in my mind, mis-labelling functionality. Things should be labelled what they are, and if not, the users will not learn what is not that difficult. But maybe the distinction is not one that the lay-person should care about.
It is an internal site, so the users are not 'the public at large' and are used to doing things in particular ways. Nonetheless, I hate the idea of mislabelling things and they like to search for things.
I guess my specific question is -- should we care about accuracy of terminology in what the user is seeing? Does the user experience of this particular site for these particular users trump the user's opportunity to potentially better understand interfaces in general?