Why Can't We Bet on ISD Outcomes: ISD "Form" as a Predictor of Success

The record of failure to deliver large-scale information systems (IS) in a timely fashion that offer value to major commercial and public organizations is legendary. Just looking to critical success factors such as top management support and user involvement in order to understand how to deliver better systems can at best be a partial solution. We seem to overlook an obvious area in our organizations: what can we learn from our information system development (ISD) historical patterns? In order to develop this idea we draw on parallels in sport where current performance and behaviour are believed to be closely linked to historical precedents, or “form”. In that domain, historical patterns are a fallible but valuable predictor of success. Our thesis is that past negative patterns in ISD will tend to repeat themselves without radical intervention. Put another way, failure begets failure. After examining the game of football as an allegory for ISD, we look briefly at two organizations that have experienced a pattern of failure in the IS area in the past but have transformed the way they build IS, moving from negative patterns to successful ones. This chapter ends with suggestions for managers charged with developing new IS as to how they might use their understanding of ISD “form” to improve their chances of success.

[1]  Rajiv Sabherwal,et al.  Determinants of Commitment to Information Systems Development: A Longitudinal Investigation , 1996, MIS Q..

[2]  Yu Zhao,et al.  The process of enterprise resource planning implementation and business process re‐engineering: tales from two Chinese small and medium‐sized enterprises , 2008, Inf. Syst. J..

[3]  Frank LandVisiting Escalation in Decision Making: The Tragedy of Taurus , 1997 .

[4]  Kalle Lyytinen,et al.  Picking Up the Pieces After a "Successful" Implementation: Networks, Coalitions and ERP Systems , 2008, AMCIS.

[5]  Kweku Ewusi-Mensah,et al.  Critical issues in abandoned information systems development projects , 1997, CACM.

[6]  Rudy Hirschheim,et al.  Information Systems Development as Symbolism: Myth, Metaphor and Magic , 2002 .

[7]  Michael Newman,et al.  Context, Process and Outcomes of ISD: An Allegorical Tale , 2007, AMCIS.

[8]  Kalle Lyytinen,et al.  Learning failure in information systems development , 1999, Inf. Syst. J..

[9]  A. Stinchcombe Information and Organizations , 2019 .

[10]  B. Pentland Building Process Theory with Narrative: from Description to Explanation , 1999 .

[11]  Michael D. Myers,et al.  The qualitative interview in IS research: Examining the craft , 2007, Inf. Organ..

[12]  Rudy Hirschheim,et al.  Symbolism and Information Systems Development: Myth, Metaphor and Magic , 1991, Inf. Syst. Res..

[13]  David E. Avison,et al.  INFORMATION SYSTEMS DEVELOPMENT , 2006 .

[14]  Donal Flynn,et al.  Escalation and de-escalation of commitment to information systems projects: Insights from a project evaluation model , 2006, Eur. J. Oper. Res..

[15]  Mark Keil,et al.  Pulling the Plug: Software Project Management and the Problem of Project Escalation , 1995, MIS Q..

[16]  Daniel Robey,et al.  Sequential patterns in information systems development: an application of a social process model , 1996, TOIS.

[17]  Daniel Robey,et al.  A Social Process Model of User-Analyst Relationships , 1992, MIS Q..

[18]  Albert S. Dexter,et al.  Surviving IT project cancellations , 2005, CACM.