Skills needed by user-centered design practitioners in real software development environments: report on the CHI'92 workshop

ABSTRACT

User-centered design (UCD) of human-computer interfaces--including task flow and documentation---is gaining acceptance in software development organizations. But managers who want their organizations to start using UCD often do not know what characteristics to look for, in candidates for hiring or retraining to fill UCD roles; this article can help. It has the recommendations from participants in a CHI '92 conference workshop on this topic. The 16 workshop participants were UCD practitioners and managers from companies and a few universities across the United States, Canada, and Sweden. This article first describes some typical roles of UCD practitioners in software development organizations. There follows a list of attributes that UCD practitioners should have. Some attributes should be had by all practitioners, regardless of their subspecialties. The most important of those universal attributes are of three types: knowledge that can be acquired formally (e.g., of the human-computer interaction literature, cognitive processes, experimental design, rapid prototyping), skill that can be gotten from experience (e.g., estimating resources needed to do a job, commitment to users, understanding of the software development process, negotiating ability, enjoyment of working on teams, ability to really listen), and attributes that are harder to acquire (e.g., tenacity, flexibility). Every practitioner needs other characteristics as well, but their importances differ by the practitioners' subspecialties (e.g., a design team leader needs team management skills).

REFERENCES

• 1: ACM SIGCHI Curriculum Development Group. (1992). <i>ACM SIGCHI Curricula for Human-Computer Interaction.</i> New York: Association for Computing Machinery.
• 2: Andrew M. Cohill, Information architecture and the design process, Taking software design seriously, Academic Press Professional, Inc., San Diego, CA, 1991
• 3: Tom Dayton, Cultivated eclecticism as the normative approach to design, Taking software design seriously, Academic Press Professional, Inc., San Diego, CA, 1991
• 4: John Karat , Tom Dayton, Taking design seriously: exploring techniques useful in HCI design, ACM SIGCHI Bulletin, v.22 n.2, p.26-33, Oct. 1990 [doi>10.1145/122475.122480]
• 5: CORPORATE Open Software Foundation, OSF/Motif style guide: revision 1.0, Prentice-Hall, Inc., Upper Saddle River, NJ, 1990
• 6: Root, R. W. (1992). <i>Graphical user interface design guidelines for Bellcore software products, Issue 2.0</i> (Memo TM-STS-021819). Piscataway, NJ: Bellcore.
• 7: Smith, S. L., &amp; Mosier, J. N. (1984). <i>Design guidelines for user-system interface software.</i> Hanscom Air Force Base, Massachusetts: Electronic Systems Division, Air Force Systems Command.
• 8: Van Cott, H. P., &amp; Huey, B. M. (Eds.). (1992). <i>Human factors specialists' education and utilization: Results of a survey.</i> Washington, DC: National Academy Press.
• 9: David A. Wroblewski, The construction of human-computer interfaces considered as a craft, Taking software design seriously, Academic Press Professional, Inc., San Diego, CA, 1991

INDEX TERMS

Primary Classification:
  H. Information Systems
  H.1 MODELS AND PRINCIPLES

Additional Classification:
  A. General Literature
  A.0 GENERAL
      Subjects: Conference proceedings

  D. Software
  D.2 SOFTWARE ENGINEERING

  H. Information Systems
  H.5 INFORMATION INTERFACES AND PRESENTATION (I.7)

General Terms:
Design, Human Factors