Systematic Sources of Suboptimal Interface Design in Large Product Development Organizations

Many poor interface features are the result of carelessness, ignorance, or neglect in the development process. For these features, methods such as user involvement in iterative design with prototyping, the use of check lists and guidelines, and even formal evaluation can be of great help. However, there are strong forces present in development environments that block the use of such methods and distort interface designs in a systematic way. Because these forces serve legitimate goals, such as making a design simpler, more easily communicated, or more marketable, they are more difficult to counter; because developers are skilled at working toward those goals, the tangential effects on the interface usually pass unnoticed. This descriptive, empirical article describes these forces in the context of large organizations developing commercial off-the-shelf software products. Most points are supported by examples and by a logical argument. Not all of the phenomena may appear in a given development organization, but the overall picture of a complex environment in which interface development requires unwavering attention is quite general.

[1]  Gary Perlman,et al.  Asynchronous design/evaluation methods for hypertext technology development , 1989, Hypertext.

[2]  John D. Gould,et al.  How to design usable systems , 1995 .

[3]  Eric Harslem,et al.  Designing the STAR User Interface , 1987, ECICS.

[4]  Jonathan Grudin,et al.  Interactive systems: bridging the gaps between developers and users , 1991, Computer.

[5]  Jonathan Grudin,et al.  Why CSCW applications fail: problems in the design and evaluationof organizational interfaces , 1988, CSCW '88.

[6]  William L. Bewley,et al.  Human factors testing in the design of Xerox's 8010 “Star” office workstation , 1983, CHI '83.

[7]  J. McKendree,et al.  Film techniques applied to the design and use of interfaces , 1991, Proceedings of the Twenty-Fourth Annual Hawaii International Conference on System Sciences.

[8]  S. Joy Mountford,et al.  The Art of Human-Computer Interface Design , 1990 .

[9]  J. Grudin,et al.  Designing in the dark: logics that compete with the user , 1986, CHI '86.

[10]  Graham Greene,et al.  The Human Factor , 1978 .

[11]  Gerhard Schmidt,et al.  Out of Scandinavia: Alternative Approaches to Software Design and System Development , 1989, Hum. Comput. Interact..

[12]  Jonathan Grudin,et al.  The case against user interface consistency , 1989, CACM.

[13]  Jonathan Grudin,et al.  Language evolution and human-computer interaction , 1991 .

[14]  Michael Good The Iterative Design of a New Text Editor , 1985 .

[15]  Ben Shneiderman,et al.  Software psychology: Human factors in computer and information systems (Winthrop computer systems series) , 1980 .

[16]  Laura Marie Leventhal,et al.  Experience of Programming Beauty: Some Patterns of Programming Aesthetics , 1988, Int. J. Man Mach. Stud..

[17]  Kaj Grønbæk,et al.  Supporting Active User Involvement in Prototyping , 1990, Scand. J. Inf. Syst..

[18]  Jonathan Grudin,et al.  User interface design in large corporations: coordination and communication across disciplines , 1989, CHI '89.

[19]  James Cornford,et al.  Computer Systems Development: History, organization and implementation , 1990 .

[20]  Pelle Ehn,et al.  Work-oriented design of computer artifacts , 1989 .

[21]  Steven E. Poltrock,et al.  Innovation in user interface development: obstacles and opportunities , 1989, CHI '89.

[22]  John L. Bennett,et al.  Usability Engineering: Our Experience and Evolution , 1988 .

[23]  B. Schneiderman,et al.  Designing the User Interface. Strategies for Effective Human-Computer Interaction , 1992 .

[24]  Jeanette Blomberg,et al.  The variable impact of computer technologies on the organization of work activities , 1986, CSCW '86.

[25]  Jonathan Grudin,et al.  Positioning human factors in the user interface development chain , 1986, CHI '87.

[26]  Morten Kyng,et al.  Design at Work , 1992 .

[27]  J. E. Sammet,et al.  Software psychology: human factors in computer and information systems , 1983, SGCH.

[28]  Ben Shneiderman,et al.  Designing the User Interface: Strategies for Effective Human-Computer Interaction , 1998 .

[29]  Peter G. Polson,et al.  Theory-Based Design for Easily Learned Interfaces , 1990, Hum. Comput. Interact..

[30]  Jonathan Grudin,et al.  Why good engineers (sometimes) create bad interfaces , 1990, CHI '90.

[31]  John D. Gould Chapter 35 – How to Design Usable Systems , 1988 .

[32]  M. Kyng,et al.  Computers and Democracy: A Scandinavian Challenge , 1987 .

[33]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[34]  J. C. R. Licklider,et al.  On-line man-computer communication , 1899, AFIPS Spring Joint Computing Conference.

[35]  Detmar W. Straub,et al.  Information technologies for the 1990s: an organizational impact perspective , 1989, CACM.

[36]  Jonathan Grudin,et al.  Obstacles to User Involvement in Software Product Development, with Implications for CSCW , 1991, Int. J. Man Mach. Stud..

[37]  R. Kinkead,et al.  Voice: technology searching for communication needs , 1986, CHI '87.

[38]  Sidney L. Smith,et al.  Guidelines for Designing User Interface Software , 1986 .

[39]  Ben Shneiderman,et al.  Designing the user interface (2nd ed.): strategies for effective human-computer interaction , 1992 .

[40]  Myron W. Krueger,et al.  Drama and personality in user interface design , 1989, CHI '89.

[41]  John D. Gould,et al.  The 1984 Olympic Message System: a test of behavioral principles of system design , 1987, CACM.

[42]  Tim Johnson,et al.  Natural Language Computing: The Commercial Applications , 1984, The Knowledge Engineering Review.