A Study of User Involvement in Packaged Software Selection

This paper is concerned with the decision-making processes surrounding the adoption of packaged software in organizations. We begin by looking at its increasing utilization and consider some of the strengths and limitations of employing a standardized approach, particularly in relation to its consideration of end-user requirements. We note the highly problematic nature of installing a global standardized product in the local environment. Using a field study concerning the adoption of a customer relationship management package in a small organization, we go on to illustrate the limited amount of end-user involvement in the selection and procurement of the product. We argue that the art of salesmanship by the third party vendor and project team, which focuses on the interests of senior management, ultimately secures the selection and procurement of the software package.

[1]  Claudio U. Ciborra,et al.  A theory of information systems based on improvisation , 1999 .

[2]  Erran Carmel,et al.  Customer-developer links in software development , 1995, CACM.

[3]  Steven Sawyer,et al.  Packaged software: implications of the differences from custom approaches to software development , 2000, Eur. J. Inf. Syst..

[4]  Enid Mumford,et al.  Computer systems in work design--the ETHICS method : effective technical and human implementation of computer systems , 1979 .

[5]  Niels Bjørn-Andersen,et al.  International Conference on Information Systems ( ICIS ) 1986 POWER OVER USERS : ITS EXERCISE BY SYSTEM PROFESSIONALS , 2017 .

[6]  Hubert Österle,et al.  Accelerated SAP: 4 Case Studies , 1998 .

[7]  Izak Benbasat,et al.  The Case Research Strategy in Studies of Information Systems , 1987, MIS Q..

[8]  Paul Quintas,et al.  A product-process model of innovation in software development , 1994, J. Inf. Technol..

[9]  Edward Yourdon,et al.  Managing the structured techniques , 1980 .

[10]  N. Blaikie.  Approaches to Social Enquiry , 1993 .

[11]  Lisa Bud-Frierman.  Information Acumen: The Understanding and Use of Knowledge in Modern Business , 1994 .

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

[13]  Frederick P. Brooks,et al.  No Silver Bullet: Essence and Accidents of Software Engineering , 1987 .

[14]  Patrick Y. K. Chau,et al.  Factors used in the selection of packaged software in small businesses: Views of owners and managers , 1995, Inf. Manag..

[15]  Juliet Webster,et al.  Mismatch and Tension: Standard Packages and Non-standard Users' , 1993 .

[16]  Geoff Walsham,et al.  Interpretive case studies in IS research: nature and method , 1995 .

[17]  Erran Carmel,et al.  American Software Hegemony in Packaged Software and 'the Culture Software' , 1997, Inf. Soc..

[18]  Sia Siew Kien,et al.  Enterprise resource planning: cultural fits and misfits: is ERP a universal solution? , 2000, CACM.

[19]  Steve Sawyer,et al.  Packaged software development teams: what makes them different? , 1998, Inf. Technol. People.

[20]  Steve Sawyer,et al.  A market-based perspective on information systems development , 2001, CACM.

[21]  Steve Woolgar,et al.  The Machine at Work: Technology, Work and Organization , 1997 .

[22]  C. H. Kriebel.  Management information systems , 1970, ACM '70.

[23]  Angèle L. M. Cavaye,et al.  User participation in system development revisited , 1995, Inf. Manag..

[24]  L. Suchman.  Plans and situated actions , 1987 .

[25]  Paul Quintas.  Social dimensions of systems engineering: people, processes, policies and software development , 1993 .

[26]  M. Markus,et al.  The Enterprise System Experience— From Adoption to Success , 2000 .

[27]  Blake Ives,et al.  User Involvement in System Design: An Empirical Test of Alternative Approaches , 1981, Inf. Manag..

[28]  Laurence Brooks,et al.  Identifying and classifying processes (traditional and soft factors) that support COTS component selection: a case study , 2000, ECIS.

[29]  Gerald M. Weinberg,et al.  Computer Systems Development: History Organization and Implementation , 1991 .

[30]  M. Lynne Markus,et al.  Learning from adopters' experiences with ERP: problems encountered and success achieved , 2000, J. Inf. Technol..

[31]  Henry C. Lucas,et al.  Implementing Packaged Software , 1987, MIS Q..

[32]  Wanda J. Orlikowski,et al.  Improvising Organizational Transformation Over Time: A Situated Change Perspective , 1996, Inf. Syst. Res..

[33]  Prasad Bingi,et al.  Critical Issues Affecting an ERP Implementation , 1999, Inf. Syst. Manag..

[34]  Brian P. Bloomfield.  Understanding the social practices of systems developers , 1992, Inf. Syst. J..

[35]  Janet Butler.  Risk Management Skills Needed in A Packaged Software Environment , 1999, Inf. Syst. Manag..

[36]  Ben Light,et al.  The maintenance implications of the customization of ERP software , 2001, J. Softw. Maintenance Res. Pract..

[37]  O. Hanseth,et al.  From Control to Drift: The Dynamics of Corporate Information Infrastructures , 2000 .

[38]  M. Lynne Markus,et al.  Power, politics, and MIS implementation , 1987, CACM.

[39]  Trevor Wood-Harper,et al.  A critical perspective on action research as a method for information systems research , 1996, J. Inf. Technol..

[40]  Gordon B. Davis,et al.  Management information systems : conceptual foundations, structure, and development , 1985 .