Case studies of two software development organizations suggest that common practices of these organizations pose obstacles to innovation. Although software development organizations have good reasons to be conservative and resist innovation, they recognize the importance of innovations to the competitiveness of their products. But organizations experienced at development of regularly scheduled releases are not well suited to development of innovations. In this research investigators worked with the user interface teams in two organizations while interviewing people throughout the organizations. Both organizations developed prototypes, but only small design changes were prototyped and tested early in development. Innovative changes were evaluated late, when resistance to iteration was great. User interface designs and prototypes were often not shown to users. Mechanisms for coordinating development were another conservative influence. Both organizations successfully overcame these obstacles by departing from established practices.
[1]
C. T. Meadow,et al.
On designing for usability: an application of four key principles
,
1986,
CHI '86.
[2]
Jonathan Grudin,et al.
User interface design in large corporations: coordination and communication across disciplines
,
1989,
CHI '89.
[3]
Robert A. Burgelman.
Robert A. BURGELMAN & Leonard R. SAYLES (1986), Inside Corporate Innovation: Strategy, Structure and Managerial Skills
,
1985
.
[4]
Mary Beth Rosson,et al.
The designer as user: building requirements for design tools from design practice
,
1988,
CACM.
[5]
T. Allen.
Managing the flow of technology
,
1977
.
[6]
Bill Curtis,et al.
A field study of the software design process for large systems
,
1988,
CACM.
[7]
Ben Shneiderman,et al.
Designing the User Interface: Strategies for Effective Human-Computer Interaction
,
1998
.