End Users Expectations Responsibilities
Preferences are definable, named, command-specific settings
presets. They store (almost) all the
settings in a command form. “Loading
a Preference” restores all the form’s settings to previously saved values.
In a well-managed environment the default preferences
should conform should be useful to productivity and conform to standards.
If so, the end user gets what he needs to perform his job in a way that
conforms to standards WITHOUT CHANGING ANY SETTINGS.
If the default Preference does not for some reason produce appropriate
results, the end user should expect that a well-named Preference exists that
will.
If the end user is spending much time changing settings, he
is wasting time. The less time the
end users spend changing settings, the more productive they are.
If at any time a command requires changing a large number of settings
repeatedly, the user should 1) create a new Preference with those settings and
2) notify the InRoads Administrator of the need for a new preference. See
managing settings changes.
| 
