I'm beating myself up over this one, since we had just that discussion today. We were arguing why a customer was eager to pay a week of work for something that could be trained. And to me it’s pretty straight forward. But let me start with the discussion.
A company has two taxonomy trees which it tags its documents with. One is location, the other is organization. Today leaving the field blank means everywhere (location) and everyone (organization). The blank field is default, and when not set everyone everywhere can read it.
I’m arguing for the fact that setting either organization or location to nothing (null), means that no one, nowhere can access the document. This is the way security works, if no one is granted access, no one can read it.
The customer want to change the default field to everyone or everywhere since users don't understand blank meaning all. I'm all for customer needs and usability on this one - but meet comments as "they could be taught what it means saving them a week of work".
What am I missing?