We're working on a filter interface. Most options can be represented by two options, one using "hide" as the primary verb, and the inverse formulation using "show" as the primary verb.
Discussion on the team and with users has been largely based on personal preference. I'm wondering if there are any UX studies or behavioral economics principles that demonstrate quantifiable effects from using one versus the other. "Show", to me, sounds more active and positive, while "hide" sort of implies that the tools is failing me by showing me irrelevant things...but I don't know if this is my own opinion or representative of an actual UX principle at play. There's also been an argument that we're showing you a set of items by default, and the "hide" terminology more accurately reflects that we're taking out some of what was previously included in that list.
I'm aware of the framing effect, but I'm having trouble figuring out whether using the verb "hide" will frame these options as a loss and therefore contribute to a sub-par experience.
Here's what the filter looks like. (We've decided that to make parsing the options easier, we're probably going to start them all off with the same verb.)
Taking the last option as an example, should I expect any difference in behavior if I use "Hide questions with score < X" rather than using "Show questions with score > 0", even though they mean the same thing?