Designing for usability—key principles and what designers think

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).

REFERENCES

• 1: Baker, F. T. & Mills, H. D. Chief Programmer Teams, Datamation, December, 1973, 58-61.
• 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.
• 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)
• 4: Crosby, P. B. Quality is Free. New York: New American Library, 1979
• 5: Dijkstra, E. W. Structured Programming Software Engineering Techniques, NATO Scientific Affairs Division, Brussels 39, Belgium, April 1970, 84-88.
• 6: Dijkstra, D. & Hoare, Structured Programming. New York: Academic Press, 1973.
• 7: Engel, S. & Granda, R. Guidelines for man/display interfaces. IBM Technical Report TR00.2720, Poughkeepsie Lab, N.Y., 1975.
• 8: Gould, J. D. & Boies, S. J. Speech Filing—an office system for principals. IBM Systems Journal, 1983 (in press) (a).
• 9: John D. Gould , Stephen J. Boies, Human factors challenges in creating a principal support office system—the speech filing system approach, ACM Transactions on Information Systems (TOIS), v.1 n.4, p.273-298, Oct. 1983 [doi>10.1145/357442.357443]
• 10: John D. Gould , John Conti , Todd Hovanyecz, Composing letters with a simulated listening typewriter, Communications of the ACM, v.26 n.4, p.295-308, April 1983 [doi>10.1145/2163.358100]
• 11: Gould, J. D. & Lewis, C. H. Human Factors Principles in Designing for Usability. IBM Research Report, 1983.
• 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)
• 13: Lewis, C. H. Using the "Thinking Aloud" Method In Cognitive Interface Design. IBM Research Report, RC-9265, 1982.
• 14: Robert L. Mack , Clayton H. Lewis , John M. Carroll, Learning to use word processors: problems and prospects, ACM Transactions on Information Systems (TOIS), v.1 n.3, p.254-271, July 1983 [doi>10.1145/357436.357440]
• 15: Morgan, C., Williams, G. & Lemmons, P. An interview with Wayne Rosing, Bruce Daniels, and Larry Tesler. Byte. 1983, 90-113.
• 16: Allen Newell, Human Problem Solving, Prentice-Hall, Inc., Upper Saddle River, NJ, 1972
• 17: Thomas, J. C. and Gould, J. D. A Psychological Study of Query-by-Example. Proceedings of 1975 National Computer Conference. 439-445, 1975
• 18: Williams, G. The Lisa computer system. Byte. 1983, 33-50
• 19: Yourdon, E. & Constantine, L. L. Structured Design New York: Yourdon Press, 1976)
• 20: Zloof, M.M. Query by Example—a data base language. IBM Systems Journal, 1977, 4, 324-343.

INDEX TERMS

Primary Classification:
  H. Information Systems
  H.1 MODELS AND PRINCIPLES
      H.1.2 User/Machine Systems
          Subjects: Human factors

Additional Classification:
  H. Information Systems
  H.3 INFORMATION STORAGE AND RETRIEVAL
      H.3.4 Systems and Software
          Subjects: Performance evaluation (efficiency and effectiveness)

  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.1 Project and People Management
          Subjects: Systems analysis and design

General Terms:
Design, Human Factors, Performance