John D. Gould
ABSTRACT
Any system designed for people to use should be (a) easy to learn; (b) useful, i.e., contain functions people really need in their work; (c) easy to use; and (d) pleasant to use. In this note we present theoretical considerations and empirical data relevant to attaining these goals. First, we mention four principles for system design which we believe are necessary to attain these goals; Then we present survey results that demonstrate that our principles are not really all that obvious, but just seem obvious once presented. The responses of designers suggest they may sometimes think they are doing what we recommend when in fact they are not. This is consistent with the experience that systems designers do not often recommend or use them themselves. We contrast some of these responses with what we have in mind in order to provide a more useful description of our principles. Lastly, we consider why this might be so. These sections are summaries of those in a longer paper to appear elsewhere (Gould & Lewis, 1983). In that paper we elaborate on our four principles, showing how they form the basis for a general methodology of design, and we describe a successful example of using them in actual system design (IBM's Audio Distribution System).
- 1.Baker, F. T. & Mills, H. D. Chief Programmer Teams, Datamation, December, 1973, 58-61.Google Scholar
- 2.Boyle, J. M., Bury, K. F., & Evey, R. J. Two studies evaluating learning and use of QBE and SQL. IBM GPD Human Factors Center Tech. Rept. HFC-39, 1981.Google Scholar
- 3.Bury, K. F. & Boyle, J. M. An on-line experimental comparison of two simulated record selection languages. In Edwards, R. E. (Ed.) Proceedings of the Human Factors Society Annual Meeting, 74-78, 1982. (Obtainable from the Human Factors Society, Box 1369, Santa Monica, California 90406)Google Scholar
- 4.Crosby, P. B. Quality is Free. New York: New American Library, 1979Google Scholar
- 5.Dijkstra, E. W. Structured Programming Software Engineering Techniques, NATO Scientific Affairs Division, Brussels 39, Belgium, April 1970, 84-88.Google Scholar
- 6.Dijkstra, D. & Hoare, Structured Programming. New York: Academic Press, 1973.Google Scholar
- 7.Engel, S. & Granda, R. Guidelines for man/display interfaces. IBM Technical Report TR00.2720, Poughkeepsie Lab, N.Y., 1975.Google Scholar
- 8.Gould, J. D. & Boies, S. J. Speech Filing—an office system for principals. IBM Systems Journal, 1983 (in press) (a).Google Scholar
- 9.Gould, J. D. & Boies, S. J. Human factors challenges in creating a principal support office system—The speech filing system approach. ACM Transactions on Office Information Systems. 1983 (in press) (b). Google ScholarDigital Library
- 10.Gould, J. D., Conti, J. & Hovanyecz, T. Composing letters with a simulated listening typewriter. Communications of the ACM, 1983, 26(4), 295-308. Google ScholarDigital Library
- 11.Gould, J. D. & Lewis, C. H. Human Factors Principles in Designing for Usability. IBM Research Report, 1983.Google Scholar
- 12.Kelley, J.F., Natural Language and Computers: Six empirical steps for writing an easy-to-use computer application. Unpublished doctoral dissertation, The Johns Hopkins University, 1983. (Available from University Microfilms International; 300 North Zeeb Rd.; Ann Arbor Mich. 48106)Google Scholar
- 13.Lewis, C. H. Using the "Thinking Aloud" Method In Cognitive Interface Design. IBM Research Report, RC-9265, 1982.Google Scholar
- 14.Mack, R., Lewis, C. H., & Carroll, J. Learning to Use Word Processors: Problems and Prospects. ACM Transactions on office information systems. 1983, 1(3), 254-271. Google ScholarDigital Library
- 15.Morgan, C., Williams, G. & Lemmons, P. An interview with Wayne Rosing, Bruce Daniels, and Larry Tesler. Byte. 1983, 90-113.Google Scholar
- 16.Newell, A. & Simon, H. A. Human Problem Solving. Englewood Cliffs, N.J.: Prentice-Hall, 1972. Google ScholarDigital Library
- 17.Thomas, J. C. and Gould, J. D. A Psychological Study of Query-by-Example. Proceedings of 1975 National Computer Conference. 439-445, 1975Google ScholarDigital Library
- 18.Williams, G. The Lisa computer system. Byte. 1983, 33-50Google Scholar
- 19.Yourdon, E. & Constantine, L. L. Structured Design New York: Yourdon Press, 1976)Google Scholar
- 20.Zloof, M.M. Query by Example—a data base language. IBM Systems Journal, 1977, 4, 324-343.Google ScholarDigital Library
Index Terms
- Designing for usability—key principles and what designers think
Recommendations
Revisiting usability's three key principles
CHI EA '08: CHI '08 Extended Abstracts on Human Factors in Computing SystemsThe foundations of much HCI research and practice were elaborated over 20 years ago as three key principles by Gould and Lewis [7]: early focus on users and tasks; empirical measurement; and iterative design. Close reading of this seminal paper and ...
Designing for usability: key principles and what designers think
This article is both theoretical and empirical. Theoretically, it describes three principles of system design which we believe must be followed to produce a useful and easy to use computer system. These principles are: early and continual focus on users;...
Comments