Necessary-use scenarios include all actions that must be performed, but that are not performed frequently. Purging databases and making exceptional requests might fall into this category. Necessary-use interactions also demand robust pedagogy. However, the user won't ever graduate from them to parallel interaction idioms such as keyboard equivalents. Because of the infrequent use, any user will be willing to conform to the program's way of doing things and won't require customization. This excuses the development team from providing the same level of finish that a daily-use scenario would require. It is like the difference between the luxurious finish on the inside of your new Jaguar and the rough metal finish of the car's engine compartment. Although most products have a small repertoire of necessary-use scenarios, it will typically be larger than the set of daily-use scenarios. |