Planning for Defaults

Having default settings that can be adjusted can be a pain, if software is being updated through time. I noticed in OmniFocus a way they have set it up that is actually pretty innovative, however minor.

There is a default setting for what day the week begins on (very common); you can change that (very common). The same option is there for time that the day starts on.
However, with the day, the default setting is "Default" -- meaning, they could change that later, which would alter user experiences for anyone who hadn't touched this (that is, who had left it set to "default").
The difference is twofold:
1.) If the software company changes what the default is, and a user notices or cares, and happens to look to see what the preference is set to, they see squarely that they are set to "default" and can understand this might change -- they themselves clearly haven't specified anything in particular.
2.) For the software company, there is a much better way to understand when the value has been specified by the user, in case they want to change what the default is. For example, with the alternative approach to this control, as used with the time (see #2), if a user pulls that down, changes it to 9:00, then changes it back to 8:00, it is unclear if this is a value that they care about, that they set, or if they were just looking at it. In the future, the software provider is unclear if they are working with a default start time (which they might choose to adjust), or something the user has selected and cares about.
"Default" as a value is interesting.