{'fraction_non_alphanumeric': 0.01661392405063291, 'fraction_numerical': 0.0, 'mean_word_length': 5.111111111111111, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Performance vs. Preference

One of the main tenets of most company-sponsored quality programs is that the customer is always right. Designers frequently evaluate the goodness of their systems by simply asking users whether or not they like the interface. The fallacy of this approach is that users genrally make judgements based on their “preferences” and tend to ignore the more important performance issues. System designers frequently use their own preferences to make decisions, and then make major inferences about how users will perform with their system. Several past studies are reviewed to show that users can perform well and not like a system, or like a system and still not perform well. Two recent studies are reported showing a mismatch between designer's preferences for certain interface decisions, and measured user performance when using the resulting interfaces. It is proposed that better user interfaces are possible if we clearly separate the performance and preference concepts, recognize the limitations of each, and work to optimize one or the other (there is usually not sufficient time to optimize both). The only way to ensure that systems will elicit acceptable levels of performance is to conduct performance-oriented usability tests.