David G. Novick
ABSTRACT
Few users of computer applications seek help from the documentation. This paper reports the results of an empirical study of why this is so and examines how, in real work, users solve their usability problems. Based on in-depth interviews with 25 subjects representing a varied cross-section of users, we find that users do avoid using both paper and online help systems. Few users have paper manuals for the most heavily used applications, but none complained about their lack. Online help is more likely to be consulted than paper manuals, but users are equally likely to report that they solve their problem by asking a colleague or experimenting on their own. Users cite difficulties in navigating the help systems, particularly difficulties in finding useful search terms, and disappointment in the level of explanation found.
- Baecker, R., Booth, K., Jovicic, S., McGrenere, J. and Moore, G. (2000). Reducing the gap between what users know and what they need to know. Proceedings of the ACM 2000 International Conference on Intelligent User Interfaces, 17--23. Google Scholar
Digital Library
- Bessiere, K., Ceaparu, I., Lazar, J., Robinson, J., and Shneiderman, B. (2003). Social and psychological influences on computer user frustration, CS Technical Report 4410, Department of Computer Science. University of Maryland.Google Scholar
- Beyer, H., and Holtzblatt, K. (1996). Contextual design: Defining customer-centered systems. San Francisco: Morgan-Kaufmann. Google ScholarDigital Library
- Carroll, J. (1990). The Nurnberg funnel: Designing minimalist instruction for practical computer skill. Cambridge, MA: MIT Press. Google ScholarDigital Library
- Carroll, J. (Ed.) (1998). Minimalism beyond the Nurnberg funnel. Cambridge, MA: MIT Press.Google Scholar
- Ceaparu, I., Lazar, J., Bessiere, K., Robinson, J., and Shneiderman, B. (2004). Determining causes and severity of end-user frustration, International Journal of Human-Computer Interaction, 17(3), 333--356.Google ScholarCross Ref
- Hazlett, R. (2003). Measurement of user frustration: a biologic approach, Conference on Human Factors in Computing Systems (CHI 2003), 734--735. Google ScholarDigital Library
- Hilbert, D. (1998). A survey of computer-aided techniques for extracting usability information from user interface events, Technical Report UCI-ICS-98-13, Department of Information and Computer Science, University of California at Irvine, March, 1998.Google Scholar
- Mendoza, V., and Novick, D. (2005). Usability over time, Proceedings of SIGDOC 2005, Coventry, UK, September 21-23, 2005, 151--158. Google ScholarDigital Library
- Rettig, M. (1991). Nobody reads documentation, Communications of the ACM, 34(7), July 1991, 19--24. Google ScholarDigital Library
- Smart, K., De Tienne, K., Whitting, M. (1995). Documentation design decisions: Accounting for customer preferences, Proceedings of SIGDOC 95, September-October, 1995, Savannah, GA, 155--156. Google ScholarDigital Library
- Smart, K., De Tienne, K., Whiting, M. (1998). Customers' use of documentation: The enduring legacy of print, Proceedings of SIGDOC 98, September, 1998, Quebec, Canada, 23--28. Google ScholarDigital Library
- Smart, K., Whiting, M., and De Tienne, K (2001). Assessing the need for printed and online documentation: A study of customer preference and use, Journal of Business Communication 38(3), 285--314.Google ScholarCross Ref
Index Terms
- Why don't people read the manual?
Recommendations
Toward a more accurate view of when and how people seek help with computer applications
SIGDOC '07: Proceedings of the 25th annual ACM international conference on Design of communicationBased on 40 interviews and 11 on-site workplace observations of people using computer applications at work, we confirm that use of printed and on-line help is very low and find that providing greater detail of categories solution methods can present a ...
Supporting end-user debugging: what do users want to know?
AVI '06: Proceedings of the working conference on Advanced visual interfacesAlthough researchers have begun to explicitly support end-user programmers' debugging by providing information to help them find bugs, there is little research addressing the right content to communicate to these users. The specific semantic content of ...
Getting access to what goes on in people's heads?: reflections on the think-aloud technique
NordiCHI '02: Proceedings of the second Nordic conference on Human-computer interactionOne of the basic usability testing techniques the HCI community draws on, and which stands out as unique, is thinking aloud. We introduce the many names, uses and modifications of the classical think aloud technique, and ask the rhetorical question: ...
Comments